[jira] [Commented] (PHOENIX-3045) Data regions in transition forever if RS holding them down during drop index

[ https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373143#comment-15373143 ] Jesse Yates commented on PHOENIX-3045: -- FWIW, i don't remember the thoughts on using the caching

[jira] [Commented] (PHOENIX-2892) Scan for pre-warming the block cache for 2ndary index should be removed

[ https://issues.apache.org/jira/browse/PHOENIX-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286053#comment-15286053 ] Jesse Yates commented on PHOENIX-2892: -- We need the locks when the edits are updating rows

Re: [ANNOUNCE] Ankit Singhal joins Phoenix PMC

Congrats Ankit! On Tue, May 3, 2016, 8:01 PM Nick Dimiduk wrote: > Nice work Ankit, congrats! > > On Tuesday, May 3, 2016, James Taylor wrote: > > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Ankit > > Singhal has accepted our

Re: Continuing Trace UI work?

I sent this to James the other day, didn't get a chance to post it on the JIRA yet: *I was poking around htrace and zipkin and it looks like zipkin has a jdbc storage plugin. Might be a nice little piece of work to integrate phoenix into that - would act as storage for the zipkin collector

[jira] [Commented] (PHOENIX-2756) FilteredKeyValueScanner should not implement KeyValueScanner

[ https://issues.apache.org/jira/browse/PHOENIX-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15190177#comment-15190177 ] Jesse Yates commented on PHOENIX-2756: -- Seems ok to me. Nice change - love all the code going away

[jira] [Commented] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145219#comment-15145219 ] Jesse Yates commented on PHOENIX-2674: -- Committed to 1.0, 4.x-HBase-1.0, and 4.x-HBase-0.98. Thanks

[jira] [Resolved] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates resolved PHOENIX-2674. -- Resolution: Fixed Fix Version/s: 4.7.0 > PhoenixMapReduceUtil#setInput doesn't ho

[jira] [Reopened] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates reopened PHOENIX-2674: -- Huh, those are a little surprising test failures. Looking into it, but have a full afternoon

[jira] [Commented] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145460#comment-15145460 ] Jesse Yates commented on PHOENIX-2674: -- sorry about that [~giacomotaylor] - it just seemed so

[jira] [Commented] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145516#comment-15145516 ] Jesse Yates commented on PHOENIX-2674: -- Ok, think I found it. Stupid missed line. Anyways, running

[jira] [Resolved] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates resolved PHOENIX-2674. -- Resolution: Fixed > PhoenixMapReduceUtil#setInput doesn't honor condition cla

[jira] [Commented] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145603#comment-15145603 ] Jesse Yates commented on PHOENIX-2674: -- Test suite passed locally. Pretty sure about this one

[jira] [Assigned] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates reassigned PHOENIX-2674: Assignee: Jesse Yates > PhoenixMapReduceUtil#setInput doesn't honor condition cla

[jira] [Updated] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-2674: - Attachment: PHOENIX-2674.patch Attaching formal patch that includes m/r test

[jira] [Commented] (PHOENIX-2667) Race condition between IndexBuilder and Split for region lock

[ https://issues.apache.org/jira/browse/PHOENIX-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141568#comment-15141568 ] Jesse Yates commented on PHOENIX-2667: -- Was thinking we might be able to get away

[jira] [Updated] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

[ https://issues.apache.org/jira/browse/PHOENIX-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-2674: - Attachment: phoenix-2674-v0-without-test.patch Attaching a simple patch that just builds

[jira] [Created] (PHOENIX-2674) PhoenixMapReduceUtil#setInput doesn't honor condition clause

Jesse Yates created PHOENIX-2674: Summary: PhoenixMapReduceUtil#setInput doesn't honor condition clause Key: PHOENIX-2674 URL: https://issues.apache.org/jira/browse/PHOENIX-2674 Project: Phoenix

[jira] [Created] (PHOENIX-2677) PhoenixMapReduceUtil#setOutput() doesn't build correct column names

Jesse Yates created PHOENIX-2677: Summary: PhoenixMapReduceUtil#setOutput() doesn't build correct column names Key: PHOENIX-2677 URL: https://issues.apache.org/jira/browse/PHOENIX-2677 Project

[jira] [Commented] (PHOENIX-2667) Race condition between IndexBuilder and Split for region lock

[ https://issues.apache.org/jira/browse/PHOENIX-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141954#comment-15141954 ] Jesse Yates commented on PHOENIX-2667: -- Yeah, that's what I was thinking. Correct wrt read vs write

[jira] [Commented] (PHOENIX-2667) Race condition between IndexBuilder and Split for region lock

[ https://issues.apache.org/jira/browse/PHOENIX-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15139672#comment-15139672 ] Jesse Yates commented on PHOENIX-2667: -- Well, that sucks. Is there any way we can process that read

Re: [ANNOUNCE] Ankit Singhal added as Apache Phoenix committer

gt; > > >> Congratulations Ankit! > > >> > > >> On Mon, Feb 1, 2016 at 7:43 PM, Josh Mahonin <jmaho...@gmail.com> > > wrote: > > >> > > >> > Great work Ankit, well deserved! > > >> > > > >> >

Re: [ANNOUNCE] Ankit Singhal added as Apache Phoenix committer

Congratulations and welcome! On Sun, Jan 31, 2016, 11:49 AM Ravi Kiran wrote: > Congrats Ankit !! > > On Sun, Jan 31, 2016 at 11:41 AM, Nick Dimiduk > wrote: > > > Thanks for the contributions Ankit, and congratulations! > > > > On Sunday,

[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=15083425#comment-15083425 ] Jesse Yates commented on PHOENIX-2535: -- I think Storm already shades all its dependencies, so I'm

[jira] [Commented] (PHOENIX-2503) Multiple Java NoClass/Method Errors with Spark and Phoenix

[ https://issues.apache.org/jira/browse/PHOENIX-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051439#comment-15051439 ] Jesse Yates commented on PHOENIX-2503: -- Meh, seems ok. Maybe add a comment to that build target

[jira] [Resolved] (PHOENIX-1910) Sort out maven assembly dependencies

[ https://issues.apache.org/jira/browse/PHOENIX-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates resolved PHOENIX-1910. -- Resolution: Won't Fix > Sort out maven assembly dependenc

[jira] [Commented] (PHOENIX-1910) Sort out maven assembly dependencies

[ https://issues.apache.org/jira/browse/PHOENIX-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978880#comment-14978880 ] Jesse Yates commented on PHOENIX-1910: -- I think people have figured this out - can we drop

Re: [ANNOUNCE] New Apache Phoenix committer - Jan Fernando

Congrats and welcome! On Wed, Sep 30, 2015, 3:48 AM Ted Yu wrote: > Congratulations, Jan. > > On Tue, Sep 29, 2015 at 11:29 AM, Thomas D'Silva > wrote: > > > Congrats Jan! > > > > On Tue, Sep 29, 2015 at 11:23 AM, Eli Levine >

Re: [DISCUSS] discontinue 4-x HBase 1.0 releases?

Along the same lines as HBase, it seems fine to discontinue old code lines until such point as there is someone willing to maintain a given line - a new RM. Essentially, its the same as an RM stepping down from managing a release and no releases happening until someone cares enough to make a new

Re: [ANNOUNCE] Welcome our newest Committer Dumindu Buddhika

Welcome and congrats! On Fri, Sep 18, 2015 at 8:27 AM rajeshb...@apache.org < chrajeshbab...@gmail.com> wrote: > Congratulations Dumindu!!! > Great work. > > Thanks, > Rajeshbabu. > > On Fri, Sep 18, 2015 at 7:43 PM, Ted Yu wrote: > > > Congratulations Dumindu > > > > On

[jira] [Commented] (PHOENIX-2183) Write to log when actually doing WAL replay

[ https://issues.apache.org/jira/browse/PHOENIX-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700515#comment-14700515 ] Jesse Yates commented on PHOENIX-2183: -- Seems trivial. Only concern would

[jira] [Commented] (PHOENIX-2183) Write to log when actually doing WAL replay

[ https://issues.apache.org/jira/browse/PHOENIX-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700517#comment-14700517 ] Jesse Yates commented on PHOENIX-2183: -- oh, and +1 on patch Write to log when

[jira] [Updated] (PHOENIX-2183) Fix debug log line when doing secondary index WAL replay

[ https://issues.apache.org/jira/browse/PHOENIX-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-2183: - Summary: Fix debug log line when doing secondary index WAL replay (was: Add debug log line

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

There was some discussion (maybe internal to salesforce?) around how to include the query in the trace. I think the simplest we came up with was just adding it to the trace metadata (as an annotation?) and then you can pull it out later since you know the key it was stored as On Wed, Jun 24, 2015

Re: [ANNOUNCE] Josh Mahonin added as Apache Phoenix committer

Congrats and welcome! On Tue, Jun 23, 2015, 10:01 AM Ravi Kiran maghamraviki...@gmail.com wrote: Welcome Josh!! On Tue, Jun 23, 2015 at 11:55 AM, Nick Dimiduk ndimi...@apache.org wrote: Nice work, congratulations Josh, and welcome! On Tue, Jun 23, 2015 at 9:40 AM, James Taylor

[jira] [Commented] (PHOENIX-2025) Phoenix-core's hbase-default.xml prevents HBaseTestingUtility from starting up in client apps

[ https://issues.apache.org/jira/browse/PHOENIX-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571631#comment-14571631 ] Jesse Yates commented on PHOENIX-2025: -- Kind of a major issue for anyone running

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

Ids are randomly assigned. Spans have parents (the process/thread/logic element) that kicked them off, so each span is going to have a parent id. All 'start' spans have the same 'parent id' the ROOT SPAN ID. On Tue, Jun 2, 2015 at 8:34 AM Ayola Jayamaha raphaelan...@gmail.com wrote: Hi, I'm

Re: Issue in Phoenix Tracing

for the property files. But is it the correct way since still the tracing table is missing. Do we need to create is manually or is it created automatically when configured correctly. Thanks. On Mon, May 25, 2015 at 10:55 PM, Jesse Yates jesse.k.ya...@gmail.com wrote: You are missing either

Re: Issue in Phoenix Tracing

You are missing either the hadoop-metrics2-phoenix.properties,hadoop-metrics2.properties on the classpath. The setup of these files should be discussed on the tracing page of the website. On Mon, May 25, 2015, 12:26 AM Ayola Jayamaha raphaelan...@gmail.com wrote: Hi All, I am using

[jira] [Commented] (PHOENIX-1977) Always getting No FileSystem for scheme: hdfs when exported HBASE_CONF_PATH

[ https://issues.apache.org/jira/browse/PHOENIX-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549775#comment-14549775 ] Jesse Yates commented on PHOENIX-1977: -- bq. Phoenix needs hadoop jars in the class

[jira] [Commented] (PHOENIX-1979) FamilyOnlyFilter should test for != INCLUDE instead of == SKIP

[ https://issues.apache.org/jira/browse/PHOENIX-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14549777#comment-14549777 ] Jesse Yates commented on PHOENIX-1979: -- Yeah, I think we can drop those classes

[jira] [Updated] (PHOENIX-1965) Upgrade Pig to version 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1965: - Fix Version/s: 4.5.0 Upgrade Pig to version 0.13

[jira] [Updated] (PHOENIX-1965) Upgrade Pig to version 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1965: - Fix Version/s: 4.4.0 Upgrade Pig to version 0.13

[jira] [Commented] (PHOENIX-1965) Upgrade Pig to version 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544263#comment-14544263 ] Jesse Yates commented on PHOENIX-1965: -- Committed to master. Happy to commit to 4.x

[jira] [Commented] (PHOENIX-1965) Upgrade Pig to version 0.13

[ https://issues.apache.org/jira/browse/PHOENIX-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14542232#comment-14542232 ] Jesse Yates commented on PHOENIX-1965: -- So, I'm only going to commit

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540851#comment-14540851 ] Jesse Yates commented on PHOENIX-1954: -- I'm ok with {{NEXT n VALUE FOR seq

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538672#comment-14538672 ] Jesse Yates commented on PHOENIX-1954: -- In the original discussion that came up, we

[jira] [Commented] (PHOENIX-1954) Reserve chunks of numbers for a sequence

[ https://issues.apache.org/jira/browse/PHOENIX-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538769#comment-14538769 ] Jesse Yates commented on PHOENIX-1954: -- I think its more that we want to reserve

Re: Reminder: merge commits

I think we need control of the git server and I don't know if apache will let us have the pre-commit-hooks installed. I don't think its worth it... as long as we are careful. they aren't the end of the world :) On Fri, Apr 24, 2015 at 5:47 PM Nick Dimiduk ndimi...@gmail.com wrote: That's how it

[jira] [Commented] (PHOENIX-1728) Pherf - Make tests use mini cluster

[ https://issues.apache.org/jira/browse/PHOENIX-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509710#comment-14509710 ] Jesse Yates commented on PHOENIX-1728: -- bq. moving the phoenix-assembly module

[jira] [Commented] (PHOENIX-1728) Pherf - Make tests use mini cluster

[ https://issues.apache.org/jira/browse/PHOENIX-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509808#comment-14509808 ] Jesse Yates commented on PHOENIX-1728: -- This is one of the caveats of using

[jira] [Commented] (PHOENIX-1728) Pherf - Make tests use mini cluster

[ https://issues.apache.org/jira/browse/PHOENIX-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509926#comment-14509926 ] Jesse Yates commented on PHOENIX-1728: -- +1 and mind filing a follow-up on me

Re: Assemblies and tgz's

of HBase/Hadoop we're not packaging against. The only things in their class path is the HBASE_CONF_DIR and the client assembly jar. On Fri, Apr 17, 2015 at 2:14 PM, Jesse Yates jya...@apache.org wrote: I think it was for convenience of packaging. While we have transitive dependencies

Re: please fix IDE compiler errors for pherf and phoenix-server

A little harsh, dont you think? He said he was going to look at it... And technically, it still compiles (in mvn, the source of compilation truth) so it's not blocking anyone On Sat, Apr 18, 2015, 9:45 AM James Taylor jamestay...@apache.org wrote: Cody, For everyone using the default Eclipse

Re: Assemblies and tgz's

I think it was for convenience of packaging. While we have transitive dependencies, they resolve when including the HBase/Hadoop classpaths as well. I think mostly this was to make it easy to run from the tarball using sqline or the various python scripts in the bin/ directory. If no one is using

[jira] [Commented] (PHOENIX-1824) Run all IT's through Query Server

[ https://issues.apache.org/jira/browse/PHOENIX-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485704#comment-14485704 ] Jesse Yates commented on PHOENIX-1824: -- Are you thinking we will want to run all

[jira] [Commented] (PHOENIX-971) Query server

[ https://issues.apache.org/jira/browse/PHOENIX-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484267#comment-14484267 ] Jesse Yates commented on PHOENIX-971: - Have you tried renaming

Re: phoenix-client in maven repo?

if the latter, it's because we don't have one right now, which I think is a mistake in our pom structure. As in, you think the client code needs to be separated from the server code so that you need less stuff on the client? Yes, totally.. but its not trivial to get there :) And has it really

Re: [jira] [Issue Comment Deleted] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

I think this would be a great discussion to continue on the JIRA. Would you mind reposting there (PHOENIX-1118)? Thanks Ayola! -J On Tue, Mar 24, 2015 at 10:17 AM Ayola Jayamaha raphaelan...@gmail.com wrote: Hi All, What is the most preferred way you would like for me to integrate the

Re: [jira] [Comment Edited] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

Hi Nishani, Thanks for your interesting in phoenix! For tracing, the first thing I would recommend doing is reading the tracing documentation: http://phoenix.apache.org/tracing.html A careful reading there would then lead you to look at org.apache.phoenix.trace.PhoenixTableMetricsWriterIT for

[jira] [Commented] (PHOENIX-39) Add sustained load tester that measures throughput

[ https://issues.apache.org/jira/browse/PHOENIX-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14355576#comment-14355576 ] Jesse Yates commented on PHOENIX-39: +1 overall; this is massive though, so I'd want

[jira] [Commented] (PHOENIX-1241) Add typing to trace annotations

[ https://issues.apache.org/jira/browse/PHOENIX-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350494#comment-14350494 ] Jesse Yates commented on PHOENIX-1241: -- Yeah, byte[] was nice in a general sense

[jira] [Commented] (PHOENIX-938) Use higher priority queue for index updates to prevent deadlock

[ https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349091#comment-14349091 ] Jesse Yates commented on PHOENIX-938: - Yup, that's a bug. Over on PHOENIX-1676 we

[jira] [Commented] (PHOENIX-1676) Set priority of Index Updates correctly

[ https://issues.apache.org/jira/browse/PHOENIX-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340926#comment-14340926 ] Jesse Yates commented on PHOENIX-1676: -- bq. Could this be why

Re: Simulating HBase write failures in Phoenix tests

Yeah, I've done that a handful of times in HBase-land (not sure where though). It gets tricky with phoenix using all the BaseTest stuff because it does a lot of setup things that could conflict with what you are trying to do.* What I was frequently doing was using a static latch for turning

Re: Simulating HBase write failures in Phoenix tests

useful. Any pointers to specific tests that spin up Coprocessors dynamically in Phoenix? On Mon, Feb 9, 2015 at 11:51 AM, Jesse Yates jesse.k.ya...@gmail.com wrote: Yeah, I've done that a handful of times in HBase-land (not sure where though). It gets tricky with phoenix using all

[jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client Phoenix-Server jars into Maven Repo

[ https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14261730#comment-14261730 ] Jesse Yates commented on PHOENIX-1567: -- bq. Is it good practice to publish über

[jira] [Updated] (PHOENIX-1233) Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError

[ https://issues.apache.org/jira/browse/PHOENIX-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1233: - Attachment: phoenix-1233-v1.patch I think we still need something like what i'm attaching. You

[jira] [Commented] (PHOENIX-1233) Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError

[ https://issues.apache.org/jira/browse/PHOENIX-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254482#comment-14254482 ] Jesse Yates commented on PHOENIX-1233: -- That patch doesn't preclude any

[jira] [Updated] (PHOENIX-1233) Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, preempting StackOverflowError

[ https://issues.apache.org/jira/browse/PHOENIX-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1233: - Attachment: phoenix-1233-master-v1.patch Attaching patch that removes slf4j-log4j12 from client

[jira] [Commented] (PHOENIX-1115) Provide a SQL command to turn tracing on/off

[ https://issues.apache.org/jira/browse/PHOENIX-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244688#comment-14244688 ] Jesse Yates commented on PHOENIX-1115: -- So that was just using the standard HTrace

Re: [ANNOUNCE] Samarth Jain added as Apache Phoenix committer

Congrats and welcome! Well deserved! On Sat Dec 06 2014 at 4:56:53 PM rajesh babu Chintaguntla chrajeshbab...@gmail.com wrote: Congratulations Samarth! On Dec 7, 2014 4:41 AM, lars hofhansl la...@apache.org wrote: Welcome Samarth! From: James Taylor jamestay...@apache.org To:

[jira] [Commented] (PHOENIX-1470) KEEP_DELETED_CELLS interface changed in HBase 0.98.8

[ https://issues.apache.org/jira/browse/PHOENIX-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14219520#comment-14219520 ] Jesse Yates commented on PHOENIX-1470: -- Yes, the 0.98.8 release has already been

[jira] [Created] (PHOENIX-1470) KEEP_DELETED_CELLS interface changed in HBase 0.98.8

Jesse Yates created PHOENIX-1470: Summary: KEEP_DELETED_CELLS interface changed in HBase 0.98.8 Key: PHOENIX-1470 URL: https://issues.apache.org/jira/browse/PHOENIX-1470 Project: Phoenix

[jira] [Updated] (PHOENIX-1470) KEEP_DELETED_CELLS interface changed in HBase 0.98.8

[ https://issues.apache.org/jira/browse/PHOENIX-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1470: - Attachment: keep-deleted-cells.patch Attaching a basic patch that at least allows compilation

[jira] [Updated] (PHOENIX-1470) KEEP_DELETED_CELLS interface changed in HBase 0.98.8

[ https://issues.apache.org/jira/browse/PHOENIX-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1470: - Attachment: keep-deleted-cells-v1.patch Updated slightly with something that at least tests

[jira] [Commented] (PHOENIX-1470) KEEP_DELETED_CELLS interface changed in HBase 0.98.8

[ https://issues.apache.org/jira/browse/PHOENIX-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14218837#comment-14218837 ] Jesse Yates commented on PHOENIX-1470: -- I think we have to keep carrying

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14215016#comment-14215016 ] Jesse Yates commented on PHOENIX-1457: -- Seems very feasible. The only thing I would

Re: [VOTE] Release of Apache Phoenix 4.2.1 RC1

I dont think it is that unreasonable to not split the sequences table for a release (this is the incompatible change, right?) to gain the ability to mix 4.1 and 4.2 clients. Yes, its a new part of the compatibility story but honestly a necessity to anyone looking to run phoenix in production

Re: phoenix backup and recovery

You absolutely can use snapshots with phoenix. You would need to snapshot both the phoenix metadata table and the table you want to snapshot. Then on restore, you restore both those tables to new tables, point phoenix there and get the data you need. Missing pieces: 1) I'm not sure there is a

[jira] [Comment Edited] (PHOENIX-1331) DropIndexDuringUpsertIT.testWriteFailureDropIndex times out

[ https://issues.apache.org/jira/browse/PHOENIX-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14199015#comment-14199015 ] Jesse Yates edited comment on PHOENIX-1331 at 11/5/14 8:33 PM

[jira] [Commented] (PHOENIX-1381) NPE in CellUtil.matchingFamily() for IndexedKeyValue

[ https://issues.apache.org/jira/browse/PHOENIX-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14185583#comment-14185583 ] Jesse Yates commented on PHOENIX-1381: -- My only concern is if this will work

[jira] [Updated] (PHOENIX-1286) Remove hadoop2 compat modules

[ https://issues.apache.org/jira/browse/PHOENIX-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1286: - Fix Version/s: 4.2 5.0.0 Remove hadoop2 compat modules

[jira] [Resolved] (PHOENIX-1286) Remove hadoop2 compat modules

[ https://issues.apache.org/jira/browse/PHOENIX-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates resolved PHOENIX-1286. -- Resolution: Fixed Committed to 4.2 and main. thanks for the review [~jamestaylor]! Remove

[jira] [Commented] (PHOENIX-1286) Remove hadoop2 compat modules

[ https://issues.apache.org/jira/browse/PHOENIX-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14180260#comment-14180260 ] Jesse Yates commented on PHOENIX-1286: -- Nope, because it never got reviewed :-/ Its

[jira] [Created] (PHOENIX-1329) Correctly support varbinary arrays

Jesse Yates created PHOENIX-1329: Summary: Correctly support varbinary arrays Key: PHOENIX-1329 URL: https://issues.apache.org/jira/browse/PHOENIX-1329 Project: Phoenix Issue Type: Bug

[jira] [Updated] (PHOENIX-1329) Correctly support varbinary arrays

[ https://issues.apache.org/jira/browse/PHOENIX-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1329: - Attachment: phoenix-1329-bug.patch Attaching patch to _demonstrate_ the issue. Its going

[jira] [Commented] (PHOENIX-1107) Support mutable indexes over replication

[ https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160597#comment-14160597 ] Jesse Yates commented on PHOENIX-1107: -- Not sure if I kept it around... will have

[jira] [Commented] (PHOENIX-1318) Tables with Put coprocessor cannot use HRegion.mutateRowsWithLocks()

[ https://issues.apache.org/jira/browse/PHOENIX-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160607#comment-14160607 ] Jesse Yates commented on PHOENIX-1318: -- Yeah, that sounds right. There are a couple

[jira] [Commented] (PHOENIX-1107) Support mutable indexes over replication

[ https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160609#comment-14160609 ] Jesse Yates commented on PHOENIX-1107: -- hehe, so it is. Future-proofing myself

[jira] [Resolved] (PHOENIX-1289) Drop index during upsert may abort RS

[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates resolved PHOENIX-1289. -- Resolution: Fixed Fix Version/s: 4.2 5.0.0 committed to master

[jira] [Commented] (PHOENIX-1289) Drop index during upsert may abort RS

[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160681#comment-14160681 ] Jesse Yates commented on PHOENIX-1289: -- hmm, looks like a flaky test issue Drop

[jira] [Commented] (PHOENIX-1107) Support mutable indexes over replication

[ https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160706#comment-14160706 ] Jesse Yates commented on PHOENIX-1107: -- Commited to 4.2 and master, leaving it open

[jira] [Updated] (PHOENIX-1107) Support mutable indexes over replication

[ https://issues.apache.org/jira/browse/PHOENIX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-1107: - Fix Version/s: 4.2 5.0.0 Support mutable indexes over replication

[jira] [Comment Edited] (PHOENIX-1289) Drop index during upsert may abort RS

[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14150896#comment-14150896 ] Jesse Yates edited comment on PHOENIX-1289 at 9/30/14 11:52 PM

[jira] [Comment Edited] (PHOENIX-1305) create index throws NPE when dataTable has specified default column family

[ https://issues.apache.org/jira/browse/PHOENIX-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14154066#comment-14154066 ] Jesse Yates edited comment on PHOENIX-1305 at 10/1/14 12:11 AM

[jira] [Commented] (PHOENIX-1289) Drop index during upsert may abort RS

[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148546#comment-14148546 ] Jesse Yates commented on PHOENIX-1289: -- Yup, that seems like a legitimate bug

[jira] [Commented] (PHOENIX-1289) Drop index during upsert may abort RS

[ https://issues.apache.org/jira/browse/PHOENIX-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148550#comment-14148550 ] Jesse Yates commented on PHOENIX-1289: -- Any interest in taking a shot at the fix

[jira] [Commented] (PHOENIX-103) Drop hadoop1.0 specifics from code

[ https://issues.apache.org/jira/browse/PHOENIX-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14145462#comment-14145462 ] Jesse Yates commented on PHOENIX-103: - Sounds good to me. I'll commit it now. Drop

[jira] [Updated] (PHOENIX-103) Drop hadoop1.0 specifics from code

[ https://issues.apache.org/jira/browse/PHOENIX-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated PHOENIX-103: Attachment: phoenix-103-4.0-v0.patch Attaching patch for change committed to 4.0 Drop hadoop1.0

[jira] [Created] (PHOENIX-1286) Remove hadoop2 compat modules

Jesse Yates created PHOENIX-1286: Summary: Remove hadoop2 compat modules Key: PHOENIX-1286 URL: https://issues.apache.org/jira/browse/PHOENIX-1286 Project: Phoenix Issue Type: Bug

  1   2   >