[jira] [Created] (PHOENIX-2963) Exception with functional indexes over UDFs

Mac created PHOENIX-2963: Summary: Exception with functional indexes over UDFs Key: PHOENIX-2963 URL: https://issues.apache.org/jira/browse/PHOENIX-2963 Project: Phoenix Issue Type: Bug Affects

[jira] [Updated] (PHOENIX-2209) Building Local Index Asynchronously via IndexTool fails to populate index table

[ https://issues.apache.org/jira/browse/PHOENIX-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla updated PHOENIX-2209: - Attachment: PHOENIX-2209.patch [~jamestaylor] Here is the patch get

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313377#comment-15313377 ] Sergey Soldatov commented on PHOENIX-2934: -- [~jamestaylor] sure. I would suggest instead of

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313283#comment-15313283 ] James Taylor commented on PHOENIX-2934: --- Maybe [~sergey.soldatov], you can help Alicia again? >

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313260#comment-15313260 ] Lars Hofhansl commented on PHOENIX-258: --- There are some more tests failing, all test fixes I think

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313163#comment-15313163 ] Hudson commented on PHOENIX-258: SUCCESS: Integrated in Phoenix-master #1242 (See

[jira] [Comment Edited] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313067#comment-15313067 ] Alicia Ying Shu edited comment on PHOENIX-2934 at 6/2/16 9:14 PM: --

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15313067#comment-15313067 ] Alicia Ying Shu commented on PHOENIX-2934: -- I added the check for desiredMaxLength > b.length

[jira] [Comment Edited] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312598#comment-15312598 ] Alicia Ying Shu edited comment on PHOENIX-2886 at 6/2/16 8:39 PM: --

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312995#comment-15312995 ] Josh Elser commented on PHOENIX-258: bq. I might have inadvertently created a 4.0 and 4.x-HBase-1.x

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312985#comment-15312985 ] Lars Hofhansl commented on PHOENIX-258: --- Done. I might have inadvertently created a 4.0 and

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312975#comment-15312975 ] Lars Hofhansl commented on PHOENIX-258: --- There are some test failures. Fix soon. > Use skip scan

[jira] [Commented] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

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

[jira] [Commented] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312765#comment-15312765 ] Josh Elser commented on PHOENIX-2940: - bq. I think the proposal above will solve your issues, Nick

[jira] [Resolved] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved PHOENIX-258. --- Resolution: Fixed Pushed to 4.x-HBase-0.98, 4.x-HBase-1.0, 4.x-HBase-1.1, and master. (I do

[jira] [Updated] (PHOENIX-258) Use skip scan when SELECT DISTINCT on leading row key column(s)

[ https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-258: -- Attachment: 258-v17.txt -v17 is what I am going to commit * fixes some comments * removes the

GSoC Project status

Hi Alexander As per our last discussion I know you were able to install Phoneix on Hbase and you were able to get basic testcases running. Have you started with the code walk through? ? DistinctValueWithCountServerAggregator and DistinctValueWithCountAggregateFunction can help you in

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312650#comment-15312650 ] James Taylor commented on PHOENIX-2934: --- Looks like a lot of copy/paste from the super class. Why

[jira] [Commented] (PHOENIX-2949) Fix estimated region size when checking for serial query

[ https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312638#comment-15312638 ] James Taylor commented on PHOENIX-2949: --- Thanks for the fix, [~an...@apache.org]. I think this

Re: Please share the status of GSoC project

A NoNode error is not a failure condition. HBase regularly makes decisions on whether or not nodes actually exist in HBase... Josh Elser wrote: Please keep all conversations on the mailing list. Pranavan Theivendiram wrote: Hi Josh. I had hadoop-2.5.1 jars. I replaced the old jars with new

Re: Please share the status of GSoC project

Please keep all conversations on the mailing list. Pranavan Theivendiram wrote: Hi Josh. I had hadoop-2.5.1 jars. I replaced the old jars with new hadoop 2.6.4 jars. (Earlier I got some class not found errors. I fixed it by replacing 2.5.1 with 2.6.4) I am thinking like, this is a problem

Re: Please share the status of GSoC project

Did you download tarballs from Apache? Some vendor? If you downloaded the Apache HBase 1.2.1 binary tarball, you will have hadoop-2.5.1 jars on the HBase classpath. It would be good to make sure you have consistent versions of Hadoop/HDFS on the HBase classpath. Pranavan Theivendiram wrote:

[jira] [Commented] (PHOENIX-2886) Union ALL with Char column not present in the table in Query 1 but in Query 2 throw exception

[ https://issues.apache.org/jira/browse/PHOENIX-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312598#comment-15312598 ] Alicia Ying Shu commented on PHOENIX-2886: -- I uploaded the patch for coerce expression issue to

[jira] [Commented] (PHOENIX-2940) Remove STATS RPCs from rowlock

[ https://issues.apache.org/jira/browse/PHOENIX-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312558#comment-15312558 ] Nick Dimiduk commented on PHOENIX-2940: --- bq. we don't use stats on the server-side, only the

Re: Please share the status of GSoC project

Hi Josh, Please find the answers inline. On 2 June 2016 at 21:22, Josh Elser wrote: > How did you install HDFS and HBase and what versions of each did you use? > It looks like you might somehow have incompatible libraries. > Hadoop - 2.6.4 Zookeeper - 3.4.8 Hbase - 1.2.1

[jira] [Updated] (PHOENIX-2949) Fix estimated region size when checking for serial query

[ https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2949: -- Fix Version/s: 4.8.0 > Fix estimated region size when checking for serial query >

Re: Please share the status of GSoC project

How did you install HDFS and HBase and what versions of each did you use? It looks like you might somehow have incompatible libraries. I also haven't seen any message from you on the hbase lists (user or dev). Make sure you subscribe to the user@ list before posting. Pranavan Theivendiram

[jira] [Commented] (PHOENIX-2926) Skip loading data for table having local indexes when there is split during bulkload job

[ https://issues.apache.org/jira/browse/PHOENIX-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312488#comment-15312488 ] James Taylor commented on PHOENIX-2926: --- +1 > Skip loading data for table having local indexes

[jira] [Commented] (PHOENIX-2209) Building Local Index Asynchronously via IndexTool fails to populate index table

[ https://issues.apache.org/jira/browse/PHOENIX-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312481#comment-15312481 ] James Taylor commented on PHOENIX-2209: --- Ok, thanks - let me know when the patch is available,

[jira] [Commented] (PHOENIX-2930) Cannot resolve columns aliased to its own name

[ https://issues.apache.org/jira/browse/PHOENIX-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312463#comment-15312463 ] James Taylor commented on PHOENIX-2930: --- [~maryannxue] - would it be possible for you to take a

[jira] [Updated] (PHOENIX-2930) Cannot resolve columns aliased to its own name

[ https://issues.apache.org/jira/browse/PHOENIX-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-2930: -- Fix Version/s: 4.8.0 > Cannot resolve columns aliased to its own name >

Re: Please share the status of GSoC project

Hi Rajesh, This is the update what I have done in first week. I worked on following things. 1. I have set up Pheonix in standalone mode as well as in cluster mode. (In cluster mode, there is a failure. Standalone mode is working perfect. Checked the tracing logs. ) 2. Set up the code

Please share the status of GSoC project

Hi Pranavan, Hope you are doing well? How's the GSoC project work going on? Can you please share the status of it and and also let's know if any help needed. Happy to help you. Thanks, Rajeshbabu.

[jira] [Updated] (PHOENIX-2953) some value is returned null when selecting query if phoenix table has a big length column

[ https://issues.apache.org/jira/browse/PHOENIX-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaeMyung Kim updated PHOENIX-2953: -- Description: I created table create table PHOENIX_TEST ( ID char(32) not null

[jira] [Commented] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311860#comment-15311860 ] Alicia Ying Shu commented on PHOENIX-2934: -- Uploaded the patch. It fixes the issue of PChar not

[jira] [Updated] (PHOENIX-2934) Checking a coerce expression at top level should not be necessary for Union All query

[ https://issues.apache.org/jira/browse/PHOENIX-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alicia Ying Shu updated PHOENIX-2934: - Attachment: PHOENIX-2934.patch > Checking a coerce expression at top level should not

[jira] [Commented] (PHOENIX-2949) Fix estimated region size when checking for serial query

[ https://issues.apache.org/jira/browse/PHOENIX-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311835#comment-15311835 ] Ankit Singhal commented on PHOENIX-2949: [~samarthjain], can you take a quick look.. as above

[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=15311829#comment-15311829 ] Hadoop QA commented on PHOENIX-2535: {color:red}-1 overall{color}. Here are the results of testing