[jira] [Commented] (PHOENIX-2178) Tracing - total time listed for a certain trace does not correlate with query wall clock time

[ https://issues.apache.org/jira/browse/PHOENIX-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328898#comment-15328898 ] Pranavan commented on PHOENIX-2178: --- I have created a pull, but it needs some HTrace l

[GitHub] phoenix pull request #173: Milli time changed to nano time - Do not change

GitHub user Pranavan135 opened a pull request: https://github.com/apache/phoenix/pull/173 Milli time changed to nano time - Do not change This PR needs some HTrace Level changes. I made those changes. We can merge the PR when HTrace is updated with my PR. You can merge this pull r

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328827#comment-15328827 ] Lars Hofhansl commented on PHOENIX-2992: Ran the unittests as well (mvn package

[jira] [Resolved] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2983. --- Resolution: Fixed > ClassCastException on auto coerce of BIGINT to DECIMAL > ---

[jira] [Resolved] (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 resolved PHOENIX-2961. --- Resolution: Fixed > select on a composite primary key fails when DESC is set in the table >

[jira] [Resolved] (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 resolved PHOENIX-2920. --- Resolution: Fixed > Incorrect Queries on Multi-tenant tables with WHERE clause containing Ro

[jira] [Resolved] (PHOENIX-2994) Coalesce function may return null

[ https://issues.apache.org/jira/browse/PHOENIX-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-2994. --- Resolution: Fixed > Coalesce function may return null > - >

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328683#comment-15328683 ] James Taylor commented on PHOENIX-2992: --- FWIW, you should always run a {{mvn packa

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328649#comment-15328649 ] Lars Hofhansl commented on PHOENIX-2992: I ran DistinctPrefixFilterIT,WhereOpti

[jira] [Updated] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2992: --- Issue Type: Improvement (was: Sub-task) Parent: (was: PHOENIX-258) > Remove ORD

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328589#comment-15328589 ] James Taylor commented on PHOENIX-2992: --- +1 for v1. The AVG compiles to two aggreg

[jira] [Updated] (PHOENIX-2992) Remove ORDER BY from aggregate-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2992: --- Summary: Remove ORDER BY from aggregate-only SELECT statements (was: Remove ORDER BY from C

[jira] [Updated] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2992: --- Attachment: 2992-v1.txt -v1 does that Passes all tests that I ran. If you look at {{WhereOp

[jira] [Updated] (PHOENIX-2995) Write performance severely degrades with large number of views

[ https://issues.apache.org/jira/browse/PHOENIX-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-2995: Assignee: James Taylor > Write performance severely degrades with large number of views >

[jira] [Updated] (PHOENIX-2995) Write performance severely degrades with large number of views

[ https://issues.apache.org/jira/browse/PHOENIX-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-2995: Description: Write performance for each 1K batch degrades significantly when there are *10

[jira] [Updated] (PHOENIX-2995) Write performance severely degrades with large number of views

[ https://issues.apache.org/jira/browse/PHOENIX-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mujtaba Chohan updated PHOENIX-2995: Attachment: upsert_rate.png > Write performance severely degrades with large number of vie

[jira] [Created] (PHOENIX-2995) Write performance severely degrades with large number of views

Mujtaba Chohan created PHOENIX-2995: --- Summary: Write performance severely degrades with large number of views Key: PHOENIX-2995 URL: https://issues.apache.org/jira/browse/PHOENIX-2995 Project: Phoe

[jira] [Updated] (PHOENIX-2994) Coalesce function may return null

[ https://issues.apache.org/jira/browse/PHOENIX-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2994: -- Attachment: PHOENIX-2994.patch Please review, [~samarthjain]. > Coalesce function may return

[jira] [Created] (PHOENIX-2994) Coalesce function may return null

James Taylor created PHOENIX-2994: - Summary: Coalesce function may return null Key: PHOENIX-2994 URL: https://issues.apache.org/jira/browse/PHOENIX-2994 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

[ https://issues.apache.org/jira/browse/PHOENIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poorna Chandra updated PHOENIX-2993: Attachment: ApacheTephraAutomaticInvalidListPruning.pdf First cut of design document. I'm

[jira] [Created] (PHOENIX-2993) Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped

Poorna Chandra created PHOENIX-2993: --- Summary: Tephra: Prune invalid transaction set once all data for a given invalid transaction has been dropped Key: PHOENIX-2993 URL: https://issues.apache.org/jira/browse/PH

[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 (was: SFDC verify) > Indexes on tenant views not working correctly > ---

[jira] [Resolved] (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 resolved PHOENIX-2277. --- Resolution: Duplicate Fix Version/s: (was: 4.8.0) This is a duplicate of PHOENIX-

[jira] [Commented] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328307#comment-15328307 ] Samarth Jain commented on PHOENIX-2983: --- +1 > ClassCastException on auto coerce o

[jira] [Updated] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2983: -- Attachment: PHOENIX-2983_v3.patch Final patch > ClassCastException on auto coerce of BIGINT t

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328277#comment-15328277 ] James Taylor commented on PHOENIX-2992: --- We should remove the ORDER BY for all cas

[jira] [Commented] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328267#comment-15328267 ] Samarth Jain commented on PHOENIX-2983: --- Looks good, [~jamestaylor]. One minor sug

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328256#comment-15328256 ] Lars Hofhansl commented on PHOENIX-2992: The patch as is _only_ removes the ORDE

[jira] [Updated] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2983: -- Attachment: PHOENIX-2983_v2.patch Thanks for the review, [~samarthjain]. Here's an updated pat

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15328249#comment-15328249 ] Samarth Jain commented on PHOENIX-2920: --- +1 > Incorrect Queries on Multi-tenant t

[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=15328235#comment-15328235 ] Samarth Jain commented on PHOENIX-2961: --- +1, looks good, [~jamestaylor] > select

[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: -- Attachment: PHOENIX-2961.patch Please review, [~samarthjain]. > select on a composite primary

[jira] [Updated] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2992: --- Attachment: 2989-orderby-v3.txt Here's the patch from PHOENIX-2989 > Remove ORDER BY from C

[jira] [Assigned] (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 reassigned PHOENIX-2961: - Assignee: James Taylor (was: Samarth Jain) > select on a composite primary key fails w

[jira] [Comment Edited] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328183#comment-15328183 ] Lars Hofhansl edited comment on PHOENIX-2992 at 6/13/16 8:25 PM: -

[jira] [Commented] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328183#comment-15328183 ] Lars Hofhansl commented on PHOENIX-2992: Thinking on it more... Can we always re

[jira] [Updated] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

[ https://issues.apache.org/jira/browse/PHOENIX-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2992: --- Description: In PHOENIX-2989 we observe that any ORDER BY clause can simply be removed from

[jira] [Created] (PHOENIX-2992) Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements

Lars Hofhansl created PHOENIX-2992: -- Summary: Remove ORDER BY from COUNT(DISTINCT...)-only SELECT statements Key: PHOENIX-2992 URL: https://issues.apache.org/jira/browse/PHOENIX-2992 Project: Phoenix

[jira] [Created] (PHOENIX-2991) Add missing documentation for functions

Josh Elser created PHOENIX-2991: --- Summary: Add missing documentation for functions Key: PHOENIX-2991 URL: https://issues.apache.org/jira/browse/PHOENIX-2991 Project: Phoenix Issue Type: Task

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328062#comment-15328062 ] James Taylor commented on PHOENIX-2989: --- +1. Nice test :-) I like the idea of com

[jira] [Updated] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2989: --- Attachment: 2989-orderby-v3.txt -v3 should do it then. Thanks for writing the test for me :)

[jira] [Updated] (PHOENIX-2990) Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance

[ https://issues.apache.org/jira/browse/PHOENIX-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-2990: Attachment: PHOENIX-2990.diff Some quick updates to the website's Data Type and Function reference

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328025#comment-15328025 ] James Taylor commented on PHOENIX-2989: --- Patch looks good. Here's a good test you

[jira] [Updated] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-2989: --- Attachment: 2989-orderby-v2.txt -v2 does that. Can you suggest a good test? > Allow Distinc

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327976#comment-15327976 ] Lars Hofhansl commented on PHOENIX-2989: What's a good way to test that the aggr

[jira] [Created] (PHOENIX-2990) Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance

Josh Elser created PHOENIX-2990: --- Summary: Ensure documentation on "time/date" datatypes/functions acknowledge lack of JDBC compliance Key: PHOENIX-2990 URL: https://issues.apache.org/jira/browse/PHOENIX-2990

[jira] [Commented] (PHOENIX-2983) ClassCastException on auto coerce of BIGINT to DECIMAL

[ https://issues.apache.org/jira/browse/PHOENIX-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327749#comment-15327749 ] Samarth Jain commented on PHOENIX-2983: --- [~jamestaylor] - considering one can invo

[jira] [Commented] (PHOENIX-2985) Phoenix-Spark IT for non-existent column fails on Apache Spark 1.6

[ https://issues.apache.org/jira/browse/PHOENIX-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327756#comment-15327756 ] Hudson commented on PHOENIX-2985: - SUCCESS: Integrated in Phoenix-master #1258 (See [ht

[jira] [Commented] (PHOENIX-2985) Phoenix-Spark IT for non-existent column fails on Apache Spark 1.6

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

[jira] [Assigned] (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 reassigned PHOENIX-2920: - Assignee: James Taylor (was: Samarth Jain) > Incorrect Queries on Multi-tenant tables

[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: -- Attachment: PHOENIX-2920.patch Please review, [~samarthjain]. > Incorrect Queries on Multi-te

[jira] [Commented] (PHOENIX-2985) Phoenix-Spark IT for non-existent column fails on Apache Spark 1.6

[ https://issues.apache.org/jira/browse/PHOENIX-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327565#comment-15327565 ] James Taylor commented on PHOENIX-2985: --- +1 > Phoenix-Spark IT for non-existent c

Re: PHOENIX-2178

Yes, I think that makes sense. Thanks, James On Monday, June 13, 2016, Pranavan Theivendiram wrote: > Hi James, > > I found the solution for $subject. I added a comment on the jira issue. > Shall we go ahead with that? > > JIRA 2178 - https://issues.apache.org/jira/browse/PHOENIX-2178 > > Thanks

PHOENIX-2178

Hi James, I found the solution for $subject. I added a comment on the jira issue. Shall we go ahead with that? JIRA 2178 - https://issues.apache.org/jira/browse/PHOENIX-2178 Thanks *T. Pranavan* *Junior Consultant | Department of Computer Science & Engineering ,University of Moratuwa* *Mobile| *

[jira] [Updated] (PHOENIX-2985) Phoenix-Spark IT for non-existent column fails on Apache Spark 1.6

[ https://issues.apache.org/jira/browse/PHOENIX-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin updated PHOENIX-2985: -- Attachment: PHOENIX-2985.patch > Phoenix-Spark IT for non-existent column fails on Apache Spar

[jira] [Assigned] (PHOENIX-2985) Phoenix-Spark IT for non-existent column fails on Apache Spark 1.6

[ https://issues.apache.org/jira/browse/PHOENIX-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Mahonin reassigned PHOENIX-2985: - Assignee: Josh Mahonin > Phoenix-Spark IT for non-existent column fails on Apache Spark

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327541#comment-15327541 ] James Taylor commented on PHOENIX-2989: --- I'd do it in the same, as it's related to

[jira] [Commented] (PHOENIX-2178) Tracing - total time listed for a certain trace does not correlate with query wall clock time

[ https://issues.apache.org/jira/browse/PHOENIX-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327540#comment-15327540 ] Pranavan commented on PHOENIX-2178: --- Hi James and Mujtaba Chohan. I found the solution

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327483#comment-15327483 ] Lars Hofhansl commented on PHOENIX-2989: I see. Was going to ask about that comm

[jira] [Commented] (PHOENIX-2834) Support Phoenix over CDH 5.7.0

[ https://issues.apache.org/jira/browse/PHOENIX-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327408#comment-15327408 ] Sean Busbey commented on PHOENIX-2834: -- got it. Thanks for the suggestion! > Suppo

[jira] [Commented] (PHOENIX-2989) Allow DistinctPrefixFilter optimization when HAVING clause only reference COUNT(DISTINCT)

[ https://issues.apache.org/jira/browse/PHOENIX-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326914#comment-15326914 ] James Taylor commented on PHOENIX-2989: --- You should also override the addExpressio