Re: [GSoC 2015][PROPOSAL][Providing a tool for visualizing Phoenix tracing information (PHOENIX-1118)]

Hi James, Regarding the weak link issue you pointed out on my proposal, I'm planning to use charts which doesn't redraw the graphs at a change of data set (updates). It draws the graph in incremental steps. Therefore a weak link between the front end and node in the cluster doesn't result a poorly

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:50 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:48 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:23 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:08 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:08 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:07 AM:

[jira] [Comment Edited] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu edited comment on PHOENIX-1580 at 4/1/15 6:02 AM:

[jira] [Commented] (PHOENIX-1580) Support UNION ALL

[ https://issues.apache.org/jira/browse/PHOENIX-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390020#comment-14390020 ] Alicia Ying Shu commented on PHOENIX-1580: -- [~jamestaylor]The temp schema is fo

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389922#comment-14389922 ] Serhiy Bilousov commented on PHOENIX-1748: -- Client operates on column metadata

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389917#comment-14389917 ] James Taylor commented on PHOENIX-1748: --- The underlying value is an 8 byte long th

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389914#comment-14389914 ] Serhiy Bilousov commented on PHOENIX-1748: -- Ok. Let me ask in different way.

[jira] [Comment Edited] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389914#comment-14389914 ] Serhiy Bilousov edited comment on PHOENIX-1748 at 4/1/15 2:59 AM:

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389912#comment-14389912 ] James Taylor commented on PHOENIX-1748: --- We use Java. There are ways to configure

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389909#comment-14389909 ] Serhiy Bilousov commented on PHOENIX-1748: -- Well, I tried with both client PHOE

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389906#comment-14389906 ] James Taylor commented on PHOENIX-1748: --- [~sergey.b] - your SQL client is the prob

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389902#comment-14389902 ] Serhiy Bilousov commented on PHOENIX-1748: -- Thank you [~dhacker1341] for checki

[jira] [Commented] (PHOENIX-1705) implement ARRAY_APPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389897#comment-14389897 ] James Taylor commented on PHOENIX-1705: --- Also, in evaluate, use this version of PD

[jira] [Commented] (PHOENIX-1705) implement ARRAY_APPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389890#comment-14389890 ] James Taylor commented on PHOENIX-1705: --- Thanks for the revisions, [~Dumindux]. Be

[jira] [Commented] (PHOENIX-1663) Implement missing string built-in functions

[ https://issues.apache.org/jira/browse/PHOENIX-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389881#comment-14389881 ] Naveen Madhire commented on PHOENIX-1663: - [~jamestaylor] I am done with INSTR f

[jira] [Commented] (PHOENIX-1712) Implementing INSTR function

[ https://issues.apache.org/jira/browse/PHOENIX-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389865#comment-14389865 ] ASF GitHub Bot commented on PHOENIX-1712: - Github user naveenmadhire commented o

[GitHub] phoenix pull request: PHOENIX-1712 Implementing INSTR Function

Github user naveenmadhire commented on the pull request: https://github.com/apache/phoenix/pull/61#issuecomment-88311224 @gabrielreid This is the new pull request which I had to create for the 1712 changes as I messed it while doing a rebase of the pull request. --- If your project i

[jira] [Commented] (PHOENIX-1712) Implementing INSTR function

[ https://issues.apache.org/jira/browse/PHOENIX-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389862#comment-14389862 ] ASF GitHub Bot commented on PHOENIX-1712: - Github user naveenmadhire commented o

[GitHub] phoenix pull request: PHOENIX-1712 Adding INSTR Function

Github user naveenmadhire commented on the pull request: https://github.com/apache/phoenix/pull/47#issuecomment-88311044 @gabrielreid I tried to do this, but messed it up and created a new Pull request 61. I am closing this request. --- If your project is set up for it, you can reply

[jira] [Commented] (PHOENIX-1712) Implementing INSTR function

[ https://issues.apache.org/jira/browse/PHOENIX-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389863#comment-14389863 ] ASF GitHub Bot commented on PHOENIX-1712: - Github user naveenmadhire closed the

[GitHub] phoenix pull request: PHOENIX-1712 Adding INSTR Function

Github user naveenmadhire closed the pull request at: https://github.com/apache/phoenix/pull/47 --- 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

[jira] [Commented] (PHOENIX-1712) Implementing INSTR function

[ https://issues.apache.org/jira/browse/PHOENIX-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389859#comment-14389859 ] ASF GitHub Bot commented on PHOENIX-1712: - GitHub user naveenmadhire opened a pu

[GitHub] phoenix pull request: PHOENIX-1712 Implementing INSTR Function

GitHub user naveenmadhire opened a pull request: https://github.com/apache/phoenix/pull/61 PHOENIX-1712 Implementing INSTR Function Changes related to Phoenix-1712 INSTR Built in function You can merge this pull request into a Git repository by running: $ git pull https://g

[jira] [Updated] (PHOENIX-1705) implement ARRAY_APPEND built in function

[ https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumindu Buddhika updated PHOENIX-1705: -- Attachment: PHOENIX-1705_implement_ARRAY_APPEND_built_in_function10.patch Hm, actually

[jira] [Commented] (PHOENIX-1681) Use the new Region Interface

[ https://issues.apache.org/jira/browse/PHOENIX-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389812#comment-14389812 ] Andrew Purtell commented on PHOENIX-1681: - Now that HBASE-12972 is committed we

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389797#comment-14389797 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user dacort commented on the p

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user dacort commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88298339 @jmahonin Thanks for this PR! You're good to go with respect to copyrights. Thanks for putting those in the appropriate place. --- If your project is set up for

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389673#comment-14389673 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user jmahonin commented on the

[VOTE] Release of Apache Phoenix 3.3.1 RC0

Hello everyone, This is a call for a vote on Apache Phoenix 3.3.1 RC0. This is a bug fix/patch release of Phoenix 3.3, compatible with the 0.94 branch of Apache HBase. The release includes both a source-only release and a convenience binary release. For a complete list of changes, see: https://ra

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user jmahonin commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88285575 Can confirm the memory settings needed adjustment on 7u76 on Linux. Special thanks to @robdaemon who had an excellent library to work with, and a pre-emptive tha

[VOTE] Release of Apache Phoenix 4.3.1 RC0

Hello everyone, This is a call for a vote on Apache Phoenix 4.3.1 RC0. This is a bug fix/patch release of Phoenix 4.3, compatible with the 0.98 branch of Apache HBase. The release includes both a source-only release and a convenience binary release. For a complete list of changes, see: https://ra

[jira] [Commented] (PHOENIX-1797) Add more tests for date literals

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

[jira] [Commented] (PHOENIX-1796) TO_DATE not functioning as stated in the documentation

[ https://issues.apache.org/jira/browse/PHOENIX-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389523#comment-14389523 ] James Taylor commented on PHOENIX-1796: --- I've seen a similar issue reported, but i

Re: delete unused 4.0.1 and type-system branches

+1 On Tue, Mar 31, 2015 at 2:27 PM, James Taylor wrote: > We're got a couple of unused branches that I'd like to delete: 4.0.1 > which was never released and type-system which is not in use. Unless I > hear otherwise, I'll plan to delete these branches by the end of the > week. > Thanks, > James

[jira] [Commented] (PHOENIX-1796) TO_DATE not functioning as stated in the documentation

[ https://issues.apache.org/jira/browse/PHOENIX-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389515#comment-14389515 ] Ivan Weiss commented on PHOENIX-1796: - Our test env got taken down. I'll recreate th

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389506#comment-14389506 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user dacort commented on the p

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user dacort commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88267935 Consider me poked! Will take a look at this and follow up tomorrow by the latest. --- If your project is set up for it, you can reply to this email and have your reply ap

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389504#comment-14389504 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user robdaemon commented on th

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user robdaemon commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88267669 So happy to see this go in. I'll push on my former colleagues at Simply Measured about the copyrights!! --- If your project is set up for it, you can reply to this ema

delete unused 4.0.1 and type-system branches

We're got a couple of unused branches that I'd like to delete: 4.0.1 which was never released and type-system which is not in use. Unless I hear otherwise, I'll plan to delete these branches by the end of the week. Thanks, James

[jira] [Commented] (PHOENIX-1781) Add Now()

[ https://issues.apache.org/jira/browse/PHOENIX-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389432#comment-14389432 ] James Taylor commented on PHOENIX-1781: --- +1. Thanks for the contribution, [~ayings

[jira] [Resolved] (PHOENIX-1797) Add more tests for date literals

[ https://issues.apache.org/jira/browse/PHOENIX-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor resolved PHOENIX-1797. --- Resolution: Fixed Fix Version/s: 4.4.0 > Add more tests for date literals > -

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389417#comment-14389417 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user apurtell commented on the

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user apurtell commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88248990 I'm not a Spark expert @JamesRTaylor . I skimmed the latest. Allowing builds with JDK 1.7 would have been the big change I'd have recommended, and it's already been don

[jira] [Updated] (PHOENIX-1797) Add more tests for date literals

[ https://issues.apache.org/jira/browse/PHOENIX-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-1797: -- Attachment: PHOENIX-1797.patch > Add more tests for date literals > --

[jira] [Created] (PHOENIX-1797) Add more tests for date literals

James Taylor created PHOENIX-1797: - Summary: Add more tests for date literals Key: PHOENIX-1797 URL: https://issues.apache.org/jira/browse/PHOENIX-1797 Project: Phoenix Issue Type: Bug

Re: dropping branch 4.x-HBase-1.x tomorrow

I have deleted the branch named "4.x-HBase-1.x" as well as the jenkins jobs. I have a local copy of the branch in case we missed something. I have also updated the jira release versions to be always major.minor.patch format, so 4.4 -> 4.4.0, 4.3 -> 4.3.0, etc. The jira query for whether we have a

[jira] [Commented] (PHOENIX-1795) Set handlerCount, numQueues and maxQueueLength of index and metadata queues correctly

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

[GitHub] phoenix pull request: Additional date query tests.

Github user JamesRTaylor commented on the pull request: https://github.com/apache/phoenix/pull/60#issuecomment-88239723 Thanks for the contribution, @michfr . LGTM. I'll get this committed to 4.x and master soon. --- If your project is set up for it, you can reply to this email and h

[jira] [Commented] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389380#comment-14389380 ] Dave Hacker commented on PHOENIX-1748: -- Things are behaving correctly. I wrote a t

[jira] [Updated] (PHOENIX-1748) Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILLISECOND on TIMESTAMP should not truncate value to the DATE only.

[ https://issues.apache.org/jira/browse/PHOENIX-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Hacker updated PHOENIX-1748: - Attachment: PHOENIX-1748.patch > Appling TRUNC|ROUND|FLOOR|CEIL with DAY|HOUR|MINUTE|SECOND|MILL

[jira] [Updated] (PHOENIX-896) Improve cmdline parsing of psql (PhoenixRuntime)

[ https://issues.apache.org/jira/browse/PHOENIX-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated PHOENIX-896: -- Fix Version/s: 4.1.0 3.1.0 > Improve cmdline parsing of psql (PhoenixRuntime

[jira] [Updated] (PHOENIX-1416) Given a schema name, DatabaseMetadata.getTables and getColumns calls erroneously match tables without schema

[ https://issues.apache.org/jira/browse/PHOENIX-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated PHOENIX-1416: --- Fix Version/s: (was: 3.3.) 3.3.0 > Given a schema name, DatabaseMetad

[jira] [Resolved] (PHOENIX-1457) Use high priority queue for metadata endpoint calls

[ https://issues.apache.org/jira/browse/PHOENIX-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva resolved PHOENIX-1457. - Resolution: Fixed > Use high priority queue for metadata endpoint calls > --

Re: dropping branch 4.x-HBase-1.x tomorrow

Let me do the work. Was waiting for a couple of things on our end. Enis On Mon, Mar 30, 2015 at 4:51 PM, James Taylor wrote: > As discussed already, we plan to drop the 4.x-HBase-1.x branch as it's > been determined not to be needed at the present time. Either Enis or I > will drop this branch

Re: Bound parameters in create table statements

Hi Gabriel, Yes, we do this in the Phoenix test harness for parameterizing split points. See o.a.p.q.BaseTest#createTestTable(String, String, byte[][], Long, boolean). I ran into this while porting QueryIT to run vs. the query server. -n On Tue, Mar 31, 2015 at 11:58 AM, Gabriel Reid wrote: >

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389270#comment-14389270 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user jmahonin commented on the

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user jmahonin commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88226194 JDK 1.7 and the ProductRDDFunctions package location have been fixed up. I tried to make some headway on getting the unit tests to run in the IDE. If you're seei

[jira] [Resolved] (PHOENIX-1771) Link to the SQuirrel on "Phoenix in 15 minutes" page is incorrect.

[ https://issues.apache.org/jira/browse/PHOENIX-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Reid resolved PHOENIX-1771. --- Resolution: Fixed Assignee: Gabriel Reid Fixed link as suggested, thanks for reporting

[jira] [Updated] (PHOENIX-1795) Set handlerCount, numQueues and maxQueueLength of index and metadata queues correctly

[ https://issues.apache.org/jira/browse/PHOENIX-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas D'Silva updated PHOENIX-1795: Attachment: PHOENIX-1795-4.3.1-v2.patch Fix QueryDatabaseMetaDataIT.testCreateViewOnExist

[jira] [Commented] (PHOENIX-1722) Speedup CONVERT_TZ function

[ https://issues.apache.org/jira/browse/PHOENIX-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389251#comment-14389251 ] Gabriel Reid commented on PHOENIX-1722: --- [~samarthjain] ok, I just wanted to doubl

[jira] [Commented] (PHOENIX-1712) Implementing INSTR function

[ https://issues.apache.org/jira/browse/PHOENIX-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389245#comment-14389245 ] ASF GitHub Bot commented on PHOENIX-1712: - Github user gabrielreid commented on

[GitHub] phoenix pull request: PHOENIX-1712 Adding INSTR Function

Github user gabrielreid commented on the pull request: https://github.com/apache/phoenix/pull/47#issuecomment-88218650 Looks good, and I think that the test cases cover what needs to be covered. Could you rebase the patch on the master branch, and squash the commits into a si

Re: Bound parameters in create table statements

Could you explain how you're using prepared statements for DDL statements? Are you parameterizing parts of the DDL statements with question marks to be filled in by the PreparedStatement parameters? On Tue, Mar 31, 2015 at 3:48 AM Nick Dimiduk wrote: > Working on PHOENIX-971, I'm wondering what

[jira] [Commented] (PHOENIX-1781) Add Now()

[ https://issues.apache.org/jira/browse/PHOENIX-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389189#comment-14389189 ] Alicia Ying Shu commented on PHOENIX-1781: -- [~jamestaylor] Modified the test an

[jira] [Updated] (PHOENIX-1781) Add Now()

[ https://issues.apache.org/jira/browse/PHOENIX-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu updated PHOENIX-1781: - Attachment: Phoenix-1781-v1.patch > Add Now() > - > > Key: PHOEN

[jira] [Commented] (PHOENIX-1796) TO_DATE not functioning as stated in the documentation

[ https://issues.apache.org/jira/browse/PHOENIX-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389167#comment-14389167 ] Gabriel Reid commented on PHOENIX-1796: --- [~ivanweiss] could you provide a test cas

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

[ https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388970#comment-14388970 ] Mujtaba Chohan commented on PHOENIX-1118: - [~nishani] One easy way would be to a

[jira] [Created] (PHOENIX-1796) TO_DATE not functioning as stated in the documentation

Ivan Weiss created PHOENIX-1796: --- Summary: TO_DATE not functioning as stated in the documentation Key: PHOENIX-1796 URL: https://issues.apache.org/jira/browse/PHOENIX-1796 Project: Phoenix Issu

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388893#comment-14388893 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user jmahonin commented on the

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user jmahonin commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88179901 @mravi Great. I can get 1 and 2 taken care of today. Are new commits on this PR fine, or would you prefer a new PR with a rebased commit? --- If your project i

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1432#comment-1432 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user mravi commented on the pu

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user mravi commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88178852 @jmahonin I can join forces with you on the Good to haves --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388868#comment-14388868 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user jmahonin commented on the

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user jmahonin commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88176830 Thanks for the feedback @mravi , point comments below: 1: Right, I'll try get that sorted out. The original phoenix-spark library would not work with 1.7 for som

[jira] [Commented] (PHOENIX-1071) Provide integration for exposing Phoenix tables as Spark RDDs

[ https://issues.apache.org/jira/browse/PHOENIX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388788#comment-14388788 ] ASF GitHub Bot commented on PHOENIX-1071: - Github user mravi commented on the pu

[GitHub] phoenix pull request: PHOENIX-1071 Add phoenix-spark for Spark int...

Github user mravi commented on the pull request: https://github.com/apache/phoenix/pull/59#issuecomment-88157968 Nice work @jmahonin . Couple of minor changes 1. JDK version in the pom.xml is 1.8. You would need to downgrade to 1.7 2. For the ProductRDDFunctions.scala fi

[jira] [Commented] (PHOENIX-1792) Add Week() and Hour() built-ins

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

[jira] [Commented] (PHOENIX-1792) Add Week() and Hour() built-ins

[ https://issues.apache.org/jira/browse/PHOENIX-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388300#comment-14388300 ] Rajeshbabu Chintaguntla commented on PHOENIX-1792: -- [~ayingshu] There i

[jira] [Commented] (PHOENIX-1792) Add Week() and Hour() built-ins

[ https://issues.apache.org/jira/browse/PHOENIX-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388261#comment-14388261 ] Rajeshbabu Chintaguntla commented on PHOENIX-1792: -- Pushed to 4.x and m

[jira] [Commented] (PHOENIX-1781) Add Now()

[ https://issues.apache.org/jira/browse/PHOENIX-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388179#comment-14388179 ] James Taylor commented on PHOENIX-1781: --- You're right, [~ayingshu] - I forgot that