[jira] [Commented] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340655#comment-16340655 ] Sergey Soldatov commented on PHOENIX-4560: -- [~jamestaylor] I was thinking about this check but

[jira] [Updated] (PHOENIX-4558) Add start/stop row for partial index rebuilder scan

[ https://issues.apache.org/jira/browse/PHOENIX-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4558: -- Description: I believe that only global tables would have set the INDEX_DISABLE_TIMESTAMP,

[jira] [Resolved] (PHOENIX-4064) Why the group by the index field will execute scan over table.

[ https://issues.apache.org/jira/browse/PHOENIX-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-4064. --- Resolution: Invalid Please ask questions on the mailing list (and make sure to include your

[jira] [Commented] (PHOENIX-4064) Why the group by the index field will execute scan over table.

[ https://issues.apache.org/jira/browse/PHOENIX-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340566#comment-16340566 ] jifei_yang commented on PHOENIX-4064: - Thanks. > Why the group by the index field will execute

precommit broken

It seems that our precommit Jenkins build is no longer working. Does anyone know why? Could it be related to moving master to HBase 1.4?

[jira] [Commented] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340518#comment-16340518 ] James Taylor commented on PHOENIX-4560: --- No problem, [~sergey.soldatov]. You did the hard part by

[jira] [Updated] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4560: -- Attachment: PHOENIX-4560_v2.patch > ORDER BY with GROUP BY doesn't work if there is WHERE on

[jira] [Commented] (PHOENIX-4130) Avoid server retries for mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340437#comment-16340437 ] Vincent Poon commented on PHOENIX-4130: --- [~jamestaylor] Attached a v3 github PR.  It has all the

[jira] [Updated] (PHOENIX-4130) Avoid server retries for mutable indexes

[ https://issues.apache.org/jira/browse/PHOENIX-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Poon updated PHOENIX-4130: -- Attachment: PHOENIX-4130.v3.master.patch > Avoid server retries for mutable indexes >

[jira] [Commented] (PHOENIX-4130) Avoid server retries for mutable indexes

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

[GitHub] phoenix pull request #290: PHOENIX-4130 Avoid server retries for mutable ind...

GitHub user vincentpoon opened a pull request: https://github.com/apache/phoenix/pull/290 PHOENIX-4130 Avoid server retries for mutable indexes You can merge this pull request into a Git repository by running: $ git pull https://github.com/vincentpoon/phoenix PHOENIX-4130

[jira] [Commented] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340395#comment-16340395 ] Sergey Soldatov commented on PHOENIX-4560: -- [~jamestaylor] Thank you for such a quick fix!

[jira] [Commented] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340363#comment-16340363 ] James Taylor commented on PHOENIX-4560: --- Yep, your analysis is spot on, [~sergey.soldatov]. Nice

[jira] [Updated] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4560: -- Attachment: PHOENIX-4560_v1.patch > ORDER BY with GROUP BY doesn't work if there is WHERE on

[jira] [Assigned] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

[ https://issues.apache.org/jira/browse/PHOENIX-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-4560: - Assignee: James Taylor > ORDER BY with GROUP BY doesn't work if there is WHERE on pk

[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340251#comment-16340251 ] Pedro Boado edited comment on PHOENIX-4553 at 1/25/18 11:36 PM: - EDIT

[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340251#comment-16340251 ] Pedro Boado edited comment on PHOENIX-4553 at 1/25/18 11:33 PM: - EDIT

[jira] [Comment Edited] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340251#comment-16340251 ] Pedro Boado edited comment on PHOENIX-4553 at 1/25/18 11:07 PM: - EDIT

[jira] [Updated] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pedro Boado updated PHOENIX-4553: - Priority: Minor (was: Major) > HBase Master could not start with activated APACHE_PHOENIX

[jira] [Commented] (PHOENIX-4553) HBase Master could not start with activated APACHE_PHOENIX parcel

[ https://issues.apache.org/jira/browse/PHOENIX-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340251#comment-16340251 ] Pedro Boado commented on PHOENIX-4553: -- [~neospyk] I just noticed the folder in your log

[jira] [Created] (PHOENIX-4560) ORDER BY with GROUP BY doesn't work if there is WHERE on pk column

Sergey Soldatov created PHOENIX-4560: Summary: ORDER BY with GROUP BY doesn't work if there is WHERE on pk column Key: PHOENIX-4560 URL: https://issues.apache.org/jira/browse/PHOENIX-4560

[jira] [Created] (PHOENIX-4559) Support local indexes on views

James Taylor created PHOENIX-4559: - Summary: Support local indexes on views Key: PHOENIX-4559 URL: https://issues.apache.org/jira/browse/PHOENIX-4559 Project: Phoenix Issue Type: Improvement

[jira] [Commented] (PHOENIX-4559) Support local indexes on views

[ https://issues.apache.org/jira/browse/PHOENIX-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340122#comment-16340122 ] James Taylor commented on PHOENIX-4559: --- FYI, [~lhofhansl]. > Support local indexes on views >

[jira] [Created] (PHOENIX-4558) Add start/stop row for partial index rebuilder scan

James Taylor created PHOENIX-4558: - Summary: Add start/stop row for partial index rebuilder scan Key: PHOENIX-4558 URL: https://issues.apache.org/jira/browse/PHOENIX-4558 Project: Phoenix

[jira] [Commented] (PHOENIX-4557) Move index state related columns to their own table

[ https://issues.apache.org/jira/browse/PHOENIX-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340098#comment-16340098 ] James Taylor commented on PHOENIX-4557: --- We may only set INDEX_DISABLE_TIMESTAMP on rows with a

[jira] [Created] (PHOENIX-4557) Move index state related columns to their own table

James Taylor created PHOENIX-4557: - Summary: Move index state related columns to their own table Key: PHOENIX-4557 URL: https://issues.apache.org/jira/browse/PHOENIX-4557 Project: Phoenix

[jira] [Commented] (PHOENIX-3173) Store views in a separate hbase table from physical tables

[ https://issues.apache.org/jira/browse/PHOENIX-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16340087#comment-16340087 ] James Taylor commented on PHOENIX-3173: --- Note that this JIRA requires PHOENIX-3534. > Store views

[jira] [Commented] (PHOENIX-4550) Ensure storage is dense when base table has many views

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339850#comment-16339850 ] Thomas D'Silva commented on PHOENIX-4550: - The scope of SINGLE_CELL_PER_LEVEL is much larger,

[jira] [Commented] (PHOENIX-4550) Ensure storage is dense when base table has many views

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339821#comment-16339821 ] James Taylor commented on PHOENIX-4550: --- I'm still thinking that having a MAX_COLUMNS declaration

[jira] [Commented] (PHOENIX-4552) Allow ROW_TIMESTAMP declaration for non PK column

[ https://issues.apache.org/jira/browse/PHOENIX-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339795#comment-16339795 ] James Taylor commented on PHOENIX-4552: --- Had one more thought, [~spetschu]: this optimization

[jira] [Commented] (PHOENIX-4550) Ensure storage is dense when base table has many views

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339788#comment-16339788 ] Thomas D'Silva commented on PHOENIX-4550: - Yes I think it makes sense to implement this as a new

[jira] [Updated] (PHOENIX-4550) Ensure storage is dense when base table has many views

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4550: -- Summary: Ensure storage is dense when base table has many views (was: Allow declaration of

[jira] [Commented] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339737#comment-16339737 ] James Taylor commented on PHOENIX-4550: --- I like the cell per level idea. That'll keep the storage

[jira] [Updated] (PHOENIX-4555) Only mark view as updatable if rows cannot overlap with other updatable views

[ https://issues.apache.org/jira/browse/PHOENIX-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-4555: Issue Type: Sub-task (was: Bug) Parent: PHOENIX-1508 > Only mark view as

[jira] [Commented] (PHOENIX-4550) Allow declaration of max columns on base physical table

[ https://issues.apache.org/jira/browse/PHOENIX-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339711#comment-16339711 ] Thomas D'Silva commented on PHOENIX-4550: - The map idea won't work as it doesn't solve the issue