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

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432189#comment-15432189 ] Samarth Jain edited comment on PHOENIX-1751 at 8/23/16 5:53 AM:

[GitHub] phoenix pull request #193: Query builder

GitHub user AyolaJayamaha opened a pull request: https://github.com/apache/phoenix/pull/193 Query builder You can merge this pull request into a Git repository by running: $ git pull https://github.com/AyolaJayamaha/phoenix query-builder Alternatively you can review and

[jira] [Commented] (PHOENIX-930) duplicated columns cause query exception and drop table exception

[ https://issues.apache.org/jira/browse/PHOENIX-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432155#comment-15432155 ] Samarth Jain commented on PHOENIX-930: -- +1 > duplicated columns cause query exception and drop

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

[ https://issues.apache.org/jira/browse/PHOENIX-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432116#comment-15432116 ] James Taylor commented on PHOENIX-1751: --- [~samarthjain]? > Perform aggregations, sorting, etc, in

[jira] [Commented] (PHOENIX-930) duplicated columns cause query exception and drop table exception

[ https://issues.apache.org/jira/browse/PHOENIX-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432115#comment-15432115 ] James Taylor commented on PHOENIX-930: -- [~samarthjain]? > duplicated columns cause query exception

Re: 4.8.1, 4.9.0, 4.9.1, and 4.10.0

Thanks Josh. Just to be clear, I did not mean that all issues should be assigned to 4.9.0 and 4.8.1, but only those issues that represent minor and backwards compatible fixes. (I know you know this, but for the sake of others). -- Lars From: Josh Elser To:

[jira] [Resolved] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-3195. Resolution: Fixed Pushed addendum to all branches. > Slight safety improvement for using

[jira] [Commented] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432055#comment-15432055 ] Lars Hofhansl commented on PHOENIX-3195: Cool. Thanks [~giacomotaylor]. > Slight safety

[jira] [Updated] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3195: -- Attachment: PHOENIX-3195_partial.patch [~lhofhansl] - here's a patch that'll fix the test

[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=15431927#comment-15431927 ] James Taylor commented on PHOENIX-3148: --- Thanks for the patch and the perf analysis. Looks very

[jira] [Commented] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431880#comment-15431880 ] Lars Hofhansl commented on PHOENIX-3195: bq.

[jira] [Reopened] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reopened PHOENIX-3195: Oops... Test failure... My bad. Will fix ASAP. > Slight safety improvement for using

[jira] [Updated] (PHOENIX-3197) DATE/TIMESTAMP comparison involving rowkey column broken

[ https://issues.apache.org/jira/browse/PHOENIX-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated PHOENIX-3197: -- Attachment: test2.sql test1.sql Test files to run with psql.py >

[jira] [Created] (PHOENIX-3197) DATE/TIMESTAMP comparison involving rowkey column broken

Nick Dimiduk created PHOENIX-3197: - Summary: DATE/TIMESTAMP comparison involving rowkey column broken Key: PHOENIX-3197 URL: https://issues.apache.org/jira/browse/PHOENIX-3197 Project: Phoenix

[jira] [Updated] (PHOENIX-3196) Array Index Out Of Bounds Exception

[ https://issues.apache.org/jira/browse/PHOENIX-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nithin updated PHOENIX-3196: Description: Data Set Size - Table with 156 Million Rows and 200 Columns Seems like this issue is

[jira] [Resolved] (PHOENIX-2916) Need a client-side level property to control write timeout

[ https://issues.apache.org/jira/browse/PHOENIX-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2916. --- Resolution: Not A Problem If HBase has a new config property to set the write RPC timeout,

[jira] [Updated] (PHOENIX-2916) Need a client-side level property to control write timeout

[ https://issues.apache.org/jira/browse/PHOENIX-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2916: -- Assignee: (was: prakul agarwal) > Need a client-side level property to control write

[jira] [Updated] (PHOENIX-3196) Array Index Out Of Bounds Exception

[ https://issues.apache.org/jira/browse/PHOENIX-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nithin updated PHOENIX-3196: Fix Version/s: (was: 4.8.1) 4.7.0 > Array Index Out Of Bounds Exception >

[jira] [Updated] (PHOENIX-3196) Array Index Out Of Bounds Exception

[ https://issues.apache.org/jira/browse/PHOENIX-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nithin updated PHOENIX-3196: Description: Data Set Size - Table with 156 Million Rows and 200 Columns Seems like this issue is

[jira] [Created] (PHOENIX-3196) Array Index Out Of Bounds Exception

Nithin created PHOENIX-3196: --- Summary: Array Index Out Of Bounds Exception Key: PHOENIX-3196 URL: https://issues.apache.org/jira/browse/PHOENIX-3196 Project: Phoenix Issue Type: Bug Affects

[jira] [Comment Edited] (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=15431735#comment-15431735 ] Thomas D'Silva edited comment on PHOENIX-3148 at 8/22/16 10:39 PM: ---

[jira] [Comment Edited] (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=15431735#comment-15431735 ] Thomas D'Silva edited comment on PHOENIX-3148 at 8/22/16 10:37 PM: ---

[jira] [Comment Edited] (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=15431735#comment-15431735 ] Thomas D'Silva edited comment on PHOENIX-3148 at 8/22/16 10:36 PM: ---

[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: Attachment: comparison.png PHOENIX-3148-v3.patch [~jamestaylor] I have

[jira] [Commented] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

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

[jira] [Resolved] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-3195. Resolution: Fixed Thanks [~giacomotaylor]. Pushed to 4.8-xxx, 4.x-xxx, and master. >

[jira] [Commented] (PHOENIX-808) Create snapshot of SYSTEM.CATALOG prior to upgrade and restore on any failure

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

[jira] [Commented] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431407#comment-15431407 ] James Taylor commented on PHOENIX-3195: --- +1 > Slight safety improvement for using

[jira] [Commented] (PHOENIX-3195) Slight safety improvement for using DistinctPrefixFilter

[ https://issues.apache.org/jira/browse/PHOENIX-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431310#comment-15431310 ] Lars Hofhansl commented on PHOENIX-3195: I'm just going to commit this. Safe trivial change. >

[jira] [Updated] (PHOENIX-808) Create snapshot of SYSTEM.CATALOG prior to upgrade and restore on any failure

[ https://issues.apache.org/jira/browse/PHOENIX-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-808: - Summary: Create snapshot of SYSTEM.CATALOG prior to upgrade and restore on any failure (was:

[jira] [Commented] (PHOENIX-3048) Wire up HTTP Basic/Digest authentication from Avatica into PQS

[ https://issues.apache.org/jira/browse/PHOENIX-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430933#comment-15430933 ] Josh Elser commented on PHOENIX-3048: - Not tagging for 4.8.1 as it is net-new functionality. > Wire

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

[ https://issues.apache.org/jira/browse/PHOENIX-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2991: Fix Version/s: 4.8.1 > Add missing documentation for functions >

[jira] [Updated] (PHOENIX-2990) Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance

[ https://issues.apache.org/jira/browse/PHOENIX-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2990: Fix Version/s: 4.8.1 > Ensure documentation on "time/date" datatypes/functions acknowledge lack

Re: 4.8.1, 4.9.0, 4.9.1, and 4.10.0

For the lazy: https://s.apache.org/KxB1 (JIRA search results for all unresolved issues with fixVersion=4.9.0, but not fixVersion=4.8.1 too) la...@apache.org wrote: Hi All, as we're two active branches right now, it is important to remember (1) that fixes are pushed to both 4.8xxx and 4.x

Re: [DISCUSS] Drop HBase 1.0 support for 4.9

+1 la...@apache.org wrote: The HBase 1.0.x branch has been EOL'd, I propose we drop support for it with Phoenix 4.9.I'd also propose that should HBase have a stable 1.3.x release soon, we should support it with Phoenix 4.9. -- Lars

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

It looks like you guys already have most of the TPCH queries running based on Enis’s talk in Ireland this year. Very cool. (Slide 20: Phoenix can execute most of the TPC-H queries!) Regards, John Leach > On Aug 19, 2016, at 8:28 PM, Nick Dimiduk wrote: > > It's