[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v4.txt The actual patch with the test. > Use skip scan when SELECT DISTINCT on

[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: (was: 258-v4.txt) > Use skip scan when SELECT DISTINCT on leading row key colum

[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v4.txt * -v4 has some basic tests. * It also deals with the scenario of a fixed

[jira] [Commented] (PHOENIX-2945) Fix SortOrderExpressionTest.toChar on non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303525#comment-15303525 ] Hadoop QA commented on PHOENIX-2945: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (PHOENIX-2945) Fix SortOrderExpressionTest.toChar on non-English locales

[ https://issues.apache.org/jira/browse/PHOENIX-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junegunn Choi updated PHOENIX-2945: --- Attachment: PHOENIX-2945.patch > Fix SortOrderExpressionTest.toChar on non-English locales >

[jira] [Created] (PHOENIX-2945) Fix SortOrderExpressionTest.toChar on non-English locales

Junegunn Choi created PHOENIX-2945: -- Summary: Fix SortOrderExpressionTest.toChar on non-English locales Key: PHOENIX-2945 URL: https://issues.apache.org/jira/browse/PHOENIX-2945 Project: Phoenix

[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=15303122#comment-15303122 ] Lars Hofhansl commented on PHOENIX-258: --- * g1, g2, g3 do not even have to be ordere

[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v3.txt -v3 observes that the same optimization is possible for queries like SEL

[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v2.txt -v2 adds EXPLAIN > Use skip scan when SELECT DISTINCT on leading row ke

[jira] [Created] (PHOENIX-2944) DATE Comparison Broken

Aaron Stephens created PHOENIX-2944: --- Summary: DATE Comparison Broken Key: PHOENIX-2944 URL: https://issues.apache.org/jira/browse/PHOENIX-2944 Project: Phoenix Issue Type: Bug Affects

[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=15303060#comment-15303060 ] Sergey Soldatov commented on PHOENIX-2535: -- [~jamestaylor] My bad, overestimate

[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=15303039#comment-15303039 ] Alicia Ying Shu commented on PHOENIX-2886: -- Uploaded a revised patch with more

[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=15303028#comment-15303028 ] Mujtaba Chohan commented on PHOENIX-2942: - [~jamestaylor] No. Same behavior with

[jira] [Updated] (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:all-tabpanel ] Alicia Ying Shu updated PHOENIX-2886: - Attachment: PHOENIX-2886-v4.patch > Union ALL with Char column not present in the table

[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-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:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v1.txt Here's a patch that works. Tests with * fixed length single field prefix

[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=15302951#comment-15302951 ] Josh Elser commented on PHOENIX-2940: - {quote} bq.do not cache stats on the serv

[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-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-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-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-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] [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-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] [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] [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] [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] [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=15302923#comment-15302923 ] Nick Dimiduk commented on PHOENIX-2940: --- Thanks for picking this one up [~elserj].

[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-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] [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-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] [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] [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: -- 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: -- 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-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] [Issue Comment Deleted] (PHOENIX-1734) Local index improvements

[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov updated PHOENIX-1734: - Comment: was deleted (was: [~rajeshbabu] Thank you for the patch, I will check how it wo

[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=15302847#comment-15302847 ] Sergey Soldatov commented on PHOENIX-1734: -- [~rajeshbabu] Thank you for the pat

[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-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:all-tabpanel ] Sergey Soldatov updated PHOENIX-2936: - Attachment: PHOENIX-2936-2.patch Revised the patch. Added missing antlr-runtime jar to t

[jira] [Assigned] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu reassigned PHOENIX-2934: Assignee: Alicia Ying Shu > Checking a coerce expression at top level should not

[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=15302804#comment-15302804 ] Alicia Ying Shu commented on PHOENIX-2931: -- [~jamestaylor] [~elserj] [~sergey.s

[jira] [Updated] (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:all-tabpanel ] Mujtaba Chohan updated PHOENIX-2943: Summary: Performance of parallel order by query is > 30X slower than serial execution (wa

[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=15302729#comment-15302729 ] Alicia Ying Shu commented on PHOENIX-2886: -- My tests reveals that checking sort

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

Mujtaba Chohan created PHOENIX-2943: --- Summary: Performance of parallel group by query is > 30X slower than serial execution Key: PHOENIX-2943 URL: https://issues.apache.org/jira/browse/PHOENIX-2943

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

Mujtaba Chohan created PHOENIX-2942: --- Summary: Incorrect results for order by queries Key: PHOENIX-2942 URL: https://issues.apache.org/jira/browse/PHOENIX-2942 Project: Phoenix Issue Type:

[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=15302556#comment-15302556 ] Alicia Ying Shu commented on PHOENIX-2886: -- Agree that we need to check MaxLeng

[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-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=15302272#comment-15302272 ] Sergey Soldatov commented on PHOENIX-2886: -- All we need is to check if 2 data t

[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] [Updated] (PHOENIX-1734) Local index improvements

[ https://issues.apache.org/jira/browse/PHOENIX-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-1734: - Attachment: PHOENIX-1734_addendum2.patch The reason for the NPE during c

MapReduce code runs only in local. How to execute my code in distributed mode?

Hello everybody, For a few days I developed a MapReduce code to insert values in HBase with Phoenix. But the code runs only in local and overcharge the machine. Whatever changes I make I observe that the mapred.LocalJobRunner class is systematically used. Do you have an idea of the problem? I

[jira] [Commented] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301952#comment-15301952 ] Hadoop QA commented on PHOENIX-2915: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301944#comment-15301944 ] Rajeshbabu Chintaguntla commented on PHOENIX-2915: -- [~ankit.singhal] Yo

[jira] [Updated] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

[ https://issues.apache.org/jira/browse/PHOENIX-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-2915: --- Attachment: PHOENIX-2915.patch Thanks [~rajeshbabu], it will be good solution.. As you said

[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=15301875#comment-15301875 ] Rajeshbabu Chintaguntla commented on PHOENIX-1734: -- [~sergey.soldatov]