[jira] [Commented] (PHOENIX-3189) HBase/ZooKeeper connection leaks when providing principal/keytab in JDBC url

[ https://issues.apache.org/jira/browse/PHOENIX-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451082#comment-15451082 ] ASF GitHub Bot commented on PHOENIX-3189: - Github user joshelser commented on the issue:

[GitHub] phoenix issue #191: PHOENIX-3189 Perform Kerberos login before ConnectionInf...

Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/191 > Thanks for pursuing this tricky issue, @joshelser. I think what you have here is definitely an improvement and should be pulled in for 4.8.1 Thanks as always for your careful eye.

[jira] [Commented] (PHOENIX-3189) HBase/ZooKeeper connection leaks when providing principal/keytab in JDBC url

[ https://issues.apache.org/jira/browse/PHOENIX-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451068#comment-15451068 ] ASF GitHub Bot commented on PHOENIX-3189: - Github user joshelser commented on the issue:

[GitHub] phoenix issue #191: PHOENIX-3189 Perform Kerberos login before ConnectionInf...

Github user joshelser commented on the issue: https://github.com/apache/phoenix/pull/191 > Did you get to look at the comment regarding the user login ? Assuming you mean the below.. > With that said I am not sure that you can support multiple users and support

[jira] [Commented] (PHOENIX-3218) First draft of Phoenix Tuning Guide

[ https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15451055#comment-15451055 ] Josh Elser commented on PHOENIX-3218: - Would it make sense to try to move all of the JVM and

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450622#comment-15450622 ] Mujtaba Chohan commented on PHOENIX-3228: - Yes it was originally set as index showed poor

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450598#comment-15450598 ] Hudson commented on PHOENIX-3223: - FAILURE: Integrated in Jenkins build Phoenix-4.8-HBase-1.2 #2 (See

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450589#comment-15450589 ] Lars Hofhansl commented on PHOENIX-3228: Yeah... Will run the tests... Didn't even compile, yet

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450579#comment-15450579 ] Hudson commented on PHOENIX-3223: - FAILURE: Integrated in Jenkins build Phoenix-master #1376 (See

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450542#comment-15450542 ] James Taylor commented on PHOENIX-3228: --- Can you do a test run too to make sure you're not

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450533#comment-15450533 ] James Taylor commented on PHOENIX-3228: --- If this is causing problems (or even not helping), then

[jira] [Commented] (PHOENIX-3218) First draft of Phoenix Tuning Guide

[ https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450527#comment-15450527 ] James Taylor commented on PHOENIX-3218: --- Thanks for putting this together, [~pconrad]. I think

[jira] [Updated] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3228: --- Attachment: 3228-remove.txt FWIW, here's a patch that removes everything. > Index table

[jira] [Updated] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3228: --- Attachment: (was: 3228-remove.txt) > Index table are configured with a custom/smaller

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450500#comment-15450500 ] Lars Hofhansl commented on PHOENIX-3228: Are you OK with just removing this logic?

[jira] [Resolved] (PHOENIX-3217) Phoenix sets MAX_FILESIZE table attribute for index tables

[ https://issues.apache.org/jira/browse/PHOENIX-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved PHOENIX-3217. - Resolution: Duplicate Dup of PHOENIX-3228 > Phoenix sets MAX_FILESIZE table attribute

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450492#comment-15450492 ] James Taylor commented on PHOENIX-3228: --- There's also this code in MetaDataClient that sets the

[jira] [Updated] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3228: --- Fix Version/s: 4.8.1 4.9.0 > Index table are configured with a

[jira] [Commented] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

[ https://issues.apache.org/jira/browse/PHOENIX-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450468#comment-15450468 ] Lars Hofhansl commented on PHOENIX-3228: For 4.8.1 we should set the default to 100% (and not

[jira] [Commented] (PHOENIX-3224) Observations from large scale testing.

[ https://issues.apache.org/jira/browse/PHOENIX-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450454#comment-15450454 ] James Taylor commented on PHOENIX-3224: --- Would be good to get more info on bigger joins. Using the

[jira] [Created] (PHOENIX-3228) Index table are configured with a custom/smaller MAX_FILESIZE

Lars Hofhansl created PHOENIX-3228: -- Summary: Index table are configured with a custom/smaller MAX_FILESIZE Key: PHOENIX-3228 URL: https://issues.apache.org/jira/browse/PHOENIX-3228 Project: Phoenix

[jira] [Commented] (PHOENIX-3227) OFFSET is very slow at scale

[ https://issues.apache.org/jira/browse/PHOENIX-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450425#comment-15450425 ] James Taylor commented on PHOENIX-3227: --- Not sure if [~an...@apache.org] has anything in mind to

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450377#comment-15450377 ] ASF GitHub Bot commented on PHOENIX-3223: - Github user asfgit closed the pull request at:

[GitHub] phoenix pull request #205: PHOENIX-3223 Add `hadoop classpath` to PQS classp...

Github user asfgit closed the pull request at: https://github.com/apache/phoenix/pull/205 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450361#comment-15450361 ] Josh Elser commented on PHOENIX-3223: - Thanks [~sergey.soldatov]! Will commit shortly. I've tested

[jira] [Commented] (PHOENIX-3227) OFFSET is very slow at scale

[ https://issues.apache.org/jira/browse/PHOENIX-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450321#comment-15450321 ] Lars Hofhansl commented on PHOENIX-3227: Should I close this one [~giacomotaylor]? > OFFSET is

Phoenix Tuning Guide [First Draft]

All, I've uploaded a draft of the Phoenix Tuning Guide as an attachment to the following Jira: https://issues.apache.org/jira/browse/PHOENIX-3218 I welcome any feedback or comments. Thanks, Peter Peter Conrad Staff Technical Writer: Infrastructure | salesforce.com Office: (415) 471-5265

[jira] [Commented] (PHOENIX-2645) Wildcard characters do not match newline characters

[ https://issues.apache.org/jira/browse/PHOENIX-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450239#comment-15450239 ] Hudson commented on PHOENIX-2645: - FAILURE: Integrated in Jenkins build Phoenix-master #1375 (See

[jira] [Commented] (PHOENIX-3163) Split during global index creation may cause ERROR 201 error.

[ https://issues.apache.org/jira/browse/PHOENIX-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450220#comment-15450220 ] James Taylor commented on PHOENIX-3163: --- I think the split detection code on the client side is

[jira] [Commented] (PHOENIX-3227) OFFSET is very slow at scale

[ https://issues.apache.org/jira/browse/PHOENIX-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450202#comment-15450202 ] James Taylor commented on PHOENIX-3227: --- [~an...@apache.org] > OFFSET is very slow at scale >

[jira] [Commented] (PHOENIX-3227) OFFSET is very slow at scale

[ https://issues.apache.org/jira/browse/PHOENIX-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450197#comment-15450197 ] James Taylor commented on PHOENIX-3227: --- Yes, that's what I expected. FYI, we do push the OFFSET

[jira] [Updated] (PHOENIX-3224) Observations from large scale testing.

[ https://issues.apache.org/jira/browse/PHOENIX-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3224: --- Description: We have a >1000 node physical cluster at our disposal for a short time, before

[jira] [Created] (PHOENIX-3227) OFFSET is very slow at scale

Lars Hofhansl created PHOENIX-3227: -- Summary: OFFSET is very slow at scale Key: PHOENIX-3227 URL: https://issues.apache.org/jira/browse/PHOENIX-3227 Project: Phoenix Issue Type: Sub-task

[jira] [Created] (PHOENIX-3226) Phoenix should have an option to fail a query that would ship large amounts of data to the client.

Lars Hofhansl created PHOENIX-3226: -- Summary: Phoenix should have an option to fail a query that would ship large amounts of data to the client. Key: PHOENIX-3226 URL:

[jira] [Updated] (PHOENIX-3225) Distinct Queries are slower than expected at scale.

[ https://issues.apache.org/jira/browse/PHOENIX-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-3225: --- Summary: Distinct Queries are slower than expected at scale. (was: Distinct Queries are

[jira] [Created] (PHOENIX-3225) Distinct Queries are slower than expected

Lars Hofhansl created PHOENIX-3225: -- Summary: Distinct Queries are slower than expected Key: PHOENIX-3225 URL: https://issues.apache.org/jira/browse/PHOENIX-3225 Project: Phoenix Issue

[jira] [Commented] (PHOENIX-3224) Observations from large scale testing.

[ https://issues.apache.org/jira/browse/PHOENIX-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450118#comment-15450118 ] Lars Hofhansl commented on PHOENIX-3224: [~giacomotaylor], [~mujtabachohan], FYI. >

[jira] [Commented] (PHOENIX-3216) Kerberos ticket is not renewed when using Kerberos authentication with Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450106#comment-15450106 ] ASF GitHub Bot commented on PHOENIX-3216: - Github user dbahir closed the pull request at:

[jira] [Commented] (PHOENIX-3216) Kerberos ticket is not renewed when using Kerberos authentication with Phoenix JDBC driver

[ https://issues.apache.org/jira/browse/PHOENIX-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450107#comment-15450107 ] ASF GitHub Bot commented on PHOENIX-3216: - Github user dbahir commented on the issue:

[GitHub] phoenix issue #203: [PHOENIX-3216] Kerberos ticket is not renewed when using...

Github user dbahir commented on the issue: https://github.com/apache/phoenix/pull/203 Closing, this issue will be fixed by [#191](https://github.com/apache/phoenix/pull/191) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] phoenix pull request #203: [PHOENIX-3216] Kerberos ticket is not renewed whe...

Github user dbahir closed the pull request at: https://github.com/apache/phoenix/pull/203 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449996#comment-15449996 ] Sergey Soldatov commented on PHOENIX-3223: -- LGTM. [~elserj] nice work :) > Add hadoop

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449987#comment-15449987 ] Josh Elser commented on PHOENIX-3223: - [~sergey.soldatov], [~aliciashu], either of you have a chance

[jira] [Updated] (PHOENIX-3223) Add hadoop classpath to PQS classpath

[ https://issues.apache.org/jira/browse/PHOENIX-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated PHOENIX-3223: Reporter: Sergio Peleato (was: Josh Elser) > Add hadoop classpath to PQS classpath >

[jira] [Commented] (PHOENIX-3223) Add hadoop classpath to PQS classpath

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

[GitHub] phoenix pull request #205: PHOENIX-3223 Add `hadoop classpath` to PQS classp...

GitHub user joshelser opened a pull request: https://github.com/apache/phoenix/pull/205 PHOENIX-3223 Add `hadoop classpath` to PQS classpath when available You can merge this pull request into a Git repository by running: $ git pull https://github.com/joshelser/phoenix

[GitHub] phoenix pull request #:

Github user twdsilva commented on the pull request: https://github.com/apache/phoenix/commit/ede483cf29c86c1acebc12d995966a838e4eaffb#commitcomment-18834750 This closes #199 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Resolved] (PHOENIX-2645) Wildcard characters do not match newline characters

[ https://issues.apache.org/jira/browse/PHOENIX-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva resolved PHOENIX-2645. - Resolution: Fixed [~kliew] I have commited to 4.x and 4.8 branches, thanks for the

[jira] [Commented] (PHOENIX-3218) First draft of Phoenix Tuning Guide

[ https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449874#comment-15449874 ] James Taylor commented on PHOENIX-3218: --- You can start a new thread on the dev and user list

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449867#comment-15449867 ] James Taylor commented on PHOENIX-3116: --- Not sure, [~poornachandra]. Hard to know what the vendors

[jira] [Commented] (PHOENIX-3218) First draft of Phoenix Tuning Guide

[ https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449866#comment-15449866 ] Peter Conrad commented on PHOENIX-3218: --- What are the steps to get this reviewed and added to the

[jira] [Created] (PHOENIX-3223) Add hadoop classpath to PQS classpath

Josh Elser created PHOENIX-3223: --- Summary: Add hadoop classpath to PQS classpath Key: PHOENIX-3223 URL: https://issues.apache.org/jira/browse/PHOENIX-3223 Project: Phoenix Issue Type: Bug

Re: [DISCUSS] which 4.8 branches will be active?

I have to concur with Enis here; I wouldn't feel great about dropping 1.{0,1} support in 4.8 since it went out the door like that. Granted, I don't recall reading any official Phoenix compatibility guidelines as to what *will* be supported between versions, so, the ability to do it is there.

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449851#comment-15449851 ] Poorna Chandra commented on PHOENIX-3116: - [~jamestaylor] Do you think those two versions of

[jira] [Commented] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449785#comment-15449785 ] Hadoop QA commented on PHOENIX-3116: {color:red}-1 overall{color}. Here are the results of testing

[GitHub] phoenix pull request #:

Github user dbahir commented on the pull request: https://github.com/apache/phoenix/commit/b5be8d85bfd05aeb3ea17b1c734eda06d914f516#commitcomment-18834022 My bad regarding the synchronization, you are correct. Did you get to look at the comment regarding the user login ?

[jira] [Commented] (PHOENIX-3200) Error trying to remove Hash Cache

[ https://issues.apache.org/jira/browse/PHOENIX-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449729#comment-15449729 ] Maryann Xue commented on PHOENIX-3200: -- Hi [~nvommi], thank you for reporting the issue. Could you

[jira] [Commented] (PHOENIX-3222) Document namespace feature

[ https://issues.apache.org/jira/browse/PHOENIX-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15449651#comment-15449651 ] James Taylor commented on PHOENIX-3222: --- It'd be great to promote this feature a bit, but there

[jira] [Created] (PHOENIX-3222) Document namespace feature

James Taylor created PHOENIX-3222: - Summary: Document namespace feature Key: PHOENIX-3222 URL: https://issues.apache.org/jira/browse/PHOENIX-3222 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3116: -- Fix Version/s: 4.9.0 > Support incompatible HBase 1.1.5 and HBase 1.2.2 >

[jira] [Updated] (PHOENIX-3116) Support incompatible HBase 1.1.5 and HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3116: -- Summary: Support incompatible HBase 1.1.5 and HBase 1.2.2 (was: Support HBase 1.2.2) >

[jira] [Updated] (PHOENIX-3116) Support HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3116: -- Attachment: PHOENIX-3116_v2.patch Adjusting patch to remove @Override tags and use reflection

[jira] [Updated] (PHOENIX-3116) Support HBase 1.2.2

[ https://issues.apache.org/jira/browse/PHOENIX-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-3116: -- Summary: Support HBase 1.2.2 (was: Upgrade HBase dependency to 1.2.2) > Support HBase 1.2.2

[GitHub] phoenix pull request #:

Github user joshelser commented on the pull request: https://github.com/apache/phoenix/commit/b5be8d85bfd05aeb3ea17b1c734eda06d914f516#commitcomment-18831881 > UserGroupInformation.getCurrentUser() will not be thread safe. ``` @InterfaceAudience.Public

Phoeinix tracing server Issue

Hi Phoenix developers/users , We are trying to use the phoenix tracing server in our environment but we are facing issue while accessing the web application. We get HTTP ERROR 404 Problem accessing /webapp/. Reason: Not Found While accessing

[GitHub] phoenix pull request #:

Github user dbahir commented on the pull request: https://github.com/apache/phoenix/commit/b5be8d85bfd05aeb3ea17b1c734eda06d914f516#commitcomment-18831582 UserGroupInformation.getCurrentUser() will not be thread safe, uploaded a patch of how to fix it.

ApacheCon Seville CFP closes September 9th

It's traditional. We wait for the last minute to get our talk proposals in for conferences. Well, the last minute has arrived. The CFP for ApacheCon Seville closes on September 9th, which is less than 2 weeks away. It's time to get your talks in, so that we can make this the best ApacheCon yet.

[jira] [Commented] (PHOENIX-3220) DAYOFMONTH function not giving correct result for 24hr clock time format

[ https://issues.apache.org/jira/browse/PHOENIX-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448929#comment-15448929 ] Ankit Singhal commented on PHOENIX-3220: Yes, it's a bug, as during TO_DATE evaluation , date

[jira] [Updated] (PHOENIX-3221) "LOCAL" keyword is not adhered for "phoenix.query.dateFormatTimeZone"

[ https://issues.apache.org/jira/browse/PHOENIX-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3221: --- Attachment: PHOENIX-3221.patch > "LOCAL" keyword is not adhered for

[jira] [Updated] (PHOENIX-3221) "LOCAL" keyword is not adhered for "phoenix.query.dateFormatTimeZone"

[ https://issues.apache.org/jira/browse/PHOENIX-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-3221: --- Description: Currently, it is falling back to GMT. > "LOCAL" keyword is not adhered for

[jira] [Created] (PHOENIX-3221) "LOCAL" keyword is not adhered for "phoenix.query.dateFormatTimeZone"

Ankit Singhal created PHOENIX-3221: -- Summary: "LOCAL" keyword is not adhered for "phoenix.query.dateFormatTimeZone" Key: PHOENIX-3221 URL: https://issues.apache.org/jira/browse/PHOENIX-3221 Project:

[jira] [Commented] (PHOENIX-3214) Kafka Phoenix Consumer

[ https://issues.apache.org/jira/browse/PHOENIX-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448913#comment-15448913 ] Kalyan commented on PHOENIX-3214: - Providing a new feature to Phoenix. Directly ingest Kafka messages

[jira] [Commented] (PHOENIX-2890) Extend IndexTool to allow incremental index rebuilds

[ https://issues.apache.org/jira/browse/PHOENIX-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448769#comment-15448769 ] Ankit Singhal commented on PHOENIX-2890: Yes [~jamestaylor], it was off my plate for sometime

[jira] [Created] (PHOENIX-3220) DAYOFMONTH function not giving correct result for 24hr clock time format

Neeru Jaroliya created PHOENIX-3220: --- Summary: DAYOFMONTH function not giving correct result for 24hr clock time format Key: PHOENIX-3220 URL: https://issues.apache.org/jira/browse/PHOENIX-3220