[
https://issues.apache.org/jira/browse/HUDI-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409226#comment-17409226
]
ASF GitHub Bot commented on HUDI-2101:
--------------------------------------
xiarixiaoyao edited a comment on pull request #3330:
URL: https://github.com/apache/hudi/pull/3330#issuecomment-912204147
@vinothchandar thanks for your review. yes this feature is a largely
independent functionality, we can always land and iterate.
The reason we use optimize api to implement z-order is that this method is
flexible enough. user no need to configure cumbersome cluster strategy。 user
can select certain partitions to do optimization by specify partition filter
conditions directly。
of course， I will delete this method if we find this method is useless.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> support z-order for hudi
> ------------------------
>
> Key: HUDI-2101
> URL: https://issues.apache.org/jira/browse/HUDI-2101
> Project: Apache Hudi
> Issue Type: Sub-task
> Components: Spark Integration
> Reporter: tao meng
> Assignee: tao meng
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.10.0
>
>
> support z-order for hudi to optimze the query
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
