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

Schema extraction #1525

Open
wohali opened this issue Aug 7, 2018 · 0 comments
Open

Schema extraction #1525

wohali opened this issue Aug 7, 2018 · 0 comments

Comments

@wohali
Copy link
Member

wohali commented Aug 7, 2018

@janl:

I have half an (old) patch that extracts top level fields from a document and stores them with a hash in an “attachment” to the database header. So we only end up storing doc values and the schema hash. First of all this trades storage for CPU time (I haven’t measured anything yet), but more interestingly, we could use that schema data to do smart things like auto-generating a validation function / mango expression based on the data that is already in the database. And other fun things like easier schema migration operations that are native in CouchDB and thus a lot faster than external ones. For the curious ones, I’ve got the idea from V8’s property access optimisation strategy.

@kocolosk:

Cloudant has some work on a metadata system that computes the schemas for various clusters of documents in a database. First use case for us was schlepping the data into a relational data warehouse for analytics. Not sure if we can open source the code but agreeing on a schema format would be good.

@wohali wohali added this to In Discussion in Roadmap Aug 7, 2018
@wohali wohali moved this from Proposed for 3.x to Proposed (backlog) in Roadmap Jul 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap
  
Proposed (backlog)
Development

No branches or pull requests

1 participant