Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Image, 2D bounding box and segmentation as Arrow extension types #22

Closed
5 tasks
eddyxu opened this issue Jul 11, 2022 · 3 comments
Closed
5 tasks
Assignees
Labels
c++ C++ issues python

Comments

@eddyxu
Copy link
Contributor

eddyxu commented Jul 11, 2022

Problem Statement

To support rich semantic types, we can utilize Arrow's extension types. It will help us to reach to the feature parity to Rikai storage format.

Questions to answers:

  • Do we want to only implement the data type in Lance?
  • How should we consolidate with Rikai's type system?
  • How to make the type system extensible?
  • Or should we keep the extension types out of the lance data format. Lance just accepts extension types?

Desired Behavior

  • Support Image type
  • Bounding Box
  • Segmentation
  • Label?
  • These objects can be SerDe transparently without manually providing schema.
@changhiskhan
Copy link
Contributor

does “only implement the data type in lance” mean whether to implement arrow extension type? Or whether to implement python classes in pylance (like in rikai)?

@changhiskhan
Copy link
Contributor

  • Start with just image/box2d
  • Separate dir and branch in lance
  • Figure out whether to create separate repo/project for this
  • How to not confuse early adopters but also not turn lance into a kitchen sink project like Rikai

@changhiskhan
Copy link
Contributor

going to make a separate issue for Segmentation etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ C++ issues python
Projects
None yet
Development

No branches or pull requests

2 participants