-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[Fix](Outfile) The Struct
type data exported from select outfile
to the csv
file format should contain a column name
#28068
Conversation
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
(From new machine)TeamCity pipeline, clickbench performance test result: |
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
|
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.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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.
LGTM
…he csv file format should contain a column name apache#28068 If the original data is: ```sql +-----------------------------------------------------+ | s_info | +-----------------------------------------------------+ | {"s_id": 2, "s_name": "nereids", "s_address": "20"} | | {"s_id": 1, "s_name": "doris", "s_address": "18"} | +-----------------------------------------------------+ ``` In the original logic, the struct type data exported to a csv file format did not contain column names,like ``` {2, "nereids", "20"} {1, "doris", "18"} ``` This pr do not need to be merged into branch-2.0
Proposed changes
Issue Number: close #xxx
If the original data is:
In the original logic, the struct type data exported to a csv file format did not contain column names,like
This pr do not need to be merged into branch-2.0
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...