-
Notifications
You must be signed in to change notification settings - Fork 993
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
PHOENIX-7014: Query compiler/optimizer changes along with some PHOENIX-7015 changes #1766
Merged
virajjasani
merged 29 commits into
apache:PHOENIX-7001-feature
from
haridsv:PHOENIX-7015
Dec 23, 2023
Merged
Changes from all commits
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
c57f9b4
Simplified hint parsing logic
haridsv 74c0c9e
Set parent table info for CDC PTable
haridsv 9bab359
Experimental client side compiler and optimizer changes with a lot of…
haridsv 884db9e
Update PHOENIX_ROW_TIMESTAMP to DATE type to be consistent with that …
haridsv 79b5090
Remove debug code
haridsv 5291bbf
Add a new assert for unimplemented functionality and also implement a…
haridsv a9e5e33
Fixex for failing hint test scenarios
haridsv 7ab3b95
Go through the uncovered index via hint
haridsv fce7ea6
A small deduping attempt
haridsv 66f99d2
Fix typo
haridsv c0f2910
Add test coverage to catch my earlier typo in BaseQueryPlan
haridsv 6ec934f
Update test case after previous typo fix
haridsv 1e4ade2
Parking ad-hoc changes to get projection type with correct expression…
haridsv 291049e
Removed previous CDC specific optimizer code and bypassed optimizer c…
haridsv 3fc774b
revert whitespace diff and remove some dead code.
haridsv e97ff2b
Narrow down some more diff
haridsv 2a6b4f9
Got the mock data to come through to the client side as expected
haridsv 1f6b6fc
Address a FIXME and remove some debug code
haridsv 002ddb6
Recognize CDC hints and serialize into a scan attribute
haridsv 1a9d19e
Remove debug code
haridsv d810886
Experimental CDC scanner with raw scan
haridsv a3a09b3
Snapashot of experimental changes
haridsv 733420f
Snapshot of experimental changes with timeline
haridsv 8fae9d6
Merge remote-tracking branch 'upstream/PHOENIX-7001-feature' into PHO…
haridsv 26f7356
Switch from TreeMap to HashMap where possible
haridsv a9244c5
Reuse scanDataRows from base class
haridsv d9dce19
Address spotbugs
haridsv 72faab4
Fix an NPE and add more test cases
haridsv ea2d8fa
Clone byte arrays for additional scenarios
haridsv File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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 file contains 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 file contains 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 file contains 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 file contains 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 file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everytime we run
CREATE CDC
do we need to passPHOENIX_ROW_TIMESTAMP
? If that is something mandatory we shouldn't make it part of the interface and the system should do it implicitly under the hood.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also it seems the uncovered index that is being created as part of CREATE CDC is being created synchronously. That will only work for small tables. For bigger tables the index needs to be created async and then built explicitly using IndexTool.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The feature allows any timestamp like column to be used instead of the PHOENIX_ROW_TIMESTMAP that is why this flexibility is being allowed, however I am not 100% sure about the use cases, I will have an offline discussion on this, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we do this, won't we also need to project the index status via CDC object, since we intend to keep the index hidden as an implementation detail? Do you think we should have an offline mode for CREATE CDC itself?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that can be later improvement but supporting creation of async index is necessary because creating sync index for large table will anyways be too expensive or not possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@haridsv I didn't quite understand what you mean by index status here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was referring to the async index creation lifecycle, which should be attributed to the CDC so that user can query and know when it is done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tkhurana In any case, I am not planning to address these as part of this PR, so are you OK to merge this as is?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, we can tackle that in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tkhurana Async index creation is addressed as part of #1802.
Also removed the need to explicitly specify
PHOENIX_ROW_TIMESTAMP()
as we dropped the support for user specified timestamp column.