[GitHub] phoenix pull request #236: PHOENIX-3654 Load Balancer for thin client

Github user joshelser commented on a diff in the pull request: https://github.com/apache/phoenix/pull/236#discussion_r122508226 --- Diff: phoenix-queryserver/src/main/java/org/apache/phoenix/queryserver/server/QueryServer.java --- @@ -233,16 +240,29 @@ public int run(String[]

[jira] [Commented] (PHOENIX-3940) NullPointerException on PERCENTILE_CONT over an empty result set

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

[GitHub] phoenix pull request #262: PHOENIX 153 implement TABLESAMPLE clause

GitHub user aertoria opened a pull request: https://github.com/apache/phoenix/pull/262 PHOENIX 153 implement TABLESAMPLE clause table sampling on each Table basis (at the 'FROM' part of the query). Sample size decided by the input sampling rate applies on Primary Key's frequency.

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052238#comment-16052238 ] ASF GitHub Bot commented on PHOENIX-3654: - Github user rahulsIOT commented on a diff in the pull

[jira] [Commented] (PHOENIX-3946) Update phoenix-spark to use 2.0.2 version

[ https://issues.apache.org/jira/browse/PHOENIX-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052259#comment-16052259 ] Kanagha Pradha commented on PHOENIX-3946: - Thanks [~jmahonin]. So, I see spark 2.0.2 version and

[jira] [Updated] (PHOENIX-3942) Fix failing PhoenixMetricsIT test

[ https://issues.apache.org/jira/browse/PHOENIX-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karan Mehta updated PHOENIX-3942: - Attachment: PHOENIX-3942.001.patch Thanks [~samarthjain] for the review. Patch applies to

[GitHub] phoenix pull request #236: PHOENIX-3654 Load Balancer for thin client

Github user rahulsIOT commented on a diff in the pull request: https://github.com/apache/phoenix/pull/236#discussion_r122505939 --- Diff: phoenix-queryserver/src/main/java/org/apache/phoenix/queryserver/server/QueryServer.java --- @@ -233,16 +240,29 @@ public int run(String[]

[jira] [Commented] (PHOENIX-3654) Load Balancer for thin client

[ https://issues.apache.org/jira/browse/PHOENIX-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052254#comment-16052254 ] ASF GitHub Bot commented on PHOENIX-3654: - Github user joshelser commented on a diff in the pull

[GitHub] phoenix issue #262: PHOENIX 153 implement TABLESAMPLE clause

Github user aertoria commented on the issue: https://github.com/apache/phoenix/pull/262 @JamesRTaylor @gjacoby126 @samarthjain --- 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 this feature

[jira] [Comment Edited] (PHOENIX-153) Implement TABLESAMPLE clause

[ https://issues.apache.org/jira/browse/PHOENIX-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16044823#comment-16044823 ] Ethan Wang edited comment on PHOENIX-153 at 6/16/17 8:29 PM: - Spec of this

[jira] [Comment Edited] (PHOENIX-153) Implement TABLESAMPLE clause

[ https://issues.apache.org/jira/browse/PHOENIX-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16044823#comment-16044823 ] Ethan Wang edited comment on PHOENIX-153 at 6/16/17 8:29 PM: - Spec of this

[jira] [Updated] (PHOENIX-3948) Enable shorter time outs for server-side index writes

[ https://issues.apache.org/jira/browse/PHOENIX-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3948: -- Labels: globalMutableSecondaryIndex (was: indexImprovement) > Enable shorter time outs for

[jira] [Updated] (PHOENIX-3949) Stop index maintenance until INDEX_DISABLED_TIMESTAMP is cleared

[ https://issues.apache.org/jira/browse/PHOENIX-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3949: -- Labels: globalMutableSecondaryIndex (was: indexImprovement) > Stop index maintenance until

[jira] [Updated] (PHOENIX-3947) Increase scan time out for partial index rebuild

[ https://issues.apache.org/jira/browse/PHOENIX-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3947: -- Labels: globalMutableSecondaryIndex (was: indexImprovement) > Increase scan time out for

[jira] [Commented] (PHOENIX-3390) Custom UDAF for HyperLogLogPlus

[ https://issues.apache.org/jira/browse/PHOENIX-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052489#comment-16052489 ] James Taylor commented on PHOENIX-3390: --- [~talktoswa...@gmail.com] - [~aertoria] is interested in

[jira] [Updated] (PHOENIX-3953) Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3953: -- Labels: globalMutableSecondaryIndex (was: ) > Clear INDEX_DISABLED_TIMESTAMP and disable

[jira] [Commented] (PHOENIX-3953) Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction

[ https://issues.apache.org/jira/browse/PHOENIX-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052420#comment-16052420 ] James Taylor commented on PHOENIX-3953: --- FYI, [~samarthjain]. > Clear INDEX_DISABLED_TIMESTAMP

[jira] [Created] (PHOENIX-3953) Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction

James Taylor created PHOENIX-3953: - Summary: Clear INDEX_DISABLED_TIMESTAMP and disable index on compaction Key: PHOENIX-3953 URL: https://issues.apache.org/jira/browse/PHOENIX-3953 Project: Phoenix

[jira] [Commented] (PHOENIX-3933) Start row is skipped when iterating a result set with ScanUtil.setReversed(scan)

[ https://issues.apache.org/jira/browse/PHOENIX-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052594#comment-16052594 ] Biju Nair commented on PHOENIX-3933: Thanks [~giacomotaylor]. I was trying to make changes to the

[jira] [Commented] (PHOENIX-1505) Support defining a VIEW over multiple tables

[ https://issues.apache.org/jira/browse/PHOENIX-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052455#comment-16052455 ] Julian Hyde commented on PHOENIX-1505: -- In the Calcite branch, defining views and expanding them in

[jira] [Commented] (PHOENIX-1505) Support defining a VIEW over multiple tables

[ https://issues.apache.org/jira/browse/PHOENIX-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052467#comment-16052467 ] James Taylor commented on PHOENIX-1505: --- Indexes on views are for updatable views that allow

[jira] [Updated] (PHOENIX-3184) Wrap HBase calls in separate thread to reliably honor query timeout

[ https://issues.apache.org/jira/browse/PHOENIX-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3184: -- Labels: SFDC (was: ) > Wrap HBase calls in separate thread to reliably honor query timeout >

[jira] [Commented] (PHOENIX-3534) Support multi region SYSTEM.CATALOG table

[ https://issues.apache.org/jira/browse/PHOENIX-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052510#comment-16052510 ] ASF GitHub Bot commented on PHOENIX-3534: - Github user JamesRTaylor commented on the issue:

[jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL

[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052533#comment-16052533 ] James Taylor commented on PHOENIX-3817: --- I'm probably not the best person to review this (though

[jira] [Commented] (PHOENIX-3184) Wrap HBase calls in separate thread to reliably honor query timeout

[ https://issues.apache.org/jira/browse/PHOENIX-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052459#comment-16052459 ] James Taylor commented on PHOENIX-3184: --- [~akshita.malhotra] - here's another timeout related

[jira] [Updated] (PHOENIX-3184) Wrap HBase calls in separate thread to reliably honor query timeout

[ https://issues.apache.org/jira/browse/PHOENIX-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3184: -- Description: If an HBase call stalls, we don't detect and account for this in our query

Re: Simple and complex views

Thanks, I've added some comments to https://issues.apache.org/jira/browse/PHOENIX-1505. I'd also like to understand why Phoenix needs indexes on views (most DBMSs only allow indexes on base tables). We can cover that in the same discussion. On Fri, Jun 16, 2017 at 8:05 AM, James Taylor

[jira] [Created] (PHOENIX-3955) Indexes should inherit the KEEP_DELETED_CELLS and TTL properties from the base table

Samarth Jain created PHOENIX-3955: - Summary: Indexes should inherit the KEEP_DELETED_CELLS and TTL properties from the base table Key: PHOENIX-3955 URL: https://issues.apache.org/jira/browse/PHOENIX-3955

[jira] [Commented] (PHOENIX-3807) Add server level metrics for secondary indexes

[ https://issues.apache.org/jira/browse/PHOENIX-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052580#comment-16052580 ] Josh Elser commented on PHOENIX-3807: - Just getting around to taking a look: bq. Count of deployed

[jira] [Updated] (PHOENIX-3954) Message displayed during "Alter view" is not accurate

[ https://issues.apache.org/jira/browse/PHOENIX-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Wang updated PHOENIX-3954: Summary: Message displayed during "Alter view" is not accurate (was: Message displayed during

[jira] [Created] (PHOENIX-3954) Message displayed during "Alter view" is not correct

Ethan Wang created PHOENIX-3954: --- Summary: Message displayed during "Alter view" is not correct Key: PHOENIX-3954 URL: https://issues.apache.org/jira/browse/PHOENIX-3954 Project: Phoenix

[jira] [Comment Edited] (PHOENIX-418) Support approximate COUNT DISTINCT

[ https://issues.apache.org/jira/browse/PHOENIX-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052446#comment-16052446 ] Ethan Wang edited comment on PHOENIX-418 at 6/16/17 10:27 PM: -- Reply to

[jira] [Commented] (PHOENIX-153) Implement TABLESAMPLE clause

[ https://issues.apache.org/jira/browse/PHOENIX-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052505#comment-16052505 ] James Taylor commented on PHOENIX-153: -- +1. Do you have something you can point us to for the

[jira] [Updated] (PHOENIX-3817) VerifyReplication using SQL

[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3817: -- Fix Version/s: 4.12.0 > VerifyReplication using SQL > --- > >

[jira] [Commented] (PHOENIX-418) Support approximate COUNT DISTINCT

[ https://issues.apache.org/jira/browse/PHOENIX-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052447#comment-16052447 ] Ethan Wang commented on PHOENIX-418: What is the current state of this jira? @maghamravikiran

[jira] [Commented] (PHOENIX-418) Support approximate COUNT DISTINCT

[ https://issues.apache.org/jira/browse/PHOENIX-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052446#comment-16052446 ] Ethan Wang commented on PHOENIX-418: Reply to [~pctony]: also in Blink DB, they have similar

[jira] [Commented] (PHOENIX-153) Implement TABLESAMPLE clause

[ https://issues.apache.org/jira/browse/PHOENIX-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052472#comment-16052472 ] Julian Hyde commented on PHOENIX-153: - Since Calcite already supports TABLESAMPLE let's save

[GitHub] phoenix issue #248: Phoenix 3534

Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/248 Looks like there are still conflicts, @churrodog. Would you mind amending your commit message to "PHOENIX-3534 Support multi region SYSTEM.CATALOG table" so that the JIRA is linked to the PR?

[jira] [Commented] (PHOENIX-3928) Consider retrying once after any SQLException

[ https://issues.apache.org/jira/browse/PHOENIX-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052301#comment-16052301 ] Thomas D'Silva commented on PHOENIX-3928: - [~sukuna...@gmail.com], can you upload a patch with

[jira] [Commented] (PHOENIX-3942) Fix failing PhoenixMetricsIT test

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

[jira] [Commented] (PHOENIX-3928) Consider retrying once after any SQLException

[ https://issues.apache.org/jira/browse/PHOENIX-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051498#comment-16051498 ] James Taylor commented on PHOENIX-3928: --- Sounds like it might be a bug. Does the server send over

[jira] [Updated] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Jha updated PHOENIX-3952: -- Description: If I'm joining two tables, say inner join, on an OR based condition, then the following

[jira] [Updated] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Jha updated PHOENIX-3952: -- Description: If I'm joining two tables, say inner join, on an OR based condition, then the following

[jira] [Updated] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Jha updated PHOENIX-3952: -- Description: If I'm joining two tables, say inner join, on an OR based condition, then the following

[jira] [Created] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

Aman Jha created PHOENIX-3952: - Summary: "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions Key: PHOENIX-3952 URL:

Re: Simple and complex views

Yes, that's the case today (documented here[1]). The two relevant JIRAs are PHOENIX-1505 and PHOENIX-1506. It'd be great if someone was interested in pursuing these. If so, let's discuss on the JIRAs. James [1] http://phoenix.apache.org/views.html#Limitations On Thu, Jun 15, 2017 at 9:20 PM

[jira] [Commented] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052052#comment-16052052 ] James Taylor commented on PHOENIX-3952: --- That's a known limitation of hash joins - only equi joins

[jira] [Commented] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052072#comment-16052072 ] Aman Jha commented on PHOENIX-3952: --- [~jamestaylor] still getting the same error using the suggested

[jira] [Comment Edited] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052072#comment-16052072 ] Aman Jha edited comment on PHOENIX-3952 at 6/16/17 4:12 PM: [~jamestaylor]

[jira] [Comment Edited] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052072#comment-16052072 ] Aman Jha edited comment on PHOENIX-3952 at 6/16/17 4:12 PM: [~jamestaylor]

[jira] [Commented] (PHOENIX-3952) "Ambiguous or non-equi join condition specified" Exception thrown for usage of OR expression in join conditions

[ https://issues.apache.org/jira/browse/PHOENIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052088#comment-16052088 ] James Taylor commented on PHOENIX-3952: --- Your can try rewriting the query using UNION instead of

[jira] [Commented] (PHOENIX-3757) System mutex table not being created in SYSTEM namespace when namespace mapping is enabled

[ https://issues.apache.org/jira/browse/PHOENIX-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052125#comment-16052125 ] Josh Elser commented on PHOENIX-3757: - bq. Was this committed, Josh Elser and if not should it be?