[jira] [Updated] (DRILL-3846) Metadata Caching : A count(*) query took more time with the cache in place

2018-10-29 Thread Pritesh Maker (JIRA) 


 [ 
https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pritesh Maker updated DRILL-3846:
-
Fix Version/s: (was: 1.15.0)
   1.16.0

> Metadata Caching : A count(*) query took more time with the cache in place
> --
>
> Key: DRILL-3846
> URL: https://issues.apache.org/jira/browse/DRILL-3846
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Rahul Challapalli
>Assignee: Venkata Jyothsna Donapati
>Priority: Critical
> Fix For: 1.16.0
>
>
> git.commit.id.abbrev=3c89b30
> I have a folder with 10k complex files. The generated cache file is around 
> 486 MB. The below numbers indicate that we regressed in terms of performance 
> when we generated the metadata cache
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (30.835 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata 
> `complex_sparse_5files`;
> +---+-+
> |  ok   |   summary   
> |
> +---+-+
> | true  | Successfully updated metadata for table complex_sparse_5files.  
> |
> +---+-+
> 1 row selected (10.69 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (47.614 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (DRILL-3846) Metadata Caching : A count(*) query took more time with the cache in place

2018-09-14 Thread Pritesh Maker (JIRA) 


 [ 
https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pritesh Maker updated DRILL-3846:
-
Fix Version/s: (was: Future)

> Metadata Caching : A count(*) query took more time with the cache in place
> --
>
> Key: DRILL-3846
> URL: https://issues.apache.org/jira/browse/DRILL-3846
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Rahul Challapalli
>Assignee: Venkata Jyothsna Donapati
>Priority: Critical
> Fix For: 1.15.0
>
>
> git.commit.id.abbrev=3c89b30
> I have a folder with 10k complex files. The generated cache file is around 
> 486 MB. The below numbers indicate that we regressed in terms of performance 
> when we generated the metadata cache
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (30.835 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata 
> `complex_sparse_5files`;
> +---+-+
> |  ok   |   summary   
> |
> +---+-+
> | true  | Successfully updated metadata for table complex_sparse_5files.  
> |
> +---+-+
> 1 row selected (10.69 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (47.614 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (DRILL-3846) Metadata Caching : A count(*) query took more time with the cache in place

2018-09-02 Thread Kunal Khatua (JIRA) 


 [ 
https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kunal Khatua updated DRILL-3846:

Fix Version/s: 1.15.0

> Metadata Caching : A count(*) query took more time with the cache in place
> --
>
> Key: DRILL-3846
> URL: https://issues.apache.org/jira/browse/DRILL-3846
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Rahul Challapalli
>Assignee: Parth Chandra
>Priority: Critical
> Fix For: Future, 1.15.0
>
>
> git.commit.id.abbrev=3c89b30
> I have a folder with 10k complex files. The generated cache file is around 
> 486 MB. The below numbers indicate that we regressed in terms of performance 
> when we generated the metadata cache
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (30.835 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata 
> `complex_sparse_5files`;
> +---+-+
> |  ok   |   summary   
> |
> +---+-+
> | true  | Successfully updated metadata for table complex_sparse_5files.  
> |
> +---+-+
> 1 row selected (10.69 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (47.614 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (DRILL-3846) Metadata Caching : A count(*) query took more time with the cache in place

2015-10-26 Thread Zelaine Fong (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zelaine Fong updated DRILL-3846:

Assignee: Parth Chandra

> Metadata Caching : A count(*) query took more time with the cache in place
> --
>
> Key: DRILL-3846
> URL: https://issues.apache.org/jira/browse/DRILL-3846
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Rahul Challapalli
>Assignee: Parth Chandra
>Priority: Critical
> Fix For: 1.3.0
>
>
> git.commit.id.abbrev=3c89b30
> I have a folder with 10k complex files. The generated cache file is around 
> 486 MB. The below numbers indicate that we regressed in terms of performance 
> when we generated the metadata cache
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (30.835 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata 
> `complex_sparse_5files`;
> +---+-+
> |  ok   |   summary   
> |
> +---+-+
> | true  | Successfully updated metadata for table complex_sparse_5files.  
> |
> +---+-+
> 1 row selected (10.69 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (47.614 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DRILL-3846) Metadata Caching : A count(*) query took more time with the cache in place

2015-09-28 Thread Rahul Challapalli (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rahul Challapalli updated DRILL-3846:
-
Priority: Critical  (was: Major)

> Metadata Caching : A count(*) query took more time with the cache in place
> --
>
> Key: DRILL-3846
> URL: https://issues.apache.org/jira/browse/DRILL-3846
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Reporter: Rahul Challapalli
>Priority: Critical
> Fix For: 1.2.0
>
>
> git.commit.id.abbrev=3c89b30
> I have a folder with 10k complex files. The generated cache file is around 
> 486 MB. The below numbers indicate that we regressed in terms of performance 
> when we generated the metadata cache
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (30.835 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> refresh table metadata 
> `complex_sparse_5files`;
> +---+-+
> |  ok   |   summary   
> |
> +---+-+
> | true  | Successfully updated metadata for table complex_sparse_5files.  
> |
> +---+-+
> 1 row selected (10.69 seconds)
> 0: jdbc:drill:zk=10.10.100.190:5181> select count(*) from 
> `complex_sparse_5files`;
> +--+
> |  EXPR$0  |
> +--+
> | 100  |
> +--+
> 1 row selected (47.614 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)