Re: Multiple rows with same key

Also, quick question, is your table salted, and have you done anything that might have altered the salt buckets? On Wed, Dec 18, 2019 at 7:50 AM la...@apache.org wrote: > You mean you see multiple rows with the same primary key? I have not see > this - or heard about this before. > > Could you

Re: [VOTE] Accept Tephra and Omid podlings as Phoenix sub-projects

+1! On Wed, Oct 30, 2019 at 8:27 AM Josh Elser wrote: > Hi, > > As was previously discussed[1][2], there is a motion to "adopt" the > Tephra and Omid podlings as sub-projects to Apache Phoenix. A > sub-project is a distinct software project from some top-level project > (TLP) but operates under

Re: [DISCUSS] Board report due 2019/08/14

A couple things that might be noteworthy: - Thanks to Lars, we now have a fully passing integration test: https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/ (since June IIRC) - Interesting discussion titled "is Apache phoenix reliable enough?" on the user list, where people shared their

Re: [VOTE] Release of Apache Phoenix 4.14.3 RC1

, 2019, 6:30 PM Geoffrey Jacoby wrote: > > > I agree with William that there's no need to block 4.14.3's 1.3 and > > 1.4-based releases on HBase 1.5. Soon-but-later, when HBase 1.5 lands I > > think we should do a followup 4.14.3 (or .4, if other critical JIRAs are &g

Re: [VOTE] Release of Apache Phoenix 4.14.3 RC1

If HBase does not patch 1.3 or 1.4 for the Jackson CVE, the recommendation for concerned users would be to use 1.5. I think that sounds like we would want to get a 1.5 branch for 4.14, unless we think 4.15 is almost ready? Either way, I am not sure if this would need to block 4.14.3, since it

[jira] [Updated] (PHOENIX-5275) Remove accidental imports from curator-client-2.12.0

[ https://issues.apache.org/jira/browse/PHOENIX-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5275: -- Attachment: PHOENIX-5275.4.14-HBase-1.3.v1.patch > Remove accidental imports from cura

[jira] [Created] (PHOENIX-5408) Typo in ConnectionQueryServicesImpl Warning Logging

William Shen created PHOENIX-5408: - Summary: Typo in ConnectionQueryServicesImpl Warning Logging Key: PHOENIX-5408 URL: https://issues.apache.org/jira/browse/PHOENIX-5408 Project: Phoenix

[jira] [Updated] (PHOENIX-5275) Remove accidental imports from curator-client-2.12.0

[ https://issues.apache.org/jira/browse/PHOENIX-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5275: -- Attachment: PHOENIX-5275.4.x-HBase-1.3.v1.patch > Remove accidental imports from cura

Re: A successful jenkins test run, at last

Awesome news. Thanks Lars! Not sure if I'm looking at the wrong place, but I don't think I found a green build on jenkins yet. Is this change local only for now? https://builds.apache.org/job/PreCommit-PHOENIX-Build/ On Mon, Jun 10, 2019 at 8:54 AM la...@apache.org wrote: > I finally managed to

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

ease happens > much > > later. We’ve always tried to get the doc changes pushed out before the > > release is cut. > > > > On Mon, Jun 3, 2019 at 9:30 AM William Shen > > wrote: > > > > > Thomas, that makes sense now. thanks for explaining. didn

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

Thomas, that makes sense now. thanks for explaining. didnt catch that the first time. would it make sense to you guys that we publish the website from master, or should we publish from say the latest of 4.x? On Mon, Jun 3, 2019 at 9:11 AM Thomas D'Silva wrote: > William, I was referring to y

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

from SVN to Git and then enable > git-pubsub. > > No concerns in doing this from me. Even better if you'd like to drive > it, William ;) > > On Fri, May 31, 2019 at 2:24 PM William Shen > wrote: > > > > Thomas, > > > > Which release line do we currently base our

[jira] [Updated] (PHOENIX-5275) Remove accidental imports from curator-client-2.12.0

[ https://issues.apache.org/jira/browse/PHOENIX-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5275: -- Attachment: PHOENIX-5275.master.v2.patch > Remove accidental imports from curator-cli

Re: [DISCUSS] Maintaining the Site in Git Instead of SVN

> > > > On Thu, May 30, 2019 at 4:38 PM William Shen > > > wrote: > > > > > Hi all, > > > > > > Currently, the Phoenix site is maintained in and built from SVN > > > <https://svn.apache.org/repos/asf/phoenix/site>. Not sure what

[DISCUSS] Maintaining the Site in Git Instead of SVN

Hi all, Currently, the Phoenix site is maintained in and built from SVN . Not sure what level of work it would require, but does it make sense to move the source from svn to git, so contribution to the website can follow the same JIRA/git workflow as

[jira] [Assigned] (PHOENIX-5306) Misleading statement in document

[ https://issues.apache.org/jira/browse/PHOENIX-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen reassigned PHOENIX-5306: - Assignee: William Shen Attachment: PHOENIX-5306.patch That makes sense to me

Re: PHOENIX-4863: Setup Travis-CI & CodeCoverage

+1 It would be awesome to be able to do this. Any concerns if we choose to run long IT as part of this setup? On Tue, May 28, 2019 at 1:00 PM Pedro Boado wrote: > What IT would you suggest to run? Testsuite (including long IT) takes ~2h. > > On Tue, 28 May 2019, 20:40 Thomas D'Silva, .invalid>

Re: The patch command could not apply the patch

.x-HBase-1.4 4.14-HBase-1.4 > master" > > Its trying to apply the patch again the master branch (by default) and > failing. I will white list the CDH branches. > > On Fri, May 24, 2019 at 11:48 AM William Shen > wrote: > > > Just saw this again at > >

Re: The patch command could not apply the patch

Just saw this again at https://issues.apache.org/jira/browse/PHOENIX-5295?focusedCommentId=16847823=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16847823 Is this a known issue? On Mon, May 20, 2019 at 4:18 PM William Shen wrote: > Hi all, > >

The patch command could not apply the patch

Hi all, On https://issues.apache.org/jira/browse/PHOENIX-5286, I encountered the Hadoop QA feedback of: -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2587//console Not totally sure what I am doing wrong here. I had

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC1

+1 Thanks for driving this Thomas. On Mon, May 20, 2019 at 7:17 AM cheng...@apache.org wrote: > +1, verified in my Environment. > > > > > > > > > At 2019-05-20 09:16:37, "Jaanai Zhang" wrote: > >+1 > > > > > > Jaanai Zhang > > Best regards! > > > > >

[jira] [Assigned] (PHOENIX-5286) IndexScrutinyToolIT Ignored in 4.x-CDH

[ https://issues.apache.org/jira/browse/PHOENIX-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen reassigned PHOENIX-5286: - Assignee: William Shen > IndexScrutinyToolIT Ignored in 4.x-

[jira] [Created] (PHOENIX-5286) IndexScrutinyToolIT Ignored in 4.x-CDH

William Shen created PHOENIX-5286: - Summary: IndexScrutinyToolIT Ignored in 4.x-CDH Key: PHOENIX-5286 URL: https://issues.apache.org/jira/browse/PHOENIX-5286 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-4373) Local index variable length key can have trailing nulls while upserting

[ https://issues.apache.org/jira/browse/PHOENIX-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-4373: -- Fix Version/s: 4.13.2-cdh > Local index variable length key can have trailing nulls wh

[jira] [Resolved] (PHOENIX-4754) Fix flapping of DerivedTableIT after PHOENIX-4728

[ https://issues.apache.org/jira/browse/PHOENIX-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen resolved PHOENIX-4754. --- Resolution: Won't Fix Closing as Won't Fix, since 4.x-HBase1.1 is now EOL per http://mail

[jira] [Closed] (PHOENIX-3848) Fix MutableIndexFailureIT for 1.1 and 0.98 branches

[ https://issues.apache.org/jira/browse/PHOENIX-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen closed PHOENIX-3848. - > Fix MutableIndexFailureIT for 1.1 and 0.98 branc

[jira] [Resolved] (PHOENIX-3848) Fix MutableIndexFailureIT for 1.1 and 0.98 branches

[ https://issues.apache.org/jira/browse/PHOENIX-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen resolved PHOENIX-3848. --- Resolution: Won't Fix Closing as Won't Fix, since 0.98 and 1.1 are now EOL per http

[jira] [Resolved] (PHOENIX-3864) PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98

[ https://issues.apache.org/jira/browse/PHOENIX-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen resolved PHOENIX-3864. --- Resolution: Won't Fix Closing as Won't Fix, since 0.98 is now EOL per http://mail

[jira] [Closed] (PHOENIX-4754) Fix flapping of DerivedTableIT after PHOENIX-4728

[ https://issues.apache.org/jira/browse/PHOENIX-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen closed PHOENIX-4754. - > Fix flapping of DerivedTableIT after PHOENIX-4

[jira] [Closed] (PHOENIX-3864) PhoenixConsumerIT is timing out frequently in 4.x-HBase-0.98

[ https://issues.apache.org/jira/browse/PHOENIX-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen closed PHOENIX-3864. - > PhoenixConsumerIT is timing out frequently in 4.x-HBase-0

[jira] [Resolved] (PHOENIX-3450) Fix hanging tests in IndexExtendedIT for 4.x-HBase-0.98

[ https://issues.apache.org/jira/browse/PHOENIX-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen resolved PHOENIX-3450. --- Resolution: Won't Fix Closing as Won't Fix, since 0.98 is now EOL per http://mail

[jira] [Closed] (PHOENIX-3450) Fix hanging tests in IndexExtendedIT for 4.x-HBase-0.98

[ https://issues.apache.org/jira/browse/PHOENIX-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen closed PHOENIX-3450. - > Fix hanging tests in IndexExtendedIT for 4.x-HBase-0

[jira] [Resolved] (PHOENIX-4117) Add hadoop qa files for 4.x-HBase-0.98 branch

[ https://issues.apache.org/jira/browse/PHOENIX-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen resolved PHOENIX-4117. --- Resolution: Won't Do Closing as Won't Do, since 0.98 is now EOL per http://mail

[jira] [Closed] (PHOENIX-4117) Add hadoop qa files for 4.x-HBase-0.98 branch

[ https://issues.apache.org/jira/browse/PHOENIX-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen closed PHOENIX-4117. - > Add hadoop qa files for 4.x-HBase-0.98 bra

[jira] [Updated] (PHOENIX-4994) Update New Data in HBase to Phoenix Secondary Index Table in Real Time

[ https://issues.apache.org/jira/browse/PHOENIX-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-4994: -- Description: 我们现在通过flume实时向hbase写数据，是否有办法将hbase新增的数据实时同步到phoenix的映射表和phoenix的二级索引表中

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC0

Not sure if this would be the right thread to attach this discussion: do we plan to also release 4.14.x patch for the CDH branches? On Thu, May 2, 2019 at 12:12 PM Thomas D'Silva wrote: > -1 > > PHOENIX-5101 and PHOENIX-5266 are blockers. > > On Tue, Apr 23, 2019 at 5:24

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC0

.close(RoundRobinResultIterator.java:125) ~[phoenix-core-4.14.2-HBase-1.2.jar:4.14.2-HBase-1.2] ... 64 common frames omitted On Mon, Apr 22, 2019 at 5:11 PM William Shen wrote: > Seems to be due to https://issues.apache.org/jira/browse/HBASE-14963 which > is not in HBase-1.2 > > On Mon, Apr 22, 2019 at 4:

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC0

Seems to be due to https://issues.apache.org/jira/browse/HBASE-14963 which is not in HBase-1.2 On Mon, Apr 22, 2019 at 4:38 PM William Shen wrote: > the bottom of the stacktrace: > Caused by: org.apache.hadoop.hbase.DoNotRetryIOException: > java.lang.IllegalAccessError: tried to acce

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC0

) at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:210) ... 39 more On Mon, Apr 22, 2019 at 4:26 PM William Shen wrote: > Not sure if it's a local issue unique to my setup, but when I set up my > Java client to use 4.14.2, I encounter the follow upon making a JDBC > connection. An

Re: [VOTE] Release of Apache Phoenix 4.14.2 RC0

Not sure if it's a local issue unique to my setup, but when I set up my Java client to use 4.14.2, I encounter the follow upon making a JDBC connection. Anyone else? Exception in thread "main" org.apache.phoenix.exception.PhoenixIOException: java.lang.IllegalAccessError: tried to access method

[jira] [Assigned] (PHOENIX-5254) Broken Link to Installation Section of the Download Page

[ https://issues.apache.org/jira/browse/PHOENIX-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen reassigned PHOENIX-5254: - Assignee: Xinyi Yan > Broken Link to Installation Section of the Download P

[jira] [Created] (PHOENIX-5254) Broken Link to Installation Section of the Download Page

William Shen created PHOENIX-5254: - Summary: Broken Link to Installation Section of the Download Page Key: PHOENIX-5254 URL: https://issues.apache.org/jira/browse/PHOENIX-5254 Project: Phoenix

Re: [DISCUSS] Making a 4.14.2 release for bug fixes

mutations Resolved Fixed Improvement PHOENIX-4900 Modify MAX_MUTATION_SIZE_EXCEEDED and MAX_MUTATION_SIZE_BYTES_EXCEEDED exception message to recommend turning autocommit on for deletes Resolved Fixed On Sat, Apr 13, 2019 at 5:59 PM William Shen wrote: > Also, there're a handful of tickets alre

[jira] [Updated] (PHOENIX-5184) HBase and Phoenix connection leaks in Indexing code path, OrphanViewTool and PhoenixConfigurationUtil

[ https://issues.apache.org/jira/browse/PHOENIX-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5184: -- Fix Version/s: 4.14.2 > HBase and Phoenix connection leaks in Indexing code p

[jira] [Updated] (PHOENIX-5101) ScanningResultIterator getScanMetrics throws NPE

[ https://issues.apache.org/jira/browse/PHOENIX-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5101: -- Fix Version/s: 4.14.2 > ScanningResultIterator getScanMetrics throws

[jira] [Updated] (PHOENIX-5131) Make spilling to disk for order/group by configurable

[ https://issues.apache.org/jira/browse/PHOENIX-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5131: -- Fix Version/s: 4.14.2 > Make spilling to disk for order/group by configura

Re: [DISCUSS] Making a 4.14.2 release for bug fixes

ere are some JIRAs to backport that > come to mind: > > https://issues.apache.org/jira/browse/PHOENIX-5184 > https://issues.apache.org/jira/browse/PHOENIX-5169 > https://issues.apache.org/jira/browse/PHOENIX-5131 > > Thanks, > Chinmay > > > On Fri, Apr 12, 2019 at 1:3

[DISCUSS] Making a 4.14.2 release for bug fixes

Hi, Since there're still some blockers for 4.15, what does the community feel about back-porting some of the bug fixes for a 4.14.2 release? One issue I have in mind is the NPE fix ( https://issues.apache.org/jira/browse/PHOENIX-5101). Is there anything else that would be of interest? Thanks -

Re: Plan to release 4.15.0?

ou the email thread about how we did the 4.14.1 release. > > On Thu, Apr 11, 2019 at 5:09 PM William Shen > wrote: > > > Thomas, > > I would love to help, but need someone to show me how :) > > > > On Thu, Apr 11, 2019 at 4:43 PM Thomas D'Silva > > wrote:

Re: Plan to release 4.15.0?

includes other bug fixes as well. > Will are you interested in being RM for 4.14.2 ? > > On Thu, Apr 11, 2019 at 4:17 PM William Shen > wrote: > > > Hi, > > > > Looking to pick up the fix for PHOENIX-5101 > > <https://issues.apache.org/jira/browse/

Plan to release 4.15.0?

Hi, Looking to pick up the fix for PHOENIX-5101 from 4.15.0, and wondering what's the expectation on when we think 4.15.0 will be considered for release. Took a quick look, and seems like current blockers are: PHOENIX-5103

[jira] [Updated] (PHOENIX-5166) DELETE didn't work on phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5166: -- Fix Version/s: 4.15.0 Restoring the fix version, as I was informed that a future fix version

Re: Unresolved JIRA issue with Fix Version

Thanks for the clarification. I will restore the fix version for a JIRA ticket that I removed. On Thu, Apr 11, 2019 at 12:04 PM Thomas D'Silva wrote: > The future release version is used to indicate a planned target. > > On Wed, Apr 10, 2019 at 4:37 PM William Shen > wro

[jira] [Created] (PHOENIX-5238) Pass NO_CACHE Hint with PhoenixRDD

William Shen created PHOENIX-5238: - Summary: Pass NO_CACHE Hint with PhoenixRDD Key: PHOENIX-5238 URL: https://issues.apache.org/jira/browse/PHOENIX-5238 Project: Phoenix Issue Type: New

Unresolved JIRA issue with Fix Version

Hi, Quick question about issue tracking for Apache Phoenix. There're a handful of tickets currently in unresolved states (Open, In Progress, Patch Available), and yet have the Fix Version specified as 4.15.0. Are these incorrectly marked with a fix version, or do we use future release in the Fix

[jira] [Updated] (PHOENIX-5166) DELETE didn't work on phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5166: -- Fix Version/s: (was: 4.15.0) I am removing the fixed version from this JIRA, as I cannot

PartialIndexRebuilderIT Flaky?

Hi, Saw that we've tried in the past to address the flakiness of PartialIndexRebuilderIT (PHOENIX-4239), but wondering if this is still an issue. I am on phoenix-4.13-HBase-1.2, and 9 times out of 10 this test fails running out of time. Anyone knows if there're any tricks to make the build less

[jira] [Updated] (PHOENIX-5122) PHOENIX-4322 breaks client backward compatibility

[ https://issues.apache.org/jira/browse/PHOENIX-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5122: -- Description: Scenario : *4.13 client -> 4.14.1 server* {noformat} Connected to: Phoe

Re: CDH 6.X road map

; working bits and push it. > > On Fri, 22 Feb 2019, 00:45 William Shen, > wrote: > > > Mahdi, > > I did a little bit of mailinglist/JIRA-diving, and found the following > > thread, which may be helpful to get you started in addition to the two > JIRA > &g

Re: CDH 6.X road map

ce Curtis On Wed, Feb 20, 2019 at 1:28 PM William Shen wrote: > Same here. Would love to help with adding more CDH versions, if someone > can help guide us on how to best go about it based on the current cdh > branches. > > On Tue, Feb 12, 2019 at 5:10 PM Mahdi Salarkia > wrote

Re: How Phoenix JDBC connection get hbase configuration

wrote: > I'm trying out on the mapreduce application, I made it work on my toy > application > > On Wed, Feb 20, 2019 at 4:09 PM William Shen > wrote: > > > A bit of a long shot, but do you happen to have another hbase-site.xml > > bundled in your jar accidentally

Re: How Phoenix JDBC connection get hbase configuration

A bit of a long shot, but do you happen to have another hbase-site.xml bundled in your jar accidentally that might be overriding what is on the classpath? On Wed, Feb 20, 2019 at 3:58 PM Xiaoxiao Wang wrote: > A bit more information, I feel the classpath didn't get passed in correctly > by

Re: How Phoenix JDBC connection get hbase configuration

Hi Xiaoxiao, Have you tried including hbase-site.xml in your conf on classpath? Will On Wed, Feb 20, 2019 at 2:50 PM Xiaoxiao Wang wrote: > Hi, who may help > > We are running a Hadoop application that needs to use phoenix JDBC > connection from the workers. > The connection works, but when

Re: CDH 6.X road map

Same here. Would love to help with adding more CDH versions, if someone can help guide us on how to best go about it based on the current cdh branches. On Tue, Feb 12, 2019 at 5:10 PM Mahdi Salarkia wrote: > Hi > Is there a plan to release a Hbase-2.0-CDH (Cloudera 6.X) compatible > version of

Re: Integration Testing Requirements

Funny. The specific IT passed locally for me. Seems more like a Jenkins setup to troubleshoot for us... Thanks for your help Ankit. On Wed, Feb 20, 2019 at 12:07 PM William Shen wrote: > Thanks Ankit. > > What is the difference between these hive tests > (e.g., org.apache.phoenix.hi

Re: Integration Testing Requirements

, Feb 19, 2019 at 11:39 AM Ankit Singhal wrote: > you can check if HADOOP_HOME and JAVA_HOME are properly set in the > environment. > > On Tue, Feb 19, 2019 at 11:23 AM William Shen > wrote: > > > Hi everyone, > > > > I'm trying to set up the Jenkins

Integration Testing Requirements

Hi everyone, I'm trying to set up the Jenkins job at work to build Phoenix and run the integration tests. However, repeatedly I encounter issues with the hive module when I run mvn verify. Does the hive integration tests require any special set up for them to pass? The other modules passed

[jira] [Updated] (PHOENIX-5067) Support for secure Phoenix cluster in Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5067: -- Description: Currently Phoenix performance and functional testing tool  {{Pherf}} doesn't

[jira] [Updated] (PHOENIX-5067) Support for secure Phoenix cluster in Pherf

[ https://issues.apache.org/jira/browse/PHOENIX-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-5067: -- Summary: Support for secure Phoenix cluster in Pherf (was: Support for secure Phoenix

Re: System.Catalog Table

We've also run into this problem in Phoenix 4.13 Here are steps to reproduce: 1) create original table in phoenix CREATE TABLE IF NOT EXISTS "test"."TRACKING_VALUES" ( "cstId" BIGINT NOT NULL, "cltId" BIGINT NOT NULL, "trkblTp" VARCHAR NOT NULL,

Access Client Side Metrics for PhoenixRDD usage

Hi all, I see that LLAM-1819 had implemented client metric collection mechanism in the PhoenixRecordReader class, which I believe is then used by PhoenixInputFormat and then used by PhoenixRDD, but I am having trouble locating example of how we can access the metric on

[jira] [Updated] (PHOENIX-4428) Trace details can't be shown in the Phoenix Tracing Web Application

[ https://issues.apache.org/jira/browse/PHOENIX-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Shen updated PHOENIX-4428: -- Comment: was deleted (was: Saw the fix here: [https://github.com/apache/phoenix/commit

[jira] [Created] (PHOENIX-4876) Delete returns incorrect number of rows affected in some case

William Shen created PHOENIX-4876: - Summary: Delete returns incorrect number of rows affected in some case Key: PHOENIX-4876 URL: https://issues.apache.org/jira/browse/PHOENIX-4876 Project: Phoenix

[jira] [Comment Edited] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528148#comment-16528148 ] William Shen edited comment on PHOENIX-4551 at 6/29/18 7:56 PM

[jira] [Commented] (PHOENIX-4551) Possible ColumnAlreadyExistsException is thrown from delete when autocommit off

[ https://issues.apache.org/jira/browse/PHOENIX-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528148#comment-16528148 ] William Shen commented on PHOENIX-4551: --- [~rajeshbabu], We are running into a similar issue

Re: Almost ready for HBaseCon+PhoenixCon 2018 SanJose CFP

Hi Josh, Looking forward to HBaseCon/PhoenixCon tomorrow. Just a quick question about the agenda, the timeline posted on the sites seem to diff slightly (trying to plan ahead :) ), and I am assuming HBase/PhoenixCon site is the source of truth?

[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

[ https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469480#comment-16469480 ] William Shen commented on PHOENIX-3431: --- Great, thanks for the pointers [~jamestaylor]. We

[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

[ https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468113#comment-16468113 ] William Shen commented on PHOENIX-3431: --- Thanks [~jamestaylor] for the speedy reply. The tool

[jira] [Commented] (PHOENIX-3431) Generate DDL from an existing Phoenix Schema

[ https://issues.apache.org/jira/browse/PHOENIX-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468103#comment-16468103 ] William Shen commented on PHOENIX-3431: --- [~jamestaylor], we have created a standalone tool

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16242794#comment-16242794 ] William Shen commented on PHOENIX-3112: --- Thank you for the clarification [~sergey.soldatov

[jira] [Commented] (PHOENIX-3112) Partial row scan not handled correctly

[ https://issues.apache.org/jira/browse/PHOENIX-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241202#comment-16241202 ] William Shen commented on PHOENIX-3112: --- [~sergey.soldatov], I see your comment: bq. Committed

Provide an option to infinite retry when updating index failed

does everybody think? Thanks William

[jira] [Commented] (PHOENIX-3994) Index RPC priority still depends on the controller factory property in hbase-site.xml

[ https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101257#comment-16101257 ] William Yang commented on PHOENIX-3994: --- I've done the test that [PHOENIX-3360-V4.patch|https

[jira] [Commented] (PHOENIX-3994) Index RPC priority still depends on the controller factory property in hbase-site.xml

[ https://issues.apache.org/jira/browse/PHOENIX-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088523#comment-16088523 ] William Yang commented on PHOENIX-3994: --- First, I'm deeply sorry for the committed patch

[jira] [Commented] (PHOENIX-2388) Support pooling Phoenix connections

[ https://issues.apache.org/jira/browse/PHOENIX-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867327#comment-15867327 ] William Yang commented on PHOENIX-2388: --- Anyone have time to have a look at this? What else shall

[jira] [Comment Edited] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865236#comment-15865236 ] William Yang edited comment on PHOENIX-3360 at 2/14/17 8:28 AM: bq

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865298#comment-15865298 ] William Yang commented on PHOENIX-3360: --- New patch attached. There is another reason we have

[jira] [Updated] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-3360: -- Attachment: PHOENIX-3360-v4.PATCH > Secondary index configuration is wr

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15865236#comment-15865236 ] William Yang commented on PHOENIX-3360: --- bq. CompoundConfiguration treats the added configs

[jira] [Updated] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-3360: -- Attachment: ConfCP.java > Secondary index configuration is wr

[jira] [Updated] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-3360: -- Attachment: PHOENIX-3360-v3.PATCH bq. I think Ankit Singhal was saying that the priorities

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858891#comment-15858891 ] William Yang commented on PHOENIX-3360: --- bq. What's the problem facing by setting the RPC class

[jira] [Updated] (PHOENIX-2388) Support pooling Phoenix connections

[ https://issues.apache.org/jira/browse/PHOENIX-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-2388: -- Attachment: (was: PHOENIX-2388.patch) > Support pooling Phoenix connecti

[jira] [Updated] (PHOENIX-2388) Support pooling Phoenix connections

[ https://issues.apache.org/jira/browse/PHOENIX-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-2388: -- Attachment: PHOENIX-2388.patch > Support pooling Phoenix connecti

[jira] [Updated] (PHOENIX-2388) Support pooling Phoenix connections

[ https://issues.apache.org/jira/browse/PHOENIX-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-2388: -- Attachment: PHOENIX-2388.patch This is a very simple connection pool. Do u have time to have

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852818#comment-15852818 ] William Yang commented on PHOENIX-3360: --- PHOENIX-3360-v2.patch attached, [~jamestaylor

[jira] [Updated] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Yang updated PHOENIX-3360: -- Attachment: PHOENIX-3360-v2.PATCH > Secondary index configuration is wr

[jira] [Comment Edited] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851023#comment-15851023 ] William Yang edited comment on PHOENIX-3360 at 2/3/17 4:08 AM: --- I don't

[jira] [Commented] (PHOENIX-3360) Secondary index configuration is wrong

[ https://issues.apache.org/jira/browse/PHOENIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851023#comment-15851023 ] William Yang commented on PHOENIX-3360: --- I don't think that current patch has solved the problem

[jira] [Commented] (PHOENIX-3498) Query with index failed when query back to data table with desc PK column

[ https://issues.apache.org/jira/browse/PHOENIX-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15675675#comment-15675675 ] William Yang commented on PHOENIX-3498: --- This should be a very old bug, I think the reason

  1   2   >