[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653112#comment-15653112 ] chenglei edited comment on PHOENIX-3452 at 11/10/16 7:29 AM: -

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Attachment: PHOENIX-3469_v1.patch > Once a column in primary key or index is DESC, the corresponding

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Attachment: PHOENIX-3469_v1.patch > Once a column in primary key or index is DESC, the corresponding

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Attachment: (was: PHOENIX-3469_v1.patch) > Once a column in primary key or index is DESC, the

[jira] [Resolved] (PHOENIX-3410) Support ALTER VIEW in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved PHOENIX-3410. -- Resolution: Fixed Done as part of PHOENIX-3409. > Support ALTER VIEW

[jira] [Resolved] (PHOENIX-3409) Support ALTER TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved PHOENIX-3409. -- Resolution: Fixed Committed to calcite branch. [~maryannxue] Thanks

[jira] [Commented] (PHOENIX-3409) Support ALTER TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653199#comment-15653199 ] Maryann Xue commented on PHOENIX-3409: -- Thank you, [~rajeshbabu]! Please go ahead and commit it.

[jira] [Resolved] (PHOENIX-3470) Boolean values discrepancy with HBase byte format

[ https://issues.apache.org/jira/browse/PHOENIX-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-3470. --- Resolution: Invalid There's no correlation between how HBase serializes a boolean and how

[jira] [Created] (PHOENIX-3470) Boolean values discrepancy with HBase byte format

Maksim Zhuk created PHOENIX-3470: Summary: Boolean values discrepancy with HBase byte format Key: PHOENIX-3470 URL: https://issues.apache.org/jira/browse/PHOENIX-3470 Project: Phoenix Issue

[jira] [Updated] (PHOENIX-3409) Support ALTER TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3409: - Attachment: PHOENIX-3409_v2.patch [~maryannxue] Here is the patch

[jira] [Commented] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653112#comment-15653112 ] chenglei commented on PHOENIX-3452: --- [~jamestaylor], when I wrote my IT tests,I found another new

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Updated] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

[ https://issues.apache.org/jira/browse/PHOENIX-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenglei updated PHOENIX-3469: -- Description: This problem can be reproduced as following: {code:borderStyle=solid} CREATE

[jira] [Created] (PHOENIX-3469) Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly

chenglei created PHOENIX-3469: - Summary: Once a column in primary key or index is DESC, the corresponding order by NULLS LAST/NULLS FIRST may work incorrectly Key: PHOENIX-3469 URL:

[jira] [Commented] (PHOENIX-3468) Double quote SYSTEM, USER keywords in IT tests

[ https://issues.apache.org/jira/browse/PHOENIX-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15653082#comment-15653082 ] Rajeshbabu Chintaguntla commented on PHOENIX-3468: -- FYI [~maryannxue] [~jamestaylor]

[jira] [Created] (PHOENIX-3468) Double quote SYSTEM, USER keywords in IT tests

Rajeshbabu Chintaguntla created PHOENIX-3468: Summary: Double quote SYSTEM, USER keywords in IT tests Key: PHOENIX-3468 URL: https://issues.apache.org/jira/browse/PHOENIX-3468 Project:

[jira] [Commented] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652864#comment-15652864 ] James Taylor commented on PHOENIX-3461: --- +1. Thanks for the test fixes, [~samarthjain]. bq. I am

[jira] [Updated] (PHOENIX-3396) Valid Multi-byte strings whose total byte size is greater than the max char limit cannot be inserted into VARCHAR fields in the PK

[ https://issues.apache.org/jira/browse/PHOENIX-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3396: -- Fix Version/s: 4.9.0 > Valid Multi-byte strings whose total byte size is greater than the max

[jira] [Commented] (PHOENIX-3409) Support ALTER TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652644#comment-15652644 ] Maryann Xue commented on PHOENIX-3409: -- Thank you very much for the patch, [~rajeshbabu]! Three

[jira] [Commented] (PHOENIX-3427) rdd.saveToPhoenix gives table undefined error when attempting to write to a tenant-specific view (TenantId defined in configuration object and passed to saveToPhoenix

[ https://issues.apache.org/jira/browse/PHOENIX-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15652240#comment-15652240 ] ASF GitHub Bot commented on PHOENIX-3427: - Github user nico-pappagianis commented on a diff in

[GitHub] phoenix pull request #221: PHOENIX-3427 fix saveToRdd for tenant-specific co...

Github user nico-pappagianis commented on a diff in the pull request: https://github.com/apache/phoenix/pull/221#discussion_r87291460 --- Diff: phoenix-spark/src/main/scala/org/apache/phoenix/spark/ProductRDDFunctions.scala --- @@ -16,19 +16,20 @@ package org.apache.phoenix.spark

[jira] [Updated] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3461: -- Attachment: PHOENIX-3461_v5.patch Updated patch that introduces a new base test class called

[jira] [Commented] (PHOENIX-3391) Supporting Hive 2.1.0 in PhoenixStorageHandler

[ https://issues.apache.org/jira/browse/PHOENIX-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651905#comment-15651905 ] Sergey Soldatov commented on PHOENIX-3391: -- [~Jeongdae Kim] Excellent work! It looks good, once

[jira] [Comment Edited] (PHOENIX-3438) Phoenix should be able to optimize LIMIT query with IN clause

[ https://issues.apache.org/jira/browse/PHOENIX-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651887#comment-15651887 ] James Taylor edited comment on PHOENIX-3438 at 11/9/16 7:57 PM:

[jira] [Commented] (PHOENIX-3438) Phoenix should be able to optimize LIMIT query with IN clause

[ https://issues.apache.org/jira/browse/PHOENIX-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651887#comment-15651887 ] James Taylor commented on PHOENIX-3438: --- [~jpalmert] - our current optimization for distinct is

[jira] [Comment Edited] (PHOENIX-3438) Phoenix should be able to optimize LIMIT query with IN clause

[ https://issues.apache.org/jira/browse/PHOENIX-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15644889#comment-15644889 ] James Taylor edited comment on PHOENIX-3438 at 11/9/16 7:30 PM: Make

[jira] [Updated] (PHOENIX-3467) Update Phoenix/Hive storage handler documentation

[ https://issues.apache.org/jira/browse/PHOENIX-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-3467: Assignee: Frank Welsch > Update Phoenix/Hive storage handler documentation >

[jira] [Updated] (PHOENIX-3241) Convert_tz doesn't allow timestamp data type

[ https://issues.apache.org/jira/browse/PHOENIX-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-3241: Attachment: PHOENIX-3241.002.patch Slight modification on Ankit's original patch. Allows DATE or

[jira] [Commented] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651640#comment-15651640 ] James Taylor commented on PHOENIX-3461: --- Yes, a new test category would still spin up a mini

[jira] [Updated] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3461: -- Attachment: PHOENIX-3461_v4.patch For namespaces to be used, we need to set the config on

Re: [VOTE] Release of Apache Phoenix 4.8.2 RC1

-1. PHOENIX-3452 is causing incorrect query results. I patch is in progress, so a fix should come soon. On Mon, Nov 7, 2016 at 1:31 PM, wrote: > Hello Fellow Phoenix'ers, > > The second RC for Apache Phoenix 4.8.2 is available. This is a patch > release for the Phoenix 4.8

[jira] [Reopened] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reopened PHOENIX-3452: --- > Secondary index and query using distinct: ORDER BY doesn't work correctly >

[jira] [Commented] (PHOENIX-3467) Update Phoenix/Hive storage handler documentation

[ https://issues.apache.org/jira/browse/PHOENIX-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651589#comment-15651589 ] Josh Elser commented on PHOENIX-3467: - I started skimming this last night. It looks really good,

[jira] [Commented] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651588#comment-15651588 ] James Taylor commented on PHOENIX-3461: --- Every test that runs as NeedsOwnCluster increases the

[jira] [Commented] (PHOENIX-3241) Convert_tz doesn't allow timestamp data type

[ https://issues.apache.org/jira/browse/PHOENIX-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651509#comment-15651509 ] Josh Elser commented on PHOENIX-3241: - Hey [~an...@apache.org], why the removal of the PDate type as

[jira] [Updated] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3461: -- Attachment: PHOENIX-3461-v3.patch [~jamestaylor], please review. > Statistics collection

[jira] [Reopened] (PHOENIX-3461) Statistics collection broken if name space mapping enabled for SYSTEM tables

[ https://issues.apache.org/jira/browse/PHOENIX-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain reopened PHOENIX-3461: --- > Statistics collection broken if name space mapping enabled for SYSTEM tables >

[jira] [Updated] (PHOENIX-3410) Support ALTER VIEW in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3410: - Labels: calcite (was: ) > Support ALTER VIEW in Phoenix-Calcite

[jira] [Updated] (PHOENIX-3409) Support ALTER TABLE in Phoenix-Calcite Integration

[ https://issues.apache.org/jira/browse/PHOENIX-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-3409: - Attachment: PHOENIX-3409.patch [~maryannxue] Here is the patch supports

Dynamic columns and indexing

Hi there, I tried mailing to the users mailing list, but the email address seems to be invalid. The following issue seems to be a bug in Phoenix. I create an index: create local index "myIndex" on "myTable"("myStaticColumn"); I do a select on a static column, and Phoenix correctly utilizes the

[jira] [Commented] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15651169#comment-15651169 ] James Taylor commented on PHOENIX-3452: --- Yes, that's correct. > Secondary index and query using

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:55 PM:

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:45 PM:

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:52 PM:

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:46 PM:

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:47 PM:

[jira] [Comment Edited] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei edited comment on PHOENIX-3452 at 11/9/16 2:32 PM: Ok,I will try

[jira] [Commented] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650438#comment-15650438 ] chenglei commented on PHOENIX-3452: --- Ok,I will try some IT tests > Secondary index and query using

[jira] [Commented] (PHOENIX-1515) explain time is too long

[ https://issues.apache.org/jira/browse/PHOENIX-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650374#comment-15650374 ] Mac commented on PHOENIX-1515: -- James, is this an issue of explain or the slow return of some RPC call in

[jira] [Commented] (PHOENIX-3452) Secondary index and query using distinct: ORDER BY doesn't work correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650176#comment-15650176 ] James Taylor commented on PHOENIX-3452: --- Thanks, [~comnetwork]. Try these tests as end-to-end