[jira] [Updated] (PHOENIX-2368) Call Driver.accept() in Driver.getConnection and return null if false

[ https://issues.apache.org/jira/browse/PHOENIX-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated PHOENIX-2368: Attachment: PHOENIX-2368.patch Patch for master. > Call Driver.accept()

[jira] [Commented] (PHOENIX-2368) Call Driver.accept() in Driver.getConnection and return null if false

[ https://issues.apache.org/jira/browse/PHOENIX-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086990#comment-15086990 ] James Taylor commented on PHOENIX-2368: --- Is this ready to go, [~ram_krish]? Should

[jira] [Commented] (PHOENIX-2364) timestamp type primary key desc error

[ https://issues.apache.org/jira/browse/PHOENIX-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086979#comment-15086979 ] James Taylor commented on PHOENIX-2364: --- Other than fixing the test so that it's n

[jira] [Resolved] (PHOENIX-2578) PhoenixIndexRPCSchedulerTest isn't shutting down the thread pool

[ https://issues.apache.org/jira/browse/PHOENIX-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-2578. --- Resolution: Fixed Fix Version/s: 4.7.0 > PhoenixIndexRPCSchedulerTest isn't shutting

[jira] [Commented] (PHOENIX-2578) PhoenixIndexRPCSchedulerTest isn't shutting down the thread pool

[ https://issues.apache.org/jira/browse/PHOENIX-2578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086893#comment-15086893 ] James Taylor commented on PHOENIX-2578: --- +1 > PhoenixIndexRPCSchedulerTest isn't

[jira] [Updated] (PHOENIX-2578) PhoenixIndexRPCSchedulerTest isn't shutting down the thread pool

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

[jira] [Commented] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

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

[jira] [Commented] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

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

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

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

[jira] [Updated] (PHOENIX-2357) Prevent queries from failing because of scanners running into lease expiration

[ https://issues.apache.org/jira/browse/PHOENIX-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2357: -- Fix Version/s: 4.7.0 > Prevent queries from failing because of scanners running into lease exp

[jira] [Updated] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2570: -- Fix Version/s: 4.7.0 > Start transaction manager only when needed and reduce number of threads

[jira] [Updated] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

[ https://issues.apache.org/jira/browse/PHOENIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2576: -- Fix Version/s: 4.7.0 > Mark scanner lease renewal threads as daemon threads >

[jira] [Updated] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

[ https://issues.apache.org/jira/browse/PHOENIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2575: -- Fix Version/s: 4.7.0 > Prevent LocalIndexIT from hanging indefinitely > --

[jira] [Resolved] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

[ https://issues.apache.org/jira/browse/PHOENIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-2576. --- Resolution: Fixed > Mark scanner lease renewal threads as daemon threads > -

[jira] [Resolved] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

[ https://issues.apache.org/jira/browse/PHOENIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain resolved PHOENIX-2575. --- Resolution: Fixed > Prevent LocalIndexIT from hanging indefinitely > ---

[jira] [Updated] (PHOENIX-2577) Use same timestamp technique for alter table as create table

[ https://issues.apache.org/jira/browse/PHOENIX-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2577: -- Attachment: PHOENIX-2577.patch [~tdsilva] - please review. > Use same timestamp technique for

[jira] [Created] (PHOENIX-2577) Use same timestamp technique for alter table as create table

James Taylor created PHOENIX-2577: - Summary: Use same timestamp technique for alter table as create table Key: PHOENIX-2577 URL: https://issues.apache.org/jira/browse/PHOENIX-2577 Project: Phoenix

[jira] [Commented] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

[ https://issues.apache.org/jira/browse/PHOENIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086712#comment-15086712 ] James Taylor commented on PHOENIX-2575: --- +1 > Prevent LocalIndexIT from hanging i

[jira] [Commented] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

[ https://issues.apache.org/jira/browse/PHOENIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086711#comment-15086711 ] James Taylor commented on PHOENIX-2576: --- +1 > Mark scanner lease renewal threads

[jira] [Commented] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

[ https://issues.apache.org/jira/browse/PHOENIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086710#comment-15086710 ] James Taylor commented on PHOENIX-2576: --- +1 > Mark scanner lease renewal threads

[jira] [Commented] (PHOENIX-2143) Use guidepost bytes instead of region name in stats primary key

[ https://issues.apache.org/jira/browse/PHOENIX-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086706#comment-15086706 ] James Taylor commented on PHOENIX-2143: --- This looks very good, [~ankit.singhal]. F

[jira] [Updated] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

[ https://issues.apache.org/jira/browse/PHOENIX-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2576: -- Attachment: PHOENIX-2576.patch [~jamestaylor], please review. > Mark scanner lease renewal th

[jira] [Created] (PHOENIX-2576) Mark scanner lease renewal threads as daemon threads

Samarth Jain created PHOENIX-2576: - Summary: Mark scanner lease renewal threads as daemon threads Key: PHOENIX-2576 URL: https://issues.apache.org/jira/browse/PHOENIX-2576 Project: Phoenix Is

[jira] [Updated] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

[ https://issues.apache.org/jira/browse/PHOENIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2575: -- Attachment: PHOENIX-2575.patch [~jamestaylor], please review. > Prevent LocalIndexIT from han

[jira] [Created] (PHOENIX-2575) Prevent LocalIndexIT from hanging indefinitely

Samarth Jain created PHOENIX-2575: - Summary: Prevent LocalIndexIT from hanging indefinitely Key: PHOENIX-2575 URL: https://issues.apache.org/jira/browse/PHOENIX-2575 Project: Phoenix Issue Ty

[jira] [Commented] (PHOENIX-2572) Backward compatibility fails between v4.5.0 and 4.7 snapshot

[ https://issues.apache.org/jira/browse/PHOENIX-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086677#comment-15086677 ] James Taylor commented on PHOENIX-2572: --- Would you mind taking a look at this, [~t

[jira] [Created] (PHOENIX-2574) Pherf Unit Test fails testCurrentDataGenerator

Cody Marcel created PHOENIX-2574: Summary: Pherf Unit Test fails testCurrentDataGenerator Key: PHOENIX-2574 URL: https://issues.apache.org/jira/browse/PHOENIX-2574 Project: Phoenix Issue Typ

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086469#comment-15086469 ] James Taylor commented on PHOENIX-2570: --- Never mind - your change is correct as yo

[jira] [Updated] (PHOENIX-2573) Pherf IT test fails

[ https://issues.apache.org/jira/browse/PHOENIX-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Marcel updated PHOENIX-2573: - Summary: Pherf IT test fails (was: PHerf IT test fails) > Pherf IT test fails > ---

[jira] [Created] (PHOENIX-2573) PHerf IT test fails

Cody Marcel created PHOENIX-2573: Summary: PHerf IT test fails Key: PHOENIX-2573 URL: https://issues.apache.org/jira/browse/PHOENIX-2573 Project: Phoenix Issue Type: Bug Reporter:

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086412#comment-15086412 ] James Taylor commented on PHOENIX-2570: --- Patch looks good, but wouldn't it be the

[jira] [Commented] (PHOENIX-2529) Fixing date generation pattern in Phoenix-Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086329#comment-15086329 ] Cody Marcel commented on PHOENIX-2529: -- Yes I did it to update the commit message s

[jira] [Updated] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2570: -- Attachment: PHOENIX-2570_4.x-HBase-0.98_v2.patch Updated patch with review comments. > Start

[jira] [Commented] (PHOENIX-2529) Fixing date generation pattern in Phoenix-Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086277#comment-15086277 ] James Taylor commented on PHOENIX-2529: --- Looks like you did a force push. Why? Was

[jira] [Commented] (PHOENIX-2529) Fixing date generation pattern in Phoenix-Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086258#comment-15086258 ] Cody Marcel commented on PHOENIX-2529: -- Iv'e run the failing IT tests locally both

[jira] [Commented] (PHOENIX-2299) Support CURRENT_DATE() in Pherf data upserts

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

[jira] [Commented] (PHOENIX-2529) Fixing date generation pattern in Phoenix-Pherf

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

[jira] [Updated] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-1311: - Assignee: Ankit Singhal (was: rajeshbabu) > HBase namespaces surfaced i

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086109#comment-15086109 ] Thomas D'Silva commented on PHOENIX-2570: - Looks good. We were conditionally ini

[jira] [Commented] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086086#comment-15086086 ] Ankit Singhal commented on PHOENIX-1311: [~rajeshbabu]/[~jamestaylor], PFA .. wi

[jira] [Created] (PHOENIX-2572) Backward compatibility fails between v4.5.0 and 4.7 snapshot

Mujtaba Chohan created PHOENIX-2572: --- Summary: Backward compatibility fails between v4.5.0 and 4.7 snapshot Key: PHOENIX-2572 URL: https://issues.apache.org/jira/browse/PHOENIX-2572 Project: Phoenix

[jira] [Updated] (PHOENIX-1311) HBase namespaces surfaced in phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-1311: --- Attachment: PHOENIX-1311_wip.patch > HBase namespaces surfaced in phoenix >

[jira] [Comment Edited] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086036#comment-15086036 ] Samarth Jain edited comment on PHOENIX-2570 at 1/6/16 7:06 PM: ---

[jira] [Commented] (PHOENIX-1544) Support indexing of an ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086041#comment-15086041 ] ramkrishna.s.vasudevan commented on PHOENIX-1544: - Generally how does in

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086036#comment-15086036 ] Samarth Jain commented on PHOENIX-2570: --- - Transaction manager is now started only

[jira] [Commented] (PHOENIX-1966) Support HBase non-default Namespace

[ https://issues.apache.org/jira/browse/PHOENIX-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086024#comment-15086024 ] James Taylor commented on PHOENIX-1966: --- Good idea, [~mathias.kluba]. I've filed P

[jira] [Created] (PHOENIX-2571) Support specifying a default schema

James Taylor created PHOENIX-2571: - Summary: Support specifying a default schema Key: PHOENIX-2571 URL: https://issues.apache.org/jira/browse/PHOENIX-2571 Project: Phoenix Issue Type: Bug

[jira] [Commented] (PHOENIX-2529) Fixing date generation pattern in Phoenix-Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086010#comment-15086010 ] Cody Marcel commented on PHOENIX-2529: -- This patching is working on both branches f

[jira] [Comment Edited] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085998#comment-15085998 ] James Taylor edited comment on PHOENIX-2570 at 1/6/16 6:30 PM: ---

[jira] [Commented] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085998#comment-15085998 ] James Taylor commented on PHOENIX-2570: --- Awesome, [~samarthjain]. Thanks so much.

[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&focusedCommentId=15085975#comment-15085975 ] Josh Mahonin commented on PHOENIX-2535: --- The day job has taken an interesting turn

[jira] [Updated] (PHOENIX-1544) Support indexing of an ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1544: -- Description: Needs to be fleshed out more, but I think we could support indexing array data t

[jira] [Updated] (PHOENIX-1544) Support indexing of an ARRAY

[ https://issues.apache.org/jira/browse/PHOENIX-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1544: -- Summary: Support indexing of an ARRAY (was: Support exploding ARRAY when indexing for immutab

[jira] [Commented] (PHOENIX-2221) Option to make data regions not writable when index regions are not available

[ https://issues.apache.org/jira/browse/PHOENIX-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085858#comment-15085858 ] Alicia Ying Shu commented on PHOENIX-2221: -- Yes. > Option to make data regions

[jira] [Commented] (PHOENIX-1966) Support HBase non-default Namespace

[ https://issues.apache.org/jira/browse/PHOENIX-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085790#comment-15085790 ] mathias kluba commented on PHOENIX-1966: Not sure that it's duplicated. We could

[jira] [Commented] (PHOENIX-2568) phoenix-spark: client-spark JAR conflicting with some Spark distributions

[ https://issues.apache.org/jira/browse/PHOENIX-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085650#comment-15085650 ] Josh Mahonin commented on PHOENIX-2568: --- Yup, it actually works the same as before

[jira] [Commented] (PHOENIX-2357) Prevent queries from failing because of scanners running into lease expiration

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

[jira] [Updated] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2570: -- Attachment: PHOENIX-2570_4.x-HBase-0.98.patch Correct patch. With this patch, I was able to di

[jira] [Updated] (PHOENIX-2570) Start transaction manager only when needed and reduce number of threads spawned for tests

[ https://issues.apache.org/jira/browse/PHOENIX-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-2570: -- Attachment: (was: PHOENIX-2570_4.x-HBase-0.98.patch) > Start transaction manager only when

[jira] [Commented] (PHOENIX-2364) timestamp type primary key desc error

[ https://issues.apache.org/jira/browse/PHOENIX-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085304#comment-15085304 ] ramkrishna.s.vasudevan commented on PHOENIX-2364: - Hmm I see. [~pierre.l

[jira] [Comment Edited] (PHOENIX-2364) timestamp type primary key desc error

[ https://issues.apache.org/jira/browse/PHOENIX-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085234#comment-15085234 ] Pierre Lacave edited comment on PHOENIX-2364 at 1/6/16 8:57 AM: --

[jira] [Commented] (PHOENIX-2364) timestamp type primary key desc error

[ https://issues.apache.org/jira/browse/PHOENIX-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085234#comment-15085234 ] Pierre Lacave commented on PHOENIX-2364: You are correct that there is an issue

[jira] [Updated] (PHOENIX-2364) timestamp type primary key desc error

[ https://issues.apache.org/jira/browse/PHOENIX-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated PHOENIX-2364: Attachment: PHOENIX-2364_1.patch The ts problem was only with windows I be

[jira] [Commented] (PHOENIX-2364) timestamp type primary key desc error

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