Re-implement support for query on local cache #204
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR integrated a basic custom execution plan for datafusion based on existing listing features. Whenever query happens it fetches all the arrows file and loads them into memory. Ideally it will have to load two or three arrow files, this is trivial and done through memory execution plan. Other one is cached parquet which may or may not be synced at query time, this is queried through already existing listing table. Finally result of local execution is combined with that of execution for object storage. To prevent files from being removed while they are used for query there is now a basic global file tracker which will only remove file once it has been uploaded and no on going query is using that file. - [ ] Greater pruning based on query time, limit and offset - [ ] Combined execution model ( will be added after further improvements )
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR integrated a basic custom execution plan for Datafusion based on existing listing features. Whenever query happens it fetches all the arrows file and loads them into memory. Ideally it will have to load two or three arrow files, this is trivial and done through memory execution plan. Other one is cached parquet which may or may not be synced at query time, this is queried through already existing listing table. Finally result of local execution is combined with that of execution for object storage. To prevent files from being removed while they are used for query there is now a basic global file tracker which will only remove file once it has been uploaded and no on going query is using that file.
Todo
This PR has: