[Enhancement](point query optimize) improve performace of point query on primary keys #15491
[Enhancement](point query optimize) improve performace of point query on primary keys #15491dataroaring merged 12 commits intoapache:masterfrom
Conversation
960efac to
066475f
Compare
|
Add documents later pls |
|
TeamCity pipeline, clickbench performance test result: |
xiaokang
left a comment
There was a problem hiding this comment.
be code reviewed.
wonderful job for point query performance.
494aa9c to
cb2c970
Compare
|
@xiaokang PR modified according to code review, lets' continue ? |
dffab70 to
2b22b71
Compare
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
There was a problem hiding this comment.
LGTM. We should complement docs later and we'd better let rowset and segment do not handle ifs for rowstore.
Because it is a independent with others, and column update of mow depends on it, so I merge it and notify the author that he should adjust some code.
|
PR approved by at least one committer and no changes requested. |
… on primary keys (apache#15491) 1. support row format using codec of jsonb 2. short path optimize for point query 3. support prepared statement for point query 4. support mysql binary format
…tatement is a point query in `OriginPlanner` (apache#26881) close apache#26882 We should not use the singleNodePlan to generate the rootPlanFragment if the query is inside a insert statement or distributedPlanner will be null. introduced in apache#15491
…tatement is a point query in `OriginPlanner` (apache#26881) close apache#26882 We should not use the singleNodePlan to generate the rootPlanFragment if the query is inside a insert statement or distributedPlanner will be null. introduced in apache#15491
…tatement is a point query in `OriginPlanner` (apache#26881) close apache#26882 We should not use the singleNodePlan to generate the rootPlanFragment if the query is inside a insert statement or distributedPlanner will be null. introduced in apache#15491
Proposed changes
Issue Number: close #15571
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...