[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=15309327#comment-15309327 ] Lars Hofhansl commented on PHOENIX-258: --- Nope. The next part will start with something >= 0x00. So

[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=15309316#comment-15309316 ] Lars Hofhansl commented on PHOENIX-258: --- Turns out there's a problem for fixed length fields when

[jira] [Commented] (PHOENIX-2952) array_length return negative value

[ https://issues.apache.org/jira/browse/PHOENIX-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309308#comment-15309308 ] Joseph Sun commented on PHOENIX-2952: - org.apache.phoenix.schema.types.PArrayDataType {code}

[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=15309272#comment-15309272 ] Lars Hofhansl commented on PHOENIX-258: --- Hmm... isOrderPreserving is calculated like this:

[jira] [Updated] (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:all-tabpanel ] Junegunn Choi updated PHOENIX-930: -- Attachment: PHOENIX-930-v3.patch New patch without irrelevant EOL change. > duplicated

[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=15309256#comment-15309256 ] Lars Hofhansl commented on PHOENIX-258: --- Lemme do those two. Was thinking on the

[jira] [Updated] (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:all-tabpanel ] Junegunn Choi updated PHOENIX-930: -- Attachment: PHOENIX-930-v2.patch New patch to address [~yhxx511]'s comment. > duplicated

[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=15309154#comment-15309154 ] Junegunn Choi commented on PHOENIX-930: --- [~william yang] Good point. I'll update the patch shortly.

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309130#comment-15309130 ] Maryann Xue commented on PHOENIX-2405: -- Hi [~RCheungIT], thank you very much for the pull request!

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65294499 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/execute/SortMergeJoinPlan.java --- @@ -572,11 +569,11 @@ public MappedByteBufferTupleQueue(int

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

[ https://issues.apache.org/jira/browse/PHOENIX-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser reassigned PHOENIX-2960: --- Assignee: Josh Elser > Upgrade to Avatica 1.8.0 > > >

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65294376 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/DeferredByteBufferSegmentQueue.java --- @@ -0,0 +1,123 @@ +package

[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=15309109#comment-15309109 ] Josh Elser commented on PHOENIX-2960: - Just launched an rc1 VOTE. I can easily bump this when it

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65294053 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/BufferSegmentQueue.java --- @@ -0,0 +1,251 @@ +package org.apache.phoenix.iterate;

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65293621 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/DeferredByteBufferSegmentQueue.java --- @@ -0,0 +1,123 @@ +package

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65293343 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/DeferredByteBufferSegmentQueue.java --- @@ -0,0 +1,123 @@ +package

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65293136 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/iterate/DeferredByteBufferSegmentQueue.java --- @@ -0,0 +1,123 @@ +package

[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=15309066#comment-15309066 ] William Yang commented on PHOENIX-930: -- [~junegunn], Why not move hasColumnWithSameNameAndFamily to

[GitHub] phoenix pull request: Phoenix-2405

Github user maryannxue commented on a diff in the pull request: https://github.com/apache/phoenix/pull/171#discussion_r65291859 --- Diff: phoenix-core/src/main/java/org/apache/phoenix/coprocessor/ScanRegionObserver.java --- @@ -234,6 +234,12 @@ protected RegionScanner

[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=15309004#comment-15309004 ] Enis Soztutar commented on PHOENIX-2931: Thinking about this, there is no surefire way to check

[jira] [Commented] (PHOENIX-2536) Return of aggregation functions do not have the correct data type and precision

[ https://issues.apache.org/jira/browse/PHOENIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308951#comment-15308951 ] Kevin Liew commented on PHOENIX-2536: - I think that is reasonable, to always return a value with the

[jira] [Updated] (PHOENIX-2380) Use smallest sized type preserving precision for float/double/Decimal

[ https://issues.apache.org/jira/browse/PHOENIX-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Liew updated PHOENIX-2380: Description: {noformat} CREATE TABLE test.DECIMAL_TABLE( KeyColumn VARCHAR(255) PRIMARY

[jira] [Updated] (PHOENIX-2380) Use smallest sized type preserving precision for float/double/Decimal

[ https://issues.apache.org/jira/browse/PHOENIX-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Liew updated PHOENIX-2380: Affects Version/s: 4.8.0 > Use smallest sized type preserving precision for float/double/Decimal

[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=15308906#comment-15308906 ] James Taylor commented on PHOENIX-2919: --- +1 > PreparedStatement Returns Incorrect Number 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=15308903#comment-15308903 ] James Taylor commented on PHOENIX-2959: --- +1 > Ignore serial hint for queries doing an ORDER BY

[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=15308911#comment-15308911 ] James Taylor commented on PHOENIX-2921: --- That's what I thought, [~poornachandra]. Any explanation,

[jira] [Commented] (PHOENIX-2536) Return of aggregation functions do not have the correct data type and precision

[ https://issues.apache.org/jira/browse/PHOENIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308904#comment-15308904 ] Sergey Soldatov commented on PHOENIX-2536: -- It's not clear what to do if one operand is exact

[jira] [Updated] (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:all-tabpanel ] Samarth Jain updated PHOENIX-2959: -- Attachment: PHOENIX-2959_v2.patch Updated patch with test. > Ignore serial hint for queries

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

[ https://issues.apache.org/jira/browse/PHOENIX-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2919: -- Attachment: PHOENIX-2919.patch Attached is the patch that fixes the issue. Also added tests

Re: Are we ready for 4.8.0 RC?

There are a few issues that I am working on currently that I hope to have fixes for by early next week: https://issues.apache.org/jira/browse/PHOENIX-2919 https://issues.apache.org/jira/browse/PHOENIX-2814 https://issues.apache.org/jira/browse/PHOENIX-2920

[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=15308871#comment-15308871 ] Poorna Chandra commented on PHOENIX-2921: - Sorry - missed the earlier comment. 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=15308866#comment-15308866 ] Mujtaba Chohan commented on PHOENIX-2535: - Few minor issues at quick glance in

Re: Are we ready for 4.8.0 RC?

Would be good to upgrade to Avatica 1.8 (PHOENIX-2960) - a vote should start on that today or tomorrow. James On Tue, May 31, 2016 at 1:48 PM, Nick Dimiduk wrote: > We're hoping to get the shaded client jars [0] and rename of queryserver > jar [1] changes in for 4.8.

[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=15308864#comment-15308864 ] Josh Elser commented on PHOENIX-2960: - bq. Any important items for Phoenix in Avatica 1.8.0 Yeah,

[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=15308853#comment-15308853 ] James Taylor commented on PHOENIX-2921: --- Pinging [~poornachandra] - does the transaction manager

[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=15308837#comment-15308837 ] James Taylor commented on PHOENIX-2960: --- Any important items for Phoenix in Avatica 1.8.0,

[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-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=15308821#comment-15308821 ] James Taylor commented on PHOENIX-2959: --- Patch looks good, but how about a test 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=15308792#comment-15308792 ] James Taylor commented on PHOENIX-258: -- +1. Looks very good, [~lhofhansl]. Couple of optional items,

[jira] [Commented] (PHOENIX-2536) Return of aggregation functions do not have the correct data type and precision

[ https://issues.apache.org/jira/browse/PHOENIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308735#comment-15308735 ] Sergey Soldatov commented on PHOENIX-2536: -- [~kliew] Thanks for the clarification. I'm aware

[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-v12.txt -v12 Does correct column count accounting. This should be close to

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

[ https://issues.apache.org/jira/browse/PHOENIX-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reassigned PHOENIX-2919: - Assignee: Samarth Jain > PreparedStatement Returns Incorrect Number of Deleted Records

Re: Are we ready for 4.8.0 RC?

We're hoping to get the shaded client jars [0] and rename of queryserver jar [1] changes in for 4.8. There's also an optimization improvement for using skip scan that's close [2]. [0]: https://issues.apache.org/jira/browse/PHOENIX-2535 [1]: https://issues.apache.org/jira/browse/PHOENIX-2267 [2]:

[jira] [Commented] (PHOENIX-2536) Return of aggregation functions do not have the correct data type and precision

[ https://issues.apache.org/jira/browse/PHOENIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308551#comment-15308551 ] Kevin Liew commented on PHOENIX-2536: - This bug applies to both aggregation SUM(column) and `column1

[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-v11.txt -v11 fixes the previous key issue. Did it slightly differently. I

[jira] [Commented] (PHOENIX-2947) NPE in ExpresssionCompiler.visitLeave

[ https://issues.apache.org/jira/browse/PHOENIX-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308407#comment-15308407 ] Alicia Ying Shu commented on PHOENIX-2947: -- The NPE can be easily reproduced. Added a test case

[jira] [Updated] (PHOENIX-2947) NPE in ExpresssionCompiler.visitLeave

[ https://issues.apache.org/jira/browse/PHOENIX-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu updated PHOENIX-2947: - Attachment: PHOENIX-2947-v1.patch > NPE in ExpresssionCompiler.visitLeave >

[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=15308359#comment-15308359 ] Mujtaba Chohan commented on PHOENIX-2943: - [~jamestaylor] Not a regression as query results are

[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=15308344#comment-15308344 ] Josh Elser commented on PHOENIX-2931: - You're completely right. SGTM! > Phoenix client asks users

[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=15308328#comment-15308328 ] Lars Hofhansl commented on PHOENIX-2919: [~giacomotaylor], FYI. Some work we'll need for

[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=15308320#comment-15308320 ] Samarth Jain commented on PHOENIX-2943: --- Thanks for pointing that out, [~an...@apache.org]. It

[jira] [Updated] (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:all-tabpanel ] Samarth Jain updated PHOENIX-2959: -- Assignee: Samarth Jain Fix Version/s: 4.8.0 > Ignore serial hint for queries doing

[jira] [Updated] (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:all-tabpanel ] Samarth Jain updated PHOENIX-2959: -- Attachment: PHOENIX-2959.patch [~jamestaylor], please review. > Ignore serial hint for

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

Samarth Jain created PHOENIX-2959: - Summary: Ignore serial hint for queries doing an ORDER BY not along the PK axis Key: PHOENIX-2959 URL: https://issues.apache.org/jira/browse/PHOENIX-2959 Project:

[jira] [Resolved] (PHOENIX-2958) Join works incorrectly with DESC columns in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2958. -- Resolution: Fixed > Join works incorrectly with DESC columns in Calcite-Phoenix >

[jira] [Created] (PHOENIX-2958) Join works incorrectly with DESC columns in Calcite-Phoenix

Maryann Xue created PHOENIX-2958: Summary: Join works incorrectly with DESC columns in Calcite-Phoenix Key: PHOENIX-2958 URL: https://issues.apache.org/jira/browse/PHOENIX-2958 Project: Phoenix

Are we ready for 4.8.0 RC?

Hello Everyone, I'd like to propose a roll out of 4.8.0 RC early next week(*7th June*) Here is the list of some good work already been done for this release. - Local Index improvements[1] - Phoenix hive integration[2] - Namespace mapping support[3] - Many VIEW enhancements[4] -

[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=15308243#comment-15308243 ] Samarth Jain commented on PHOENIX-2901: --- Thanks for the patch, [~an...@apache.org]. Looking at

[jira] [Created] (PHOENIX-2957) WhereOptimizer to provide an estimate of key selectivity for key filters containing bind variables

Maryann Xue created PHOENIX-2957: Summary: WhereOptimizer to provide an estimate of key selectivity for key filters containing bind variables Key: PHOENIX-2957 URL:

[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=15308217#comment-15308217 ] Hadoop QA commented on PHOENIX-930: --- {color:red}-1 overall{color}. Here are the results of testing the

[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=15308212#comment-15308212 ] Lars Hofhansl commented on PHOENIX-258: --- Makes sense. Thanks for the case where it would not work.

[jira] [Resolved] (PHOENIX-2881) Support bind parameters in Calcite-Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue resolved PHOENIX-2881. -- Resolution: Fixed > Support bind parameters in Calcite-Phoenix >

[jira] [Assigned] (PHOENIX-2536) Return of aggregation functions do not have the correct data type and precision

[ https://issues.apache.org/jira/browse/PHOENIX-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Soldatov reassigned PHOENIX-2536: Assignee: Sergey Soldatov > Return of aggregation functions do not have the

[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=15308159#comment-15308159 ] James Taylor commented on PHOENIX-258: -- Thanks, [~lhofhansl]. Please file a separate bug for the RVC

[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=15308094#comment-15308094 ] James Taylor commented on PHOENIX-2267: --- Yes, PHOENIX-2535. Thanks - appreciate it! Let's get it

[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=15308084#comment-15308084 ] Nick Dimiduk commented on PHOENIX-2267: --- I assume you meant PHOENIX-2535. Yes hoping so; I want

[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=15308071#comment-15308071 ] James Taylor commented on PHOENIX-2267: --- Yes, correct. Would you have some spare cycles to

[jira] [Updated] (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:all-tabpanel ] Junegunn Choi updated PHOENIX-930: -- Attachment: PHOENIX-930.patch > duplicated columns cause query exception and drop table

[jira] [Reopened] (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:all-tabpanel ] Junegunn Choi reopened PHOENIX-930: --- Assignee: Junegunn Choi Reopening as it's reproducible with the current master.

[jira] [Commented] (PHOENIX-2956) apache-rat plugin error: Too many unapproved licenses

[ https://issues.apache.org/jira/browse/PHOENIX-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307976#comment-15307976 ] ASF GitHub Bot commented on PHOENIX-2956: - GitHub user shijinkui opened a pull request:

[GitHub] phoenix pull request: [PHOENIX-2956] apache-rat plugin error: Too many unapp...

GitHub user shijinkui opened a pull request: https://github.com/apache/phoenix/pull/172 [PHOENIX-2956] apache-rat plugin error: Too many unapproved licenses [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.8:check (default-cli) on project phoenix-core: Too many

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307974#comment-15307974 ] Haoran Zhang commented on PHOENIX-2405: --- Hi [~maryannxue], About this JIRA I just finished an

[jira] [Updated] (PHOENIX-2956) apache-rat plugin error: Too many unapproved licenses

[ https://issues.apache.org/jira/browse/PHOENIX-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shijinkui updated PHOENIX-2956: --- Summary: apache-rat plugin error: Too many unapproved licenses (was: apache-rat plugin ) >

[jira] [Updated] (PHOENIX-2956) apache-rat plugin

[ https://issues.apache.org/jira/browse/PHOENIX-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shijinkui updated PHOENIX-2956: --- Summary: apache-rat plugin (was: apache-rat skip check ignore error) > apache-rat plugin >

[jira] [Updated] (PHOENIX-2956) apache-rat skip check ignore error

[ https://issues.apache.org/jira/browse/PHOENIX-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shijinkui updated PHOENIX-2956: --- Description: [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.8:check

[jira] [Commented] (PHOENIX-2405) Improve performance and stability of server side sort for ORDER BY

[ https://issues.apache.org/jira/browse/PHOENIX-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307954#comment-15307954 ] ASF GitHub Bot commented on PHOENIX-2405: - GitHub user RCheungIT opened a pull request:

[GitHub] phoenix pull request: Phoenix-2405

GitHub user RCheungIT opened a pull request: https://github.com/apache/phoenix/pull/171 Phoenix-2405 https://issues.apache.org/jira/browse/PHOENIX-2405 You can merge this pull request into a Git repository by running: $ git pull https://github.com/RCheungIT/phoenix

[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=15307938#comment-15307938 ] Nick Dimiduk commented on PHOENIX-2267: --- I see. Patch v6 on 2535 does the work of this one as

[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=15307935#comment-15307935 ] Nick Dimiduk commented on PHOENIX-2267: --- bq. Thanks for PHOENIX-2535. Can we close this as a dup

[jira] [Commented] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

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

[GitHub] phoenix pull request: [PHOENIX-2955] use xmllint for parsing phoenix name in...

Github user JamesRTaylor commented on the pull request: https://github.com/apache/phoenix/pull/170 @joshelser - WDYT? If it's fine, would you mind committing? --- 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

[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=15307920#comment-15307920 ] James Taylor commented on PHOENIX-2535: --- Your feedback on this would be much appreciated too,

[jira] [Created] (PHOENIX-2956) apache-rat skip check ignore error

shijinkui created PHOENIX-2956: -- Summary: apache-rat skip check ignore error Key: PHOENIX-2956 URL: https://issues.apache.org/jira/browse/PHOENIX-2956 Project: Phoenix Issue Type: Bug

[GitHub] phoenix pull request: [PHOENIX-2955] use xmllint for parsing phoenix name in...

GitHub user shijinkui opened a pull request: https://github.com/apache/phoenix/pull/170 [PHOENIX-2955] use xmllint for parsing phoenix name in pom.xml at make_rc.sh fix problem: "Cannot open file -q at /System/Library/Perl/Extras/5.18/XML/XPath.pm line 53." use `xmllint`

[jira] [Created] (PHOENIX-2955) replace xpath to xmllint at make_rc.sh

shijinkui created PHOENIX-2955: -- Summary: replace xpath to xmllint at make_rc.sh Key: PHOENIX-2955 URL: https://issues.apache.org/jira/browse/PHOENIX-2955 Project: Phoenix Issue Type: Bug

[jira] [Created] (PHOENIX-2954) Avoid doing a full sort if the input is ordered on the leading edge of the sort key

Maryann Xue created PHOENIX-2954: Summary: Avoid doing a full sort if the input is ordered on the leading edge of the sort key Key: PHOENIX-2954 URL: https://issues.apache.org/jira/browse/PHOENIX-2954

[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=15307723#comment-15307723 ] Ian Hellstrom commented on PHOENIX-2930: I can confirm this bug on Hortonworks HDP 2.3.2.0 with

[jira] [Created] (PHOENIX-2953) some value is returned null when selecting query if phoenix table has a big length column

JaeMyung Kim created PHOENIX-2953: - Summary: some value is returned null when selecting query if phoenix table has a big length column Key: PHOENIX-2953 URL: https://issues.apache.org/jira/browse/PHOENIX-2953

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

[ https://issues.apache.org/jira/browse/PHOENIX-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307308#comment-15307308 ] Ankit Singhal commented on PHOENIX-2951: [~giacomotaylor], it is a duplicate of PHOENIX-2902.

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

[ https://issues.apache.org/jira/browse/PHOENIX-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved PHOENIX-2951. Resolution: Duplicate > Ensure DatabaseMetaData.getSchema() methods work with namespace

[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=15307296#comment-15307296 ] Ravi Kishore Valeti commented on PHOENIX-1833: -- [~jamestaylor] - Moved the patch to

[jira] [Updated] (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:all-tabpanel ] Ravi Kishore Valeti updated PHOENIX-1833: - Attachment: (was: PHOENIX-1833-0.98.patch) > Optionally trigger MR job to

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

[ https://issues.apache.org/jira/browse/PHOENIX-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307293#comment-15307293 ] Ravi Kishore Valeti commented on PHOENIX-2950: -- [~jamestaylor] Moved the patch from

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

[ https://issues.apache.org/jira/browse/PHOENIX-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Kishore Valeti updated PHOENIX-2950: - Attachment: PHOENIX-2950-0.98.patch Attached the patch > Implement CRON job to

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

[ https://issues.apache.org/jira/browse/PHOENIX-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Kishore Valeti reassigned PHOENIX-2950: Assignee: Ravi Kishore Valeti > Implement CRON job to start async index