[jira] [Commented] (PHOENIX-2991) Add missing documentation for functions

[ https://issues.apache.org/jira/browse/PHOENIX-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436269#comment-15436269 ] Maryann Xue commented on PHOENIX-2991: -- [~jamestaylor] bq. I don't think we should document

[jira] [Created] (PHOENIX-3206) Make default Calcite-Phoenix JDBC driver compatible with PhoenixConnection interfaces

Maryann Xue created PHOENIX-3206: Summary: Make default Calcite-Phoenix JDBC driver compatible with PhoenixConnection interfaces Key: PHOENIX-3206 URL: https://issues.apache.org/jira/browse/PHOENIX-3206

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436071#comment-15436071 ] Andrew Purtell commented on PHOENIX-1751: - Ok, then I don't have a good idea what the issue

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436063#comment-15436063 ] James Taylor commented on PHOENIX-1751: --- It appears that heartbeats are only performed if the scan

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436001#comment-15436001 ] James Taylor commented on PHOENIX-1751: --- bq. What did you do to get the test to pass? Sorry - left

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435991#comment-15435991 ] James Taylor commented on PHOENIX-2909: --- bq. How does this update statement interact with

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435860#comment-15435860 ] Cameron Hatfield commented on PHOENIX-2909: --- I would agree, and I would say is a good argument

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435728#comment-15435728 ] James Taylor commented on PHOENIX-2909: --- Wouldn't we be in the same boat with MERGE statement

[jira] [Comment Edited] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435680#comment-15435680 ] Cameron Hatfield edited comment on PHOENIX-2909 at 8/24/16 9:04 PM:

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435680#comment-15435680 ] Cameron Hatfield commented on PHOENIX-2909: --- I like the idea of this (of course), but the

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435639#comment-15435639 ] James Taylor commented on PHOENIX-2909: --- The two aren't mutually exclusive. We can still surface

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435629#comment-15435629 ] Cameron Hatfield commented on PHOENIX-2909: --- What has changed since the original discussion

[jira] [Commented] (PHOENIX-2909) Surface checkAndPut through UPDATE statement

[ https://issues.apache.org/jira/browse/PHOENIX-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435628#comment-15435628 ] Cameron Hatfield commented on PHOENIX-2909: --- Previous discussion on check-and-put > Surface

[jira] [Comment Edited] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435607#comment-15435607 ] Andrew Purtell edited comment on PHOENIX-1751 at 8/24/16 8:22 PM: -- bq.

[jira] [Comment Edited] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435607#comment-15435607 ] Andrew Purtell edited comment on PHOENIX-1751 at 8/24/16 8:22 PM: -- bq.

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435607#comment-15435607 ] Andrew Purtell commented on PHOENIX-1751: - bq. Here's the patch for 0.98 with the test passing

[jira] [Comment Edited] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435607#comment-15435607 ] Andrew Purtell edited comment on PHOENIX-1751 at 8/24/16 8:21 PM: -- bq.

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435590#comment-15435590 ] Hadoop QA commented on PHOENIX-1751: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1751: -- Attachment: PHOENIX-1751-0.98.patch Here's the patch for 0.98 with the test passing. Unknown

[jira] [Updated] (PHOENIX-3203) Tenant cache lookup in Global Cache fails in certain conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3203: Summary: Tenant cache lookup in Global Cache fails in certain conditions (was: Upserting

[jira] [Updated] (PHOENIX-3203) Upserting rows to a table with a mutable index using a tenant specific connection fails

[ https://issues.apache.org/jira/browse/PHOENIX-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3203: Description: In ServerCachingEndpointImpl.addServerCache we look up the tenant cache

Re: Issues while Running Apache Phoenix against TPC-H data

Thanks Mujtaba… Regards, John > On Aug 24, 2016, at 2:29 PM, Mujtaba Chohan wrote: > > That sounds about right for loading CSV directly on a 5-8 node cluster. As > Gabriel/James mentioned in another thread, CSVBulkLoadTool with pre-split > table might offer significantly

Re: Issues while Running Apache Phoenix against TPC-H data

That sounds about right for loading CSV directly on a 5-8 node cluster. As Gabriel/James mentioned in another thread, CSVBulkLoadTool with pre-split table might offer significantly better performance for large datasets. On Tue, Aug 23, 2016 at 2:17 PM, John Leach wrote:

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435459#comment-15435459 ] James Taylor commented on PHOENIX-1751: --- The new unit test is failing in 0.98 (but passing in 1.1

[jira] [Commented] (PHOENIX-3204) Scanner lease timeout exception during UPSERT INTO t1 SELECT * FROM t2

[ https://issues.apache.org/jira/browse/PHOENIX-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435421#comment-15435421 ] James Taylor commented on PHOENIX-3204: --- Would you have some spare cycles to take a look at this

[jira] [Commented] (PHOENIX-3204) Scanner lease timeout exception during UPSERT INTO t1 SELECT * FROM t2

[ https://issues.apache.org/jira/browse/PHOENIX-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435417#comment-15435417 ] Lars Hofhansl commented on PHOENIX-3204: Note... All hostnames changes to not reflect our real

[jira] [Created] (PHOENIX-3204) Scanner lease timeout exception during UPSERT INTO t1 SELECT * FROM t2

Lars Hofhansl created PHOENIX-3204: -- Summary: Scanner lease timeout exception during UPSERT INTO t1 SELECT * FROM t2 Key: PHOENIX-3204 URL: https://issues.apache.org/jira/browse/PHOENIX-3204

[jira] [Commented] (PHOENIX-1751) Perform aggregations, sorting, etc, in the preScannerNext instead of postScannerOpen

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435365#comment-15435365 ] Hudson commented on PHOENIX-1751: - SUCCESS: Integrated in Jenkins build Phoenix-master #1370 (See

[GitHub] phoenix issue #195: Zipkin

Github user mujtabachohan commented on the issue: https://github.com/apache/phoenix/pull/195 Please merge with phoenix-tracing-webapp and name it phoenix-tracing. Use default properties for zipkin configuration in case they are not configurable. --- If your project is set up for it,

[GitHub] phoenix issue #195: Zipkin

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/195 Please squash all commits into a single commit. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] phoenix pull request #195: Zipkin

Github user mujtabachohan commented on a diff in the pull request: https://github.com/apache/phoenix/pull/195#discussion_r76099712 --- Diff: phoenix-zipkin/pom.xml --- @@ -0,0 +1,102 @@ + + + + http://maven.apache.org/POM/4.0.0;

[GitHub] phoenix pull request #195: Zipkin

Github user mujtabachohan commented on a diff in the pull request: https://github.com/apache/phoenix/pull/195#discussion_r76099515 --- Diff: phoenix-zipkin/pom.xml --- @@ -0,0 +1,102 @@ + + + + http://maven.apache.org/POM/4.0.0;

[GitHub] phoenix pull request #195: Zipkin

Github user mujtabachohan commented on a diff in the pull request: https://github.com/apache/phoenix/pull/195#discussion_r76099342 --- Diff: phoenix-zipkin/pom.xml --- @@ -0,0 +1,102 @@ + + + + http://maven.apache.org/POM/4.0.0;

high client cpu usage

Seeing higher than expected CPU/MEM usage for the java process started by the sqlline.py client. From top: top - 14:37:32 up 7 days, 22:15, 2 users, load average: 25.52, 9.74, 7.89 Tasks: 509 total, 1 running, 508 sleeping, 0 stopped, 0 zombie Cpu(s): 61.2%us, 6.3%sy, 0.0%ni, 31.0%id,

[jira] [Commented] (PHOENIX-3199) ServerCacheClient would send cache to all regions unnecessarily once it should send cache to the first region

[ https://issues.apache.org/jira/browse/PHOENIX-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434799#comment-15434799 ] Hadoop QA commented on PHOENIX-3199: {color:red}-1 overall{color}. Here are the results of testing

[GitHub] phoenix pull request #195: Zipkin

GitHub user AyolaJayamaha opened a pull request: https://github.com/apache/phoenix/pull/195 Zipkin Flipping zipkin chart on vertical axis would be done on the zipkin codebase. The zipkin codebase does not support date/time in milliseconds. You can merge this pull request into

[jira] [Updated] (PHOENIX-3203) Upserting rows to a table with a mutable index using a tenant specific connection fails

[ https://issues.apache.org/jira/browse/PHOENIX-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3203: --- Fix Version/s: (was: 4.8.0) 4.8.1 4.9.0 >

[jira] [Commented] (PHOENIX-2900) Unable to find hash cache once a salted table 's first region has split

[ https://issues.apache.org/jira/browse/PHOENIX-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434489#comment-15434489 ] chenglei commented on PHOENIX-2900: --- I create a new issue

[jira] [Commented] (PHOENIX-3199) ServerCacheClient would send cache to all regions unnecessarily once it should send cache to the first region

[ https://issues.apache.org/jira/browse/PHOENIX-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434462#comment-15434462 ] Hadoop QA commented on PHOENIX-3199: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (PHOENIX-3148) Reduce size of PTable so that more tables can be cached in the metada cache.

[ https://issues.apache.org/jira/browse/PHOENIX-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434431#comment-15434431 ] Hudson commented on PHOENIX-3148: - SUCCESS: Integrated in Jenkins build Phoenix-master #1369 (See

[jira] [Updated] (PHOENIX-3203) Upserting rows to a table with a mutable index using a tenant specific connection fails

[ https://issues.apache.org/jira/browse/PHOENIX-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3203: Description: In ServerCachingEndpointImpl.addServerCache we look up the tenant cache

[jira] [Created] (PHOENIX-3203) Upserting rows to a table with a mutable index using a tenant specific connection fails

Thomas D'Silva created PHOENIX-3203: --- Summary: Upserting rows to a table with a mutable index using a tenant specific connection fails Key: PHOENIX-3203 URL: https://issues.apache.org/jira/browse/PHOENIX-3203

[jira] [Updated] (PHOENIX-3199) ServerCacheClient would send cache to all regions unnecessarily once it should send cache to the first region

[ https://issues.apache.org/jira/browse/PHOENIX-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3199: -- Attachment: PHOENIX-3199_v1.patch > ServerCacheClient would send cache to all regions unnecessarily

[jira] [Updated] (PHOENIX-3199) ServerCacheClient would send cache to all regions unnecessarily once it should send cache to the first region

[ https://issues.apache.org/jira/browse/PHOENIX-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3199: -- Attachment: (was: PHOENIX-3199.patch) > ServerCacheClient would send cache to all regions

[jira] [Updated] (PHOENIX-3148) Reduce size of PTable so that more tables can be cached in the metada cache.

[ https://issues.apache.org/jira/browse/PHOENIX-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-3148: Fix Version/s: 4.9.0 > Reduce size of PTable so that more tables can be cached in the

[jira] [Resolved] (PHOENIX-3148) Reduce size of PTable so that more tables can be cached in the metada cache.

[ https://issues.apache.org/jira/browse/PHOENIX-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva resolved PHOENIX-3148. - Resolution: Fixed > Reduce size of PTable so that more tables can be cached in the