[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2887: -- Labels: impala performance roadmap-candidate (was: impala roadmap-candidate) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: LiFu He >Priority: Minor > Labels: impala, performance, roadmap-candidate > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count( *) from table". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2887: -- Labels: imapala (was: ) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: LiFu He >Priority: Minor > Labels: imapala > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count( *) from table". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2887: -- Labels: impala roadmap-candidate (was: impala) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: LiFu He >Priority: Minor > Labels: impala, roadmap-candidate > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count( *) from table". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-2887: -- Labels: impala (was: imapala) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: LiFu He >Priority: Minor > Labels: impala > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count( *) from table". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HeLifu updated KUDU-2887: - Description: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the query like "select count(*) from table". (was: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) short) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: HeLifu >Priority: Minor > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count(*) from table". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HeLifu updated KUDU-2887: - Description: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the query like "select count( *) from table". (was: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the query like "select count(*) from table".) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: HeLifu >Priority: Minor > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the > query like "select count( *) from table". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-2887) Expose the tablet statistics in Client API
[ https://issues.apache.org/jira/browse/KUDU-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] HeLifu updated KUDU-2887: - Description: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) short (was: The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically.) > Expose the tablet statistics in Client API > -- > > Key: KUDU-2887 > URL: https://issues.apache.org/jira/browse/KUDU-2887 > Project: Kudu > Issue Type: Improvement > Components: client >Reporter: HeLifu >Priority: Minor > > The patch about aggregating tablet statistics on the kudu-master is on the > way. And I think it's important to expose these statistics in client api by > which the query engine can optimize their query plan. For example: (1) adjust > the order of scanning tables, (2) Split a big tablet into multiple range > pieces(KUDU-2437) to improve concurrency automatically, (3) short -- This message was sent by Atlassian JIRA (v7.6.3#76005)
