[jira] [Resolved] (PHOENIX-2904) Fix UPDATE STATISTICS documentation

[ https://issues.apache.org/jira/browse/PHOENIX-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2904. --- Resolution: Fixed > Fix UPDATE STATISTICS documentation > --

[jira] [Commented] (PHOENIX-2925) CsvBulkloadTool not working properly if there are multiple local indexes to the same table(After PHOENIX-1973)

[ https://issues.apache.org/jira/browse/PHOENIX-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295422#comment-15295422 ] James Taylor commented on PHOENIX-2925: --- Rather than have another boolean flag for

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_v1.patch Here's a patch the handles splits for all cases, including a

[jira] [Commented] (PHOENIX-2925) CsvBulkloadTool not working properly if there are multiple local indexes to the same table(After PHOENIX-1973)

[ https://issues.apache.org/jira/browse/PHOENIX-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295722#comment-15295722 ] James Taylor commented on PHOENIX-2925: --- I like [~sergey.soldatov]'s idea. > CsvB

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295793#comment-15295793 ] James Taylor commented on PHOENIX-2886: --- My point was that checking for a coerce a

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295795#comment-15295795 ] James Taylor commented on PHOENIX-2903: --- Thanks, [~rajeshbabu]. So do we not need

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295827#comment-15295827 ] James Taylor commented on PHOENIX-2903: --- How does the region.startRegionOperation(

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295837#comment-15295837 ] James Taylor commented on PHOENIX-2886: --- Please let me know what query you're runn

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295846#comment-15295846 ] James Taylor commented on PHOENIX-2903: --- But only when we get to the row that's ou

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295877#comment-15295877 ] James Taylor commented on PHOENIX-2903: --- Yes, just talking about those lines and t

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296477#comment-15296477 ] James Taylor commented on PHOENIX-2886: --- [~ayingshu] - I don't understand the cont

[jira] [Commented] (PHOENIX-2925) CsvBulkloadTool not working properly if there are multiple local indexes to the same table(After PHOENIX-1973)

[ https://issues.apache.org/jira/browse/PHOENIX-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296487#comment-15296487 ] James Taylor commented on PHOENIX-2925: --- +1. Nice work, [~sergey.soldatov]. > Csv

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296803#comment-15296803 ] James Taylor commented on PHOENIX-2921: --- [~mujtabachohan] - are you doing it in lo

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297127#comment-15297127 ] James Taylor commented on PHOENIX-2921: --- Does the transaction manager require Guav

[jira] [Commented] (PHOENIX-2931) Phoenix client asks users to provide configs in cli that are present on the machine in hbase conf

[ https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297386#comment-15297386 ] James Taylor commented on PHOENIX-2931: --- Sounds complicated and hard to maintain.

[jira] [Commented] (PHOENIX-2931) Phoenix client asks users to provide configs in cli that are present on the machine in hbase conf

[ https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297429#comment-15297429 ] James Taylor commented on PHOENIX-2931: --- Not sure. This sounds messy. Do you have

[jira] [Commented] (PHOENIX-2931) Phoenix client asks users to provide configs in cli that are present on the machine in hbase conf

[ https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297493#comment-15297493 ] James Taylor commented on PHOENIX-2931: --- That seems more clear if we don't rely on

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297494#comment-15297494 ] James Taylor commented on PHOENIX-2886: --- [~sergey.soldatov] - if you have any spar

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_v2.patch Thanks for the review, [~rajeshbabu]. I've removed the unnec

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297537#comment-15297537 ] James Taylor commented on PHOENIX-2886: --- Did you do all the other stuff I recommen

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297584#comment-15297584 ] James Taylor commented on PHOENIX-2886: --- Did you update the tests too? Upload a pa

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_v3.patch Fixed a few issues and removed some unnecessary (and incorre

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Fix Version/s: 4.8.0 > Handle split during scan for row key ordered aggregations > ---

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298348#comment-15298348 ] James Taylor commented on PHOENIX-2903: --- Tests pass locally. [~samarthjain] - woul

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298412#comment-15298412 ] James Taylor commented on PHOENIX-2903: --- Yes, for non aggregate queries we always

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300059#comment-15300059 ] James Taylor commented on PHOENIX-2936: --- Will this include only antr runtime or al

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301145#comment-15301145 ] James Taylor commented on PHOENIX-2936: --- +1 on the patch. Thanks, [~sergey.soldato

[jira] [Commented] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301540#comment-15301540 ] James Taylor commented on PHOENIX-2940: --- To expand on what Josh said, a simple sol

[jira] [Commented] (PHOENIX-2941) Alternative means of propagating schema changes

[ https://issues.apache.org/jira/browse/PHOENIX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301559#comment-15301559 ] James Taylor commented on PHOENIX-2941: --- The new UPDATE_CACHE_FREQUENCY property[1

[jira] [Commented] (PHOENIX-1734) Local index improvements

[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302227#comment-15302227 ] James Taylor commented on PHOENIX-1734: --- +1 > Local index improvements >

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302281#comment-15302281 ] James Taylor commented on PHOENIX-2903: --- bq. In ScanUtil#setLocalIndexAttributes w

[jira] [Commented] (PHOENIX-2936) Missing antlr runtime on server side after PHOENIX-2908

[ https://issues.apache.org/jira/browse/PHOENIX-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302836#comment-15302836 ] James Taylor commented on PHOENIX-2936: --- +1 > Missing antlr runtime on server sid

[jira] [Updated] (PHOENIX-2924) Remove staging repository once Apache Tephra 0.8.0 is released

[ https://issues.apache.org/jira/browse/PHOENIX-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2924: -- Attachment: PHOENIX-2924.patch > Remove staging repository once Apache Tephra 0.8.0 is release

[jira] [Updated] (PHOENIX-2814) WhereOptimizer does not handle multi-tenant local index correctly when connection is non-tenant-specific

[ https://issues.apache.org/jira/browse/PHOENIX-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2814: -- Fix Version/s: 4.8.0 > WhereOptimizer does not handle multi-tenant local index correctly when

[jira] [Updated] (PHOENIX-2920) Incorrect Queries on Multi-tenant tables with WHERE clause containing Row Value Constructor

[ https://issues.apache.org/jira/browse/PHOENIX-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2920: -- Assignee: Samarth Jain > Incorrect Queries on Multi-tenant tables with WHERE clause containing

[jira] [Updated] (PHOENIX-2920) Incorrect Queries on Multi-tenant tables with WHERE clause containing Row Value Constructor

[ https://issues.apache.org/jira/browse/PHOENIX-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2920: -- Fix Version/s: 4.8.0 > Incorrect Queries on Multi-tenant tables with WHERE clause containing R

[jira] [Updated] (PHOENIX-2814) WhereOptimizer does not handle multi-tenant local index correctly when connection is non-tenant-specific

[ https://issues.apache.org/jira/browse/PHOENIX-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2814: -- Assignee: Samarth Jain > WhereOptimizer does not handle multi-tenant local index correctly whe

[jira] [Updated] (PHOENIX-2920) Incorrect Queries on Multi-tenant tables with WHERE clause containing Row Value Constructor

[ https://issues.apache.org/jira/browse/PHOENIX-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2920: -- Labels: SFDC (was: ) > Incorrect Queries on Multi-tenant tables with WHERE clause containing

[jira] [Commented] (PHOENIX-2943) Performance of parallel order by query is > 30X slower than serial execution

[ https://issues.apache.org/jira/browse/PHOENIX-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302903#comment-15302903 ] James Taylor commented on PHOENIX-2943: --- Is this a regression from 4.7.0, [~mujtab

[jira] [Commented] (PHOENIX-2942) Incorrect results for order by queries

[ https://issues.apache.org/jira/browse/PHOENIX-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302904#comment-15302904 ] James Taylor commented on PHOENIX-2942: --- Is this a regression from 4.7.0, [~mujtab

[jira] [Commented] (PHOENIX-2901) If namespaces are enabled, check for existence of schema when sequence created

[ https://issues.apache.org/jira/browse/PHOENIX-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302915#comment-15302915 ] James Taylor commented on PHOENIX-2901: --- Thanks for the patch, [~an...@apache.org]

[jira] [Updated] (PHOENIX-2896) Support encoded column qualifiers per column family

[ https://issues.apache.org/jira/browse/PHOENIX-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2896: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Support encoded column qualifiers p

[jira] [Commented] (PHOENIX-2596) Asynchronous Local Index is not available

[ https://issues.apache.org/jira/browse/PHOENIX-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302928#comment-15302928 ] James Taylor commented on PHOENIX-2596: --- [~rajeshbabu] - this probably be an impor

[jira] [Resolved] (PHOENIX-2761) Upgrade Hadoop version in poms

[ https://issues.apache.org/jira/browse/PHOENIX-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2761. --- Resolution: Fixed Assignee: James Taylor > Upgrade Hadoop version in poms > --

[jira] [Updated] (PHOENIX-2639) LIKE query against ARRAY of VARCHAR

[ https://issues.apache.org/jira/browse/PHOENIX-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2639: -- Fix Version/s: (was: 4.8.0) 4.9.0 > LIKE query against ARRAY of VARCHAR

[jira] [Updated] (PHOENIX-2675) Allow stats to be configured on a table-by-table basis

[ https://issues.apache.org/jira/browse/PHOENIX-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2675: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Allow stats to be configured on a t

[jira] [Updated] (PHOENIX-2565) Store data for immutable tables in single KeyValue

[ https://issues.apache.org/jira/browse/PHOENIX-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2565: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Store data for immutable tables in

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302941#comment-15302941 ] James Taylor commented on PHOENIX-2535: --- [~sergey.soldatov]? > Create shaded clie

[jira] [Updated] (PHOENIX-2378) Use your parallelized two level heap implementation to perform a client-side sort

[ https://issues.apache.org/jira/browse/PHOENIX-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2378: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Use your parallelized two level hea

[jira] [Updated] (PHOENIX-2277) Indexes on tenant views not working correctly

[ https://issues.apache.org/jira/browse/PHOENIX-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2277: -- Labels: SFDC verify (was: verify) > Indexes on tenant views not working correctly > -

[jira] [Updated] (PHOENIX-2277) Indexes on tenant views not working correctly

[ https://issues.apache.org/jira/browse/PHOENIX-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2277: -- Assignee: Samarth Jain > Indexes on tenant views not working correctly > -

[jira] [Updated] (PHOENIX-2276) Creating index on a global view on a multi-tenant table fails with NPE

[ https://issues.apache.org/jira/browse/PHOENIX-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2276: -- Labels: SFDC verify (was: verify) > Creating index on a global view on a multi-tenant table f

[jira] [Updated] (PHOENIX-2276) Creating index on a global view on a multi-tenant table fails with NPE

[ https://issues.apache.org/jira/browse/PHOENIX-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2276: -- Assignee: Samarth Jain > Creating index on a global view on a multi-tenant table fails with NP

[jira] [Updated] (PHOENIX-2268) Pentaho BA query fails

[ https://issues.apache.org/jira/browse/PHOENIX-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2268: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Pentaho BA query fails > --

[jira] [Updated] (PHOENIX-2941) Alternative means of propagating schema changes

[ https://issues.apache.org/jira/browse/PHOENIX-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2941: -- Fix Version/s: 4.9.0 > Alternative means of propagating schema changes > -

[jira] [Updated] (PHOENIX-2939) MetaCache is easily thrashed with default settings

[ https://issues.apache.org/jira/browse/PHOENIX-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2939: -- Fix Version/s: 4.9.0 > MetaCache is easily thrashed with default settings > --

[jira] [Updated] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2940: -- Fix Version/s: 4.9.0 > Remove STATS RPCs from rowlock > -- > >

[jira] [Updated] (PHOENIX-2544) Update phoenix-spark PhoenixRecordWritable to use phoenix-core implementation

[ https://issues.apache.org/jira/browse/PHOENIX-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2544: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Update phoenix-spark PhoenixRecordW

[jira] [Updated] (PHOENIX-2507) Add IT for JsonBulkLoadTool

[ https://issues.apache.org/jira/browse/PHOENIX-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2507: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Add IT for JsonBulkLoadTool > -

[jira] [Updated] (PHOENIX-2501) BatchUpdateExecution typo in name, should extend java.sql.BatchUpdateException

[ https://issues.apache.org/jira/browse/PHOENIX-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2501: -- Fix Version/s: (was: 4.8.0) 4.9.0 > BatchUpdateExecution typo in name,

[jira] [Updated] (PHOENIX-2023) Build tgz only on release profile

[ https://issues.apache.org/jira/browse/PHOENIX-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2023: -- Fix Version/s: (was: 4.8.0) 4.9.0 > Build tgz only on release profile >

[jira] [Updated] (PHOENIX-2006) py scripts support for printing its command

[ https://issues.apache.org/jira/browse/PHOENIX-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2006: -- Fix Version/s: (was: 4.8.0) 4.9.0 > py scripts support for printing its

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305654#comment-15305654 ] James Taylor commented on PHOENIX-258: -- This is awesome, [~lhofhansl]! Thanks so muc

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306009#comment-15306009 ] James Taylor commented on PHOENIX-258: -- Thanks for the updates, [~lhofhansl]. That's

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306800#comment-15306800 ] James Taylor commented on PHOENIX-258: -- This is looking very good, [~lhofhansl]. A c

[jira] [Created] (PHOENIX-2950) Implement CRON job to start async index builds and restart failed jobs

James Taylor created PHOENIX-2950: - Summary: Implement CRON job to start async index builds and restart failed jobs Key: PHOENIX-2950 URL: https://issues.apache.org/jira/browse/PHOENIX-2950 Project: P

[jira] [Commented] (PHOENIX-1833) Optionally trigger MR job to build index automatically

[ https://issues.apache.org/jira/browse/PHOENIX-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306825#comment-15306825 ] James Taylor commented on PHOENIX-1833: --- Awesome, [~rvaleti] - thanks so much for

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306884#comment-15306884 ] James Taylor commented on PHOENIX-2535: --- Thanks for getting back to this, [~sergey

[jira] [Commented] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306888#comment-15306888 ] James Taylor commented on PHOENIX-2903: --- Found a few issues in that salted tables

[jira] [Created] (PHOENIX-2951) Ensure DatabaseMetaData.getSchema() methods work with namespace change

James Taylor created PHOENIX-2951: - Summary: Ensure DatabaseMetaData.getSchema() methods work with namespace change Key: PHOENIX-2951 URL: https://issues.apache.org/jira/browse/PHOENIX-2951 Project: P

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307920#comment-15307920 ] James Taylor commented on PHOENIX-2535: --- Your feedback on this would be much appre

[jira] [Commented] (PHOENIX-2267) Disambiguate server jar from phoenix-server module jar

[ https://issues.apache.org/jira/browse/PHOENIX-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308071#comment-15308071 ] James Taylor commented on PHOENIX-2267: --- Yes, correct. Would you have some spare c

[jira] [Commented] (PHOENIX-2267) Disambiguate server jar from phoenix-server module jar

[ https://issues.apache.org/jira/browse/PHOENIX-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308094#comment-15308094 ] James Taylor commented on PHOENIX-2267: --- Yes, PHOENIX-2535. Thanks - appreciate it

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308159#comment-15308159 ] James Taylor commented on PHOENIX-258: -- Thanks, [~lhofhansl]. Please file a separate

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308792#comment-15308792 ] James Taylor commented on PHOENIX-258: -- +1. Looks very good, [~lhofhansl]. Couple of

[jira] [Commented] (PHOENIX-2959) Ignore serial hint for queries doing an ORDER BY not along the PK axis

[ https://issues.apache.org/jira/browse/PHOENIX-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308821#comment-15308821 ] James Taylor commented on PHOENIX-2959: --- Patch looks good, but how about a test in

[jira] [Created] (PHOENIX-2960) Upgrade to Avatica 1.8.0

James Taylor created PHOENIX-2960: - Summary: Upgrade to Avatica 1.8.0 Key: PHOENIX-2960 URL: https://issues.apache.org/jira/browse/PHOENIX-2960 Project: Phoenix Issue Type: Improvement

[jira] [Commented] (PHOENIX-2960) Upgrade to Avatica 1.8.0

[ https://issues.apache.org/jira/browse/PHOENIX-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308837#comment-15308837 ] James Taylor commented on PHOENIX-2960: --- Any important items for Phoenix in Avatic

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308853#comment-15308853 ] James Taylor commented on PHOENIX-2921: --- Pinging [~poornachandra] - does the trans

[jira] [Commented] (PHOENIX-2921) Transaction manager won't start in local mode without replacing guava

[ https://issues.apache.org/jira/browse/PHOENIX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308911#comment-15308911 ] James Taylor commented on PHOENIX-2921: --- That's what I thought, [~poornachandra].

[jira] [Commented] (PHOENIX-2959) Ignore serial hint for queries doing an ORDER BY not along the PK axis

[ https://issues.apache.org/jira/browse/PHOENIX-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308903#comment-15308903 ] James Taylor commented on PHOENIX-2959: --- +1 > Ignore serial hint for queries doin

[jira] [Commented] (PHOENIX-2919) PreparedStatement Returns Incorrect Number of Deleted Records

[ https://issues.apache.org/jira/browse/PHOENIX-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308906#comment-15308906 ] James Taylor commented on PHOENIX-2919: --- +1 > PreparedStatement Returns Incorrect

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310636#comment-15310636 ] James Taylor commented on PHOENIX-258: -- Yes, good point, [~lhofhansl]. The reverse s

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310640#comment-15310640 ] James Taylor commented on PHOENIX-258: -- (and yes, you're correct - don't need to wor

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310668#comment-15310668 ] James Taylor commented on PHOENIX-258: -- What if you have these three rows (assume IN

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310723#comment-15310723 ] James Taylor commented on PHOENIX-258: -- I think what we need is an int[] indexed by

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Fix Version/s: 4.8.0 > select on a composite primary key fails when DESC is set in the table >

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Assignee: Samarth Jain > select on a composite primary key fails when DESC is set in the table

[jira] [Updated] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2961: -- Labels: SFDC (was: ) > select on a composite primary key fails when DESC is set in the table

[jira] [Commented] (PHOENIX-2961) select on a composite primary key fails when DESC is set in the table

[ https://issues.apache.org/jira/browse/PHOENIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310905#comment-15310905 ] James Taylor commented on PHOENIX-2961: --- My first guess is that the full row key(s

[jira] [Commented] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310981#comment-15310981 ] James Taylor commented on PHOENIX-2940: --- [~ndimiduk] - we don't use stats on the s

[jira] [Updated] (PHOENIX-2903) Handle split during scan for row key ordered aggregations

[ https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2903: -- Attachment: PHOENIX-2903_v4_wip.patch WIP patch > Handle split during scan for row key ordere

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311600#comment-15311600 ] James Taylor commented on PHOENIX-258: -- +1. Awesome job, [~lhofhansl]. I love the tr

[jira] [Updated] (PHOENIX-2930) Cannot resolve columns aliased to its own name

[ https://issues.apache.org/jira/browse/PHOENIX-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2930: -- Fix Version/s: 4.8.0 > Cannot resolve columns aliased to its own name > --

[jira] [Commented] (PHOENIX-2930) Cannot resolve columns aliased to its own name

[ https://issues.apache.org/jira/browse/PHOENIX-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312463#comment-15312463 ] James Taylor commented on PHOENIX-2930: --- [~maryannxue] - would it be possible for

[jira] [Commented] (PHOENIX-2596) Asynchronous Local Index is not available

[ https://issues.apache.org/jira/browse/PHOENIX-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312479#comment-15312479 ] James Taylor commented on PHOENIX-2596: --- +1 > Asynchronous Local Index is not ava

[jira] [Commented] (PHOENIX-2209) Building Local Index Asynchronously via IndexTool fails to populate index table

[ https://issues.apache.org/jira/browse/PHOENIX-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312481#comment-15312481 ] James Taylor commented on PHOENIX-2209: --- Ok, thanks - let me know when the patch i

[jira] [Commented] (PHOENIX-2926) Skip loading data for table having local indexes when there is split during bulkload job

[ https://issues.apache.org/jira/browse/PHOENIX-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312488#comment-15312488 ] James Taylor commented on PHOENIX-2926: --- +1 > Skip loading data for table having

[jira] [Updated] (PHOENIX-2949) Fix estimated region size when checking for serial query

[ https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2949: -- Fix Version/s: 4.8.0 > Fix estimated region size when checking for serial query >

[jira] [Commented] (PHOENIX-2949) Fix estimated region size when checking for serial query

[ https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312638#comment-15312638 ] James Taylor commented on PHOENIX-2949: --- Thanks for the fix, [~an...@apache.org].

<    1   2   3   4   5   6   7   8   9   10   >