Refactor FT interface #1351
Merged
Refactor FT interface #1351
Conversation
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
andyfengHKU
approved these changes
Mar 6, 2023
| @@ -18,7 +18,9 @@ std::unique_ptr<PhysicalOperator> PlanMapper::mapLogicalExpressionsScanToPhysica | |||
| auto sharedState = std::make_shared<FTableSharedState>(); | |||
| // populate static table | |||
| std::unique_ptr<FactorizedTableSchema> tableSchema = std::make_unique<FactorizedTableSchema>(); | |||
| // TODO(Ziyi): remove vectors when we have done the refactor of dataChunk. | |||
| std::vector<std::shared_ptr<ValueVector>> vectors; | |||
There was a problem hiding this comment.
Can't u remove vectors?
There was a problem hiding this comment.
No, vectors need to take ownership of the valueVectors because the expression evaluator will be destroyed after.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
shared_ptr<ValueVector>as the input parameter type, the new set of APIs now takes inValueVector*.shared_ptr<ValueVector>. Instead of usingshared_ptr<ValueVector>, we should consider usingunique_ptr<ValueVector>for ownership andValueVector*when passing around.