blaze / blaze/odo

`odo.resource(in_memory_object)`

Open
#320 1 comment 0 reactions 0 assignees View on GitHub
question testing user experience
Dominant language
Python
Stars
1k
Forks
131
PR merge metrics
No merged PRs in 30d

Description

Conceptually, it seems like it should be possible to create an `odo.resource()` from an in-memory object, like a `DataFrame`, for instance. I get an exception when trying to pass a df to `resource()` however. This requires me to persist the dataframe first, and then use `odo.resource()` on the CSV, for example.

Any reason why making a resource out of an in-memory object can't work?

The usecase is exploration, testing, debugging, and fleshing out odo's `resource()` abstraction.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating odo.resource() and reproducing the exception with an in-memory DataFrame. Read the surrounding resource abstraction and existing handling for CSV inputs before deciding how in-memory objects should fit. Done means the exploration use case works without first persisting the DataFrame, with behavior covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.