[jira] [Commented] (PHOENIX-2042) Windows need hadoop native libraries to run tests

[ https://issues.apache.org/jira/browse/PHOENIX-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606892#comment-14606892 ] Hudson commented on PHOENIX-2042: - FAILURE: Integrated in Phoenix-master #805 (See [htt

[jira] [Updated] (PHOENIX-2087) Ensure predictable column position during alter table

[ https://issues.apache.org/jira/browse/PHOENIX-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2087: -- Attachment: PHOENIX-2087.patch > Ensure predictable column position during alter table > -

[jira] [Created] (PHOENIX-2087) Ensure predictable column position during alter table

James Taylor created PHOENIX-2087: - Summary: Ensure predictable column position during alter table Key: PHOENIX-2087 URL: https://issues.apache.org/jira/browse/PHOENIX-2087 Project: Phoenix I

Re: [DISCUSS] drop 4.x-HBase-1.1 branch

Should we also drop 1.0 branch and support only HBase-1.1+ in Phoenix 4.5+ ? HBase-1.0 users have 4.4.x releases to use. It should be fair to require a minor HBase upgrade for a minor Phoenix version upgrade. Enis On Mon, Jun 22, 2015 at 9:18 AM, James Taylor wrote: > Ok, I'll drop the branch

[jira] [Updated] (PHOENIX-2050) Avoid checking for child views unless operating on table

[ https://issues.apache.org/jira/browse/PHOENIX-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2050: -- Attachment: 0001-PHOENIX-2050-Avoid-checking-for-child-views-unless-o.patch Patch for master b

[jira] [Updated] (PHOENIX-2050) Avoid checking for child views unless operating on table

[ https://issues.apache.org/jira/browse/PHOENIX-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2050: -- Summary: Avoid checking for child views unless operating on table (was: Dropping a view check

[jira] [Assigned] (PHOENIX-2050) Dropping a view checks whether it has child views which has to be done only when a table is dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-2050: - Assignee: James Taylor > Dropping a view checks whether it has child views which has to

[jira] [Commented] (PHOENIX-2059) MR index build does not handle table with a schema name correctly

[ https://issues.apache.org/jira/browse/PHOENIX-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606747#comment-14606747 ] James Taylor commented on PHOENIX-2059: --- +1 from me too. > MR index build does no

[jira] [Updated] (PHOENIX-2058) Check for existence and compatibility of columns being added in view

[ https://issues.apache.org/jira/browse/PHOENIX-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2058: -- Assignee: Thomas D'Silva (was: Samarth Jain) > Check for existence and compatibility of colum

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606633#comment-14606633 ] Hudson commented on PHOENIX-1659: - FAILURE: Integrated in Phoenix-master #804 (See [htt

[jira] [Commented] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606568#comment-14606568 ] James Taylor commented on PHOENIX-2075: --- +1 > MR integration uses single mapper u

[jira] [Updated] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2075: Attachment: PHOENIX-2075-4.4-HBase-0.98-v3.patch Thanks [~jamestaylor] , I have made the c

Re: [jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

Hi Nishani, Any progress on your module for including the SQL query in the UI? Thanks, Nick On Wed, Jun 24, 2015 at 11:46 AM, Ayola Jayamaha wrote: > Hi All, > I'll create a javascript module in angular to solve this issue and share. > > Thanks, > Nishani. > > On Thu, Jun 25, 2015 at 12:09 AM,

[jira] [Commented] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606464#comment-14606464 ] James Taylor commented on PHOENIX-2075: --- Thanks, [~tdsilva]. Here's some feedback:

[jira] [Updated] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2075: Attachment: PHOENIX-2075-4.4-HBase-0.98-v2.patch > MR integration uses single mapper unles

[jira] [Updated] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2075: Attachment: (was: PHOENIX-2075-4.4-HBase-0.98-v2.patch) > MR integration uses single m

[jira] [Updated] (PHOENIX-2075) MR integration uses single mapper unless table is salted

[ https://issues.apache.org/jira/browse/PHOENIX-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2075: Attachment: PHOENIX-2075-4.4-HBase-0.98-v2.patch I removed the pom changes and will fix th

[jira] [Commented] (PHOENIX-2036) PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime

[ https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606410#comment-14606410 ] James Taylor commented on PHOENIX-2036: --- Any ETA on this, [~maghamravikiran]? > P

Re: Writing to Underlying HBase Tables

+user Hi Jeff, Phoenix and non-Phoenix tables can co-exist in the same cluster, no problem. Sharing the same table with both Phoenix and non-Phoenix clients can be a bit tricky. Likely you'll become intimately familiar Phoenix's encoding formats and compound-types. This interoperability is a roa

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606377#comment-14606377 ] Hudson commented on PHOENIX-978: FAILURE: Integrated in Phoenix-master #803 (See [https:

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606370#comment-14606370 ] James Taylor commented on PHOENIX-1659: --- +1. Thanks for the quick follow up, [~jma

[jira] [Commented] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606364#comment-14606364 ] James Taylor commented on PHOENIX-2085: --- +1. Thanks, [~tdsilva]. > Include joda-t

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2085: -- Description: To enable MR jobs to be runnable through the HBase shell, we need to include the

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2085: Attachment: PHOENIX-2085.patch > Include joda-time in phoenix server jar > ---

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2085: Attachment: (was: PHOENIX-2075.patch) > Include joda-time in phoenix server jar >

[jira] [Created] (PHOENIX-2086) CONSTRAINT_VIOLATION error code should use sqlstate 23, not 22.

Lukas Lalinsky created PHOENIX-2086: --- Summary: CONSTRAINT_VIOLATION error code should use sqlstate 23, not 22. Key: PHOENIX-2086 URL: https://issues.apache.org/jira/browse/PHOENIX-2086 Project: Phoe

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2085: Fix Version/s: 4.4.1 4.5.0 5.0.0 > Include joda-time

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2085: Attachment: PHOENIX-2075.patch > Include joda-time in phoenix server jar > ---

[jira] [Updated] (PHOENIX-2085) Include joda-time in phoenix server jar

[ https://issues.apache.org/jira/browse/PHOENIX-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-2085: Summary: Include joda-time in phoenix server jar (was: Inlcude joda-time in phoenix serve

[jira] [Updated] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-1659: -- Attachment: PHOENIX-1659-followup.patch Adjust COLUMN_FAMILY_POSITION in QueryUtil to account

[jira] [Created] (PHOENIX-2085) Inlcude joda-time in phoenix server jar

Thomas D'Silva created PHOENIX-2085: --- Summary: Inlcude joda-time in phoenix server jar Key: PHOENIX-2085 URL: https://issues.apache.org/jira/browse/PHOENIX-2085 Project: Phoenix Issue Type:

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606171#comment-14606171 ] Josh Mahonin commented on PHOENIX-1659: --- It looks like there's an issue with the f

Re: Numeric types with flipped back sign bit

Are you wanting to interface with HBase-client data from Phoenix, or is it vice-versa? Phoenix's UNSIGNED_TINYINT type is the equivalent of using HBase's Bytes.putByte(byte[], int, byte). HBase's Bytes encodings do not preserve the sort order of negative values in encoded form, hence the OrderedByt

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606103#comment-14606103 ] Hudson commented on PHOENIX-1659: - FAILURE: Integrated in Phoenix-master #802 (See [htt

Writing to Underlying HBase Tables

Hey all, We previously had a setup with Phoenix views over an HBase table. However, now we want to take advantage of Multi-tenancy so we are planning to map a multi-tenant Phoenix table to the HBase table, and then put the views on top of the Phoenix table. The question that has been raised is i

Numeric types with flipped back sign bit

Is there a way to create numeric column in Apache Phoenix table or view with flipped back sign bit? I want to used TINYINT type for instance but in my HBase table is written value with flipped sign bit: ROW COLUMN+CELL 1 column=0:_0, timestamp=1435

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605874#comment-14605874 ] Josh Mahonin commented on PHOENIX-1659: --- Pushed to master, 4.4 and 4.x branches. H

[jira] [Commented] (PHOENIX-2036) PhoenixConfigurationUtil should provide a pre-normalize table name to PhoenixRuntime

[ https://issues.apache.org/jira/browse/PHOENIX-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605866#comment-14605866 ] James Taylor commented on PHOENIX-2036: --- FYI, [~tdsilva] is working on a change th

[jira] [Commented] (PHOENIX-2067) Sort order incorrect for variable length DESC columns

[ https://issues.apache.org/jira/browse/PHOENIX-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605762#comment-14605762 ] James Taylor commented on PHOENIX-2067: --- This bug potentially affects any PK colum

[jira] [Updated] (PHOENIX-2067) Sort order incorrect for variable length DESC columns

[ https://issues.apache.org/jira/browse/PHOENIX-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2067: -- Summary: Sort order incorrect for variable length DESC columns (was: Incorrect order while us

[jira] [Commented] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605684#comment-14605684 ] James Taylor commented on PHOENIX-1659: --- +1. This can get checked into all 4.x and

[jira] [Updated] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-1659: -- Attachment: PHOENIX-1659-v2.patch Updated patch with tests to ensure lookup by column name / p

[jira] [Updated] (PHOENIX-1659) PhoenixDatabaseMetaData.getColumns does not return REMARKS column

[ https://issues.apache.org/jira/browse/PHOENIX-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-1659: -- Attachment: (was: PHOENIX-1659.patch) > PhoenixDatabaseMetaData.getColumns does not return