[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-18780: Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to master. Thanks, Slim! > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.11.patch, HIVE-18780.12.patch, > HIVE-18780.13.patch, HIVE-18780.14.patch, HIVE-18780.2.patch, > HIVE-18780.4.patch, HIVE-18780.5.patch, HIVE-18780.6.patch, > HIVE-18780.7.patch, HIVE-18780.8.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.14.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.11.patch, HIVE-18780.12.patch, > HIVE-18780.13.patch, HIVE-18780.14.patch, HIVE-18780.2.patch, > HIVE-18780.4.patch, HIVE-18780.5.patch, HIVE-18780.6.patch, > HIVE-18780.7.patch, HIVE-18780.8.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.13.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.11.patch, HIVE-18780.12.patch, > HIVE-18780.13.patch, HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.5.patch, HIVE-18780.6.patch, HIVE-18780.7.patch, > HIVE-18780.8.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.12.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.11.patch, HIVE-18780.12.patch, > HIVE-18780.2.patch, HIVE-18780.4.patch, HIVE-18780.5.patch, > HIVE-18780.6.patch, HIVE-18780.7.patch, HIVE-18780.8.patch, HIVE-18780.patch, > HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.11.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.11.patch, HIVE-18780.2.patch, > HIVE-18780.4.patch, HIVE-18780.5.patch, HIVE-18780.6.patch, > HIVE-18780.7.patch, HIVE-18780.8.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.8.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.5.patch, HIVE-18780.6.patch, HIVE-18780.7.patch, > HIVE-18780.8.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.7.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.5.patch, HIVE-18780.6.patch, HIVE-18780.7.patch, HIVE-18780.patch, > HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.6.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.5.patch, HIVE-18780.6.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.5.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.5.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.4.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.4.patch, > HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.2.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.2.patch, HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.patch, HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Status: Patch Available (was: Open) > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Attachment: HIVE-18780.patch > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > Attachments: HIVE-18780.patch > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Fix Version/s: 3.0.0 > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > Fix For: 3.0.0 > > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-18780) Improve schema discovery For Druid Storage Handler
[ https://issues.apache.org/jira/browse/HIVE-18780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] slim bouguerra updated HIVE-18780: -- Component/s: Druid integration > Improve schema discovery For Druid Storage Handler > -- > > Key: HIVE-18780 > URL: https://issues.apache.org/jira/browse/HIVE-18780 > Project: Hive > Issue Type: Improvement > Components: Druid integration >Reporter: slim bouguerra >Assignee: slim bouguerra >Priority: Major > > Currently, Druid Storage adapter issues a Segment metadata Query every time > the query is of type Select or Scan. Not only that but then every input split > (map) will do the same as well since it is using the same Serde, this is very > expensive and put a lot of pressure on the Druid Cluster. The way to fix this > is to add the schema out of the calcite plan instead of serializing the query > itself as part of the Hive query context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
