4.4.0 tags in git

Hi! I went to git[1] today to try to get the official tags for the 4.4.0 release and noticed that there are a bunch of rc0 and rc1 tags, but no official pushed tags for 4.4.0. Anyone have the official ones handy that they could push, please? Additional brownie points if someone can clean up

Re: 4.4.0 tags in git

Thanks so much, Mujtaba! Mujtaba Chohan wrote: Added: https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=1557b5d34ec5bd4d6c99b23a5bff63cc6b5cec31 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=890e3ac7bcb571dd7269ee56d61c00d243a04d74 On Thu, Jul 30, 2015 at 12:37 PM,

[ANNOUNCE] Apache Calcite Avatica 1.8.0 released

problems and get involved, visit the project website at: https://calcite.apache.org/avatica/ or the Apache Calcite project website: https://calcite.apache.org/ Thanks to everyone involved! Josh Elser, on behalf of the Apache Calcite team.

Re: Jenkins build failures?

it definitely means that the code was compiled with 1.8 since 1.7 returns a simple Set while 1.8 returns KeySetView On Thu, Apr 28, 2016 at 4:08 PM, Josh Elser< josh.el...@gmail.com <javascript:;>> wrote: *tl;dr* * I'm removing ubuntu-us1 from all pools * Phoenix-Flu

Re: Please share the status of GSoC project

: Please find the answers inline. On 2 June 2016 at 21:22, Josh Elser <josh.el...@gmail.com <mailto:josh.el...@gmail.com>> 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

Re: Please share the status of GSoC project

2016 at 22:04, Josh Elser <josh.el...@gmail.com <mailto:josh.el...@gmail.com>> wrote: 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 ma

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

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

Re: Are we ready for 4.8.0 RC?

+1 VOTE is ongoing over on dev@calcite.a.o for an Avatica 1.8.0 (anyone with a binding vote over there would be appreciated too) This would be a nice gain for Phoenix-4.8 (perf improvements, new features, better docs, etc). I can try to help knock out some of those issues you mentioned as

Re: Regular build failures

We can try, but, IMO, it's not likely that we'll get a very positive answer from them. Better use of time would probably be trying to identify if there are certain nodes which are flakey (and just avoid them completely) and if there is anything we can do to stabilize the tests (reduce number

Re: RC on Monday

r done or have +1s on them. so how about having RC by Thursday EOD? Checked with Rajesh too , PHOENIX-1734 is also ready for 4.x branches and will be committed by tomorrow. Regards, Ankit Singhal On Wed, Jun 1, 2016 at 12:33 PM, Nick Dimiduk<ndimi...@gmail.com> wrote: On Wed, Jun 1, 2016

Re: [ANNOUNCE] New Apache Phoenix committer - Josh Elser

Thanks everyone! Happy to join the ranks, and I'm looking forward to helping out more :) James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Josh Elser has accepted our invitation to become a committer on the Apache Phoenix project. He's done an excellent job

Re: Jenkins build failures?

*tl;dr* * I'm removing ubuntu-us1 from all pools * Phoenix-Flume ITs look busted * UpsertValuesIT looks busted * Something is weirdly wrong with Phoenix-4.x-HBase-1.1 in its entirety. Details below... It looks like we have a bunch of different reasons for the failures. Starting with

Re: Jenkins build failures?

Also, didn't mean to ignore you Sergey. I haven't seen anything at the moment which pointed to getting more info from -X (general flakiness from the ASF jenkins boxes is... the norm). We can definitely do this if we think there is something concrete that we're missing. Sergey Soldatov

Re: [ANNOUNCE] Ankit Singhal joins Phoenix PMC

Congrats and well deserved, Ankit! James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Ankit Singhal has accepted our invitation to become a member of the Apache Phoenix project management committee (PMC). Recently he's implemented two of the most asked for

Re: Phoenix : Update protobuf-java and guava version

Hi Naveen, The Protocol Buffer dependency on 2.5 is very unlikely to change in Phoenix as that is directly inherited from HBase (as you can imagine, these need to be kept in sync). There are efforts, in both HBase and Phoenix, underway to provide shaded-jars for each project which would

Force-unsubscribe user list subscriber (was: Fwd: DELIVERY FAILURE: Error transferring to QCMBSJ601.HERMES.SI.SOCGEN; Maximum hop count exceeded. Message probably in a routing loop.)

ecute" not "prepareAndExecuteBatch". Josh Elser wrote: Thanks, will fix this. Plamen Paskov wrote: Ah i found the error. It should be "sqlCommands": instead of "sqlCommands", The documentation syntax is wrong for this request type: http://calcite.apache.org/avatica/docs/json_refe

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

Sean Busbey was a fine gent and gave me some great feedback this morning. I think it's in a good place -- does anyone else want to look at it before I merge it? Josh Elser wrote: From a packaging perspective, I think this is good to go. https://github.com/apache/phoenix/pull/183 I've asked

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

:16 AM, Josh Elser<josh.el...@gmail.com> wrote: Sean Busbey was a fine gent and gave me some great feedback this morning. I think it's in a good place -- does anyone else want to look at it before I merge it? Josh Elser wrote: From a packaging perspective, I think this is good to go.

Re: new 4.8.0 RC?

. Maybe we should just delete the 4.8 branches and recreate them once the RC is up? On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser<josh.el...@gmail.com> wrote: Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I just noticed that we have the same Maven versions on both the 4.8 a

Re: [ANNOUNCE] Josh Elser joins Phoenix PMC

Thank you all! I look forward to working more closely with everyone :D James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Josh Elser has accepted our invitation to become a member of the Apache Phoenix PMC. Recently he found and fixed licensing-related issues

[DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

(Moving this over to its own thread to avoid bogging down the VOTE further) PMC, what say you? I have cycles to work on this now. Original Message Subject: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0 Date: Mon, 18 Jul 2016 14:43:54 -0400 From: Josh Elser <josh

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

. Meanwhile, I'll run a few tests myself to make sure the code is still working as intended :) Josh Elser wrote: A quick update from me for those not watching the JIRA issues: I've found two LGPL dependencies that have been bundled in the binary artifact which *must* not be included

Re: Errors while launching sqlline

You can check the dev list for the VOTE thread which contains a link to the release candidate but it is not an official Apache Phoenix release yet. Vasanth Bhat wrote: Thanks a lot Ankit. where do I download this from? I am looking at http://mirror.fibergrid.in/apache/phoenix/don't seem

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

On Jul 17, 2016, at 10:53 AM, Josh Elser<els...@apache.org> wrote: -1 (non-binding) from me with my Phoenix hat on (avoiding putting on the ASF member hat for now). Lots of wrong licensing stuff in here -- as-in, this should very definitely not go out as a release. I hope the Phoenix

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

Ankit Singhal wrote: @Josh, bq. Bad: * SHA1 xsum is wrong. It looks like complete nonsense to me, but I can't find the appropriate xsum in that file (which was 64208164580f3467cd2c8b51c0d9f8ac37f0c671) In Phoenix , we don't use SHA1 , SHA files has only SHA-512 and SHA-256

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

Sean Busbey wrote: On Mon, Jul 18, 2016 at 12:05 PM, Ankit Singhal wrote: Now we have three options to go forward with 4.8 release (or whether to include licenses and notices for the dependency used now or later):- *Option 1:- Go with this RC0 for 4.8 release.*

Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0

binary LICENSE and NOTICE files using templates and velocity macros. Sean Busbey did the lion's share of the work. Refer to https://issues.apache.org/jira/browse/HBASE-14085 . It was a significant effort. On Jul 17, 2016, at 10:53 AM, Josh Elser<els...@apache.org> wrote: -1 (non-bind

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

;> > Am I reading the tallies correctly? >>> > >>> > 0.98: pass with four +1s >>> > 1.0: pass with four +1s >>> > 1.1: fail with two +1s >>> > 1.2: pass with three +1s, one -1, and one non-binding -1 >>> > >>> &

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

. Option 1 is not a good option. Let's go with another. On Jul 18, 2016, at 1:53 PM, Josh Elser<els...@apache.org> wrote: (Moving this over to its own thread to avoid bogging down the VOTE further) PMC, what say you? I have cycles to work on this now. Original Message S

Re: [DISCUSS] Licensing in 4.8.0 rc0 (was Fwd: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0)

/resolved.html#category-x [2] https://issues.apache.org/jira/browse/PHOENIX-3101 [3] https://issues.apache.org/jira/browse/PHOENIX-3102 James Taylor wrote: Ok, that's great then. We can just combine the separate vote emails into one then. Much easier. Thanks, James On Tuesday, July 19, 2016, Josh Elser

Re: New RC?

I just filed https://issues.apache.org/jira/browse/PHOENIX-3136. This one is pretty serious IMO and I plan to get a patch up and tested within the next hour or so. Sorry for the last-minute-ness of it. tl;dr The shading changes broke backwards wire compatibility of PQS due to how the Avatica

Re: [VOTE] Release of Apache Phoenix 4.8.0 RC2

+1 (non-binding) * xsums/sigs match * KEYS published and contains key used for signing * `mvn apache-rat:check package` passes on each src tarball * Skimmed L for each to verify contents looked correct (trusting past-Josh for the most part, see caveat below). The (non-blocker)

Re: [DISCUSS] Some licensing issues to resolve before the next release

://github.com/tdunning/open-json On Thu, Feb 9, 2017 at 12:10 PM, Josh Elser<els...@apache.org> wrote: See https://issues.apache.org/jira/browse/PHOENIX-3658 and https://issues.apache.org/jira/browse/PHOENIX-3659 for the full details. The summary is that I noticed two dependencies that we're inc

[DISCUSS] Some licensing issues to resolve before the next release

See https://issues.apache.org/jira/browse/PHOENIX-3658 and https://issues.apache.org/jira/browse/PHOENIX-3659 for the full details. The summary is that I noticed two dependencies that we're including (one direct, one transitive) that are disallowed. The direct dependency (org.json:json by

Re: [DISCUSS] Some licensing issues to resolve before the next release

the dependency problem as long as we don't detect a regression by doing so. On Thu, Feb 9, 2017 at 1:10 PM, Josh Elser<els...@apache.org> wrote: Sweetness. Thanks for taking that on! Josh Mahonin wrote: Re: the flume dependency, I suspect we can swap out the org.json:json depe

Re: [ANNOUNCE] Apache Phoenix 4.8.0 released

(-cc other lists) Hi Afshin, The release notes you referenced are more meant to alert users about any issues in the new release that you may run into over previous releases. "Release notes provide details on issues and their fixes which may have an impact on prior Phoenix behavior" - Josh

Re: [DISCUSS] Drop HBase 1.0 support for 4.9

+1 la...@apache.org wrote: The HBase 1.0.x branch has been EOL'd, I propose we drop support for it with Phoenix 4.9.I'd also propose that should HBase have a stable 1.3.x release soon, we should support it with Phoenix 4.9. -- Lars

Re: 4.8.1, 4.9.0, 4.9.1, and 4.10.0

For the lazy: https://s.apache.org/KxB1 (JIRA search results for all unresolved issues with fixVersion=4.9.0, but not fixVersion=4.8.1 too) la...@apache.org wrote: Hi All, as we're two active branches right now, it is important to remember (1) that fixes are pushed to both 4.8xxx and 4.x

Re: [ANNOUNCE] New Apache Phoenix committer - Geoffrey Jacoby

Congrats, Geoffrey! Well deserved! James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Geoffrey Jacoby has accepted our invitation to become a committer on the Apache Phoenix project. He's been involved with Phoenix for two years and his list of fixed issues

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

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

TestIndexWriter hanging on 4.8-HBase-0.98

FYI, currently bisect'ing this test hang. I am assuming it affects more than just 4.8-HBase-0.98, just pursuing it on this one branch for now. Will file a JIRA case and ping the author of the offending commit when I get to the bottom of it ;) - Josh

Re: TestIndexWriter hanging on 4.8-HBase-0.98

Correction: 4.8 0.98 and 1.0 both hang with JDK8 Threaddump: https://paste.apache.org/Iput Josh Elser wrote: Hrm, maybe this is me just being silly. I forgot that I finally switched my JAVA_HOME to jdk8. Is it not expected that the hbase-0.98 wouldn't be working with JDK8? The 1.x branches

Re: [VOTE] The first rc (RC0) for Phoenix 4.8.1 is available

+1 (binding) However, it looks like your GPG key isn't present in the include KEYS file nor in subversion[1], Lars. I don't think the fact that it's not in the source is problem, but it definitely needs to be present in dist.a.o before this is released. For src's * sigs/xsums OK * L look

Re: [DISCUSS] Making upgrade to a new minor release a manual step

+1 to the idea. Automatic upgrades on your behalf with knowledge can be scary. But, let me pose a hypothetical: say I upgrade from Phoenix X to Phoenix Y. I have some application that using Phoenix X and I want to make sure that before I finish my upgrade to Phoenix Y that things are "OK". It

Re: Guidence for phoenix calcite development

Hi Krishna, Thanks for your interest in contributing to Apache Phoenix. Have you seen http://phoenix.apache.org/contributing.html? Please take some time to read through the information on the website and then ask a more pointed question if you are confused. - Josh Shiva Krishna wrote: Hi

Re: I want to provide a module that provides the unshaded version of the jdbc client.

Hey Marco, Just to clarify: Nick and I were not arguing against the value provided by shaded versions of Phoenix jars. We were more confused with your explanation of the problem(s) you outlined. Personally, you will never see me argue that we will create a shaded client jar that *does not*

Re: [VOTE] The first rc (RC0) for Phoenix 4.8.1 is available

5A9D D0BE B8C5 C7CF E328. -- Lars From: Josh Elser<els...@apache.org> To: dev@phoenix.apache.org Sent: Friday, September 23, 2016 2:48 PM Subject: Re: [VOTE] The first rc (RC0) for Phoenix 4.8.1 is available +1 (binding) However, it looks like your GPG key isn't present in the i

Re: plan to cut RC for 4.9.0 on Fri (10/28)

I'd like to get updated to Avatica 1.9.0 for Phoenix 4.9.0 (let's us do PHOENIX-3004), but its vote is scheduled to close tmrw. That _should_ give me time to push in the update and do some basic testing before Friday. Might I be able to sway you into casting a vote over there to make sure

Re: plan to cut RC for 4.9.0 on Fri (10/28)

howstopper fixes in Avatica 1.9.0, are you ok with getting that in the next Phoenix release planned for one month from now, Josh? Thanks, James On Wed, Oct 26, 2016 at 12:20 PM, Josh Elser<josh.el...@gmail.com> wrote: I'd like to get updated to Avatica 1.9.0 for Phoenix 4.9.0 (let's us

Re: plan to cut RC for 4.9.0 on Fri (10/28)

:-) )? Thanks, James On Fri, Oct 28, 2016 at 8:08 AM, Josh Elser<els...@apache.org> wrote: I wouldn't -1 4.9.0 over it since it's my own lack of time to have gotten out an Avatica release prior to this, but my feelings are best summarized by a -0. There aren't any show-stoppers, but

Re: python-phoenixdb

+1 I was poking around with it this weekend. I had some issues (trying to use it from the Avatica side, instead of PQS, specifically), but for the most part it worked. Definitely feel free to report any issues you run into: https://bitbucket.org/lalinsky/python-phoenixdb. It would be nice to

Re: [ANNOUNCE] New Apache Phoenix committer - Kevin Liew

Congrats, Kevin! James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Kevin Liew has accepted our invitation to become a committer on the Apache Phoenix project. He's done an great job finding and fixing many important Phoenix JIRAs as well as most recently

Re: Unassigned issues to look at

Hi Vikash, Can you share some details on this (e.g. what branch of Phoenix, what version of Eclipse)? There is configuration we can place in the pom.xml for Phoenix which should properly configure the Eclipse project's classpath when you import it as a Maven project. Would be good to make

Re: Excessive ExecService RPCs with multi-threaded ingest

ive impact (with serialized IndexMaintainers only being about 20bytes for one index table, the server-side memory impact certainly isn't that crazy, but the extra RPCs likely adds up). Feedback welcome from the brave :) Josh Elser wrote: Hi folks, I was doing some testing earlier this week

Excessive ExecService RPCs with multi-threaded ingest

Hi folks, I was doing some testing earlier this week and Enis's keen eye caught something rather interesting. When using YCSB to ingest data into a table with a secondary index using 8 threads and batch size of 1000 rows, the number of ExecService coprocessor calls actually exceeded the

Re: Coprocessor metrics

Yep -- see avatica-metrics[1], avatica-dropwizard-metrics3[2], and my dropwizard-hadoop-metrics2[3] project for what Nick is referring to. What I ended up doing in Calcite/Avatica was a step beyond your #3, Enis. Instead of choosing a subset of some standard metrics library to expose, I

Re: Excessive ExecService RPCs with multi-threaded ingest

the client and prepare them at the server itself and cache/refresh it per table like we do currently for PTable? On Mon, Oct 24, 2016 at 9:32 AM, Josh Elser<josh.el...@gmail.com> wrote: If anyone is interested, I did hack on this some more over the weekend. https://github.com/joshelser/phoeni

Precommit builds stuck due to no nodes

It would appear that Precommit builds are hung due to having no available Jenkins nodes to execute the jobs on. I'm guessing this has to do with Infra's recent re-working of some of the worker node labels. Just an FYI that I'm looking into it and I'll send a note when I get a resolution in

Re: Precommit builds stuck due to no nodes

work for our builds. Keep an eye on things, and send me a ping if you see precommit builds failing reliably on certain hosts and we can go from there. The queue of precommit jobs is starting to be worked off as I type. Josh Elser wrote: It would appear that Precommit builds are hung

Re: [VOTE] Release of Apache Phoenix 4.9.0 RC5

+1 (binding) * xsums/sigs pass * KEYS is present * Verified no change in pom.xml (for dependencies which might affect L) For each src-release: * Top level LICENSE/NOTICE files look OK * No unexpected binary files or files missing ASL header in src release (`mvn apache-rat:check`) * Can build

Re: [VOTE] Release of Apache Phoenix 4.8.2 RC2

+1 (binding) * KEYS is good * xsums/sigs are good * No change in dependencies since 4.8.1 For each src-release: * No binary files * L are good * Can build and run tests (mvn apache-rat:check package) Ran a simple local test with the resulting artifact built by hbase-1.2-src. la...@apache.org

Re: Sample phoenix upserts using threads

(cc: -dev +user, bcc: +dev) Hi Krishna, Might you be able to share the stacktrace that accompanied that Exception? Shiva Krishna wrote: Hi All, Can any one give me a small example of Phoenix upserts using Threads in Java. I wrote a sample it is working fine in local environment but when

Re: plan to cut RC for 4.9.0 on Fri (10/28)

FYSA -- I'm doing this Avatica upgrade and pushing in PHOENIX-3004 now. James Taylor wrote: Ok, thanks, Josh. We can hold off until Mon for the RC so we can get the latest and greatest Avatica. On Fri, Oct 28, 2016 at 2:26 PM, Josh Elser<els...@apache.org> wrote: Looks like Alan just

Re: plan to cut RC for 4.9.0 on Fri (10/28)

Superb. Much appreciated! James Taylor wrote: Ok, thanks, Josh. We can hold off until Mon for the RC so we can get the latest and greatest Avatica. On Fri, Oct 28, 2016 at 2:26 PM, Josh Elser<els...@apache.org> wrote: Looks like Alan just voted, so it will pass once the 72hrs is up.

Re: plan to cut RC for 4.9.0 on Fri (10/28)

. Thanks, James On Mon, Oct 31, 2016 at 6:15 AM, Josh Elser<els...@apache.org> wrote: FYSA -- I'm doing this Avatica upgrade and pushing in PHOENIX-3004 now. James Taylor wrote: Ok, thanks, Josh. We can hold off until Mon for the RC so we can get the latest and greatest Avatica. On Fri,

Re: [VOTE] Release of Apache Phoenix 4.8.2 RC2

No worries! Thanks to you for making the time to do this all. I just wanted to make sure you hadn't forgotten about it :) la...@apache.org wrote: Yeah... Sorry *very* busy. Will call the vote, do the release, and announce. -- Lars From: Josh Elser<els...@apache.org> T

Re: Coprocessor metrics

Enis Söztutar wrote: Bumping this up in case people are interested. Also this is not coprocessor-specific, because I think we can incrementally start using the new hbase-metrics module, and get rid of our complicated metrics2 based patterns for core metrics as well. We should of course start

Re: Phoenix Tuning Guide

Thanks for sending a note, Peter. I'll try to give it a glance. Peter Conrad wrote: The Phoenix Tuning Guide has been through several reviews and revisions. The latest version is attached to PHOENIX-3218: https://issues.apache.org/jira/browse/PHOENIX-3218 Please take a look and comment with

Re: Phoenix ODBC driver

There's been chatter of building an ODBC driver in Apache Calcite channels (as PQS is built on Avatica which falls under the Calcite umbrella) but no one has stepped up to build such a driver yet. The driver available via Hortonworks/Simba is the only one I am presently aware of. Evagelos

Re: [VOTE] Release of Apache Phoenix 4.8.2 RC2

Hey Lars, Is a +1 from yourself to be implied here (if not, anyone want to add one)? Would be nice to get this one out too. - Josh Thomas D'Silva wrote: +1 Ran integration tests. Ran some manual tests for indexes and transactions. On Wed, Nov 23, 2016 at 12:20 PM, Josh Elser<

Re: python-phoenixdb

-11-07 18:12 GMT+01:00 Josh Elser<els...@apache.org>: +1 I was poking around with it this weekend. I had some issues (trying to use it from the Avatica side, instead of PQS, specifically), but for the most part it worked. Definitely feel free to report any issues you run into: https://b

Re: FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2

Sergey too. ;) Will catch up over on dev@hbase. Thanks for making sure we were aware of this one downstream, Stack. On Apr 11, 2017 19:53, "James Taylor" wrote: > Thanks for the heads-up, Stack. Josh is our resident shading expert - > hopefully he'll chime in based on

Re: [VOTE] Release of Apache Phoenix 4.10.0 RC1

+1 (binding) * xsums/sigs OK * can build from src * verified no new dependencies (for L) * Commits for the RC exist in scm * Ran unit tests James Taylor wrote: Hello Everyone, This is a call for a vote on Apache Phoenix 4.10.0 RC1. This is the next minor release of Phoenix 4, compatible with

Re: Seeking feedback on severity of change to hbase coprocessor api from phoenix community.

Hey Sean, Thanks for taking a moment to ask! I did a quick grep over some branches for `RpcServerInterface` and I don't see any usages. The only thing I could find (and, that I was aware of) was some use of the RpcScheduler classes. It doesn't seem like this change would cause any heartburn.

Re: PreCommit busted again

I seem to have gotten things back to normal. Shout if things are busted. Also filed PHOENIX-4011 to fix some of the things in the test-patch.properties file. On 7/11/17 1:46 PM, Josh Elser wrote: Seems like the dev/test-patch.sh files just don't even exist for the 4.x-HBase-0.98 branch. I'm

Re: [DISCUSS] Dropping 4.x-HBase-0.98?

suspect our contingent of contributors and committers will come around to your viewpoint, Josh. On Wed, Jul 19, 2017 at 3:57 PM, Josh Elser <els...@apache.org> wrote: Do folks have any strong opinions on whether or not we should continue to target a Phoenix release against HBase 0.98?

[DISCUSS] Handling missing HBase features/code across versions

Hi all, James raised a good question on PHOENIX-3598 surrounding how Phoenix should handle the case when a specific version of HBase that Phoenix uses is lacking/missing some kind of code/functionality. For example, I wrote some test cases which set-up a minicluster with Kerberos. HBase

Re: [DISCUSS] Handling missing HBase features/code across versions

Thanks for the reply! On 7/24/17 9:52 PM, Andrew Purtell wrote: As a coprocessor application there is no way not to be bogged down in internal details. Coprocessors are by definition mixin extensions to internal HBase code. Compatibility discontinuities are going to be a fact of life. All

[DISCUSS] Dropping 4.x-HBase-0.98?

Do folks have any strong opinions on whether or not we should continue to target a Phoenix release against HBase 0.98? I seem to recall our Andrew prioritizing newer HBase releases instead of continuing the 0.98 cadence. Any reason to not do the same? - Josh

Re: HBase 2.0 future integration.

Sergey Soldatov wrote: Hi, Well, HBase 2.0 will be released in the near future and we need to think about adopting Phoenix to it. I tried to do that and already feel uncomfortable with the amount of changes related to existing and potential problems. There are the list of problems I'm aware

Re: Question about Git tag for 4.8.2 release and RC2

mwbg/Screenshot%202017-05-15%2008.32.45.png?dl=0 for reference of what we are seeing (which has no "tag" link to those commits). No worries, it is OK to use the commit hashes, we were merely wondering why they were not tagged, and also why the naming changed. Cheers, Lars On Tue, May 9, 2017 at

Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)

tl;dr Infra is upgrading Jenkins in 2 weeks and Java7 Maven jobs may/may-not work after this. See explanation below from [1]: Users with jobs configured with the "Maven project" type may not be able to use Java 7 for their Maven jobs. The correct behavior is not guaranteed so proceed at your

Re: Missing precommit results

On 6/1/17 11:24 AM, Josh Elser wrote: FYI -- it seems like something went awry with Infra's installation of the latest Maven on the Jenkins nodes. As such, if you've put up a patch in the last ~18hrs, you'll probably notice two things: 1) PreCommit didn't comment on your JIRA issue 2) A job

Missing precommit results

FYI -- it seems like something went awry with Infra's installation of the latest Maven on the Jenkins nodes. As such, if you've put up a patch in the last ~18hrs, you'll probably notice two things: 1) PreCommit didn't comment on your JIRA issue 2) A job did run, but it failed after ~15s,

Re: RC for 4.11.0 by end of week?

https://issues.apache.org/jira/browse/PHOENIX-3891 would be nice to get in. If a user runs into this, things would blow up fairly quickly :). Test provided, just needs a review. Let me get a patch up for 3895. On 5/30/17 8:07 PM, James Taylor wrote: We've got a bunch of good bug fixes in our

Re: [VOTE] Release of Apache Phoenix 4.11.0 RC1

+1 (binding) * xsums/sigs OK * Verified pom.xml made no changes (implying no required L changes) * apache-rat:check on all src archives * Can build from source on all archives * Ran all UT/IT successfully on hbase-1.3 release - Josh On 6/14/17 4:57 PM, James Taylor wrote: Hello Everyone,

Re: Question about Git tag for 4.8.2 release and RC2

Hi Lars, The tags for 4.8.2 are: https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3d4205123f763fdfd875211d551da42deeb78412 https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=40de1f6cd5326b2c8ec2da5ad817696e050c2f3a

Re: [VOTE] Release of Apache Phoenix 4.12.0 RC0

+1 (binding) * apache-rat:check OK * Couldn't find any unexpected binaries * Could build from source * xsums/sigs OK * Could run all UTs Will try to do some more later today. Thanks all for getting this put together. On 10/4/17 3:46 AM, James Taylor wrote: Hello Everyone, This is a call

Re: [DISCUSS] Road to HBase 2.0.0

an umbrella issue once we have a plan for the version based on HBase 2.0 -Anoop- On Thu, Oct 12, 2017 at 3:30 AM, Josh Elser <els...@apache.org> wrote: Since 4.12.0 is out and we have the concurrent discussions about the 0.98, 1.1, and 1.2 HBase branches, do folks have a vision of how

[ANNOUNCE] New PMC Member: Sergey Soldatov

All, The Apache Phoenix PMC has recently voted to extend an invitation to Sergey to join the PMC in recognition of his continued contributions to the community. We are happy to share that he has accepted this offer. Please join me in congratulating Sergey! Congratulations on a well-deserved

Re: [DISCUSS] discontinue HBase 1.1 based Phoenix releases

I'm still mulling this over, but my first reaction is that I think this is an acceptable solution going forward (agreeing with your "lighter burden" sentiments in the other thread). Would kindly request a few days to give it some thought before we make any decisions. On 10/11/17 12:59 PM,

Re: [ANNOUNCE] New Phoenix committer: Vincent Poon

Congrats Vincent! On 10/11/17 9:51 PM, James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm delighted to announce that Vincent Poon has accepted our invitation to become a committer. He's had a big impact in helping to stabilize our secondary index implementation, including the creation

Re: [ANNOUNCE] New Phoenix committer: Ethan Wang

Congrats Ethan! On 10/11/17 9:45 PM, James Taylor wrote: On behalf of the Apache Phoenix PMC, I'm please to announce that Ethan Wang has accepted our invitation to become a committer. He's behind some of the great new 4.12 features of table sampling [1] and approximate count distinct [2] along

Re: [DISCUSS] Road to HBase 2.0.0

-2.0 the master branch Thoughts? On Fri, Oct 13, 2017 at 8:31 AM, Josh Elser <els...@apache.org> wrote: Thanks, Anoop! I know Sergey, Ankit, and Rajeshbabu have been looking at this already. While tracking it is good, I think we still need to come up with a plan for where we're going to

Re: [DISCUSS] discontinue HBase 1.1 based Phoenix releases

1.1.14 will be the last release (though I'm still not sure that DISCUSS thread has reached a conclusion). On Wed, Oct 11, 2017 at 2:54 PM Josh Elser <els...@apache.org> wrote: I'm still mulling this over, but my first reaction is that I think this is an acceptable solution going forwa

Re: [DISCUSS] Road to HBase 2.0.0

to be locked-down internal and external API -- but better late than never. Thanks, St.Ack 1. https://docs.google.com/document/d/10cabwp_ aR3OmpHVoeh544YLC3KwqMD9KiTIrHZAmfec/edit#heading=h.7swwa1jl6wiw On Wed, Oct 11, 2017 at 3:00 PM, Josh Elser <els...@apache.org> wrote: Since 4.12.0 is out

Re: [DISCUSS] Road to HBase 2.0.0

On 10/18/17 2:51 PM, Andrew Purtell wrote: Hopefully, Phoenix will not find itself in a position where business-critical things it's doing are being removed from API (and Phoenix has no recourse to hack what it needs back in place). I feel fairly confident this is going to happen given the

Re: Phoenix Salted Table Rowkey Issue

If you want to use Phoenix, please use Phoenix APIs to read and write the data. You are wholly responsible for understanding how to correctly write the data given Phoenix's schema if you bypass it. On 12/13/17 9:25 AM, Oussama BEN BACCAR wrote: Hello Phoenixers, I have a rowkey issue when

Re: rename 5.0-HBase-2.0 branch to 5.x-HBase-2.0

Just went ahead and did it. No problem from my POV. On 10/31/17 1:54 PM, James Taylor wrote: I propose we rename the 5.0-HBase-2.0 branch to 5.x-HBase-2.0 so that we can do all 5.x based releases from this branch similar to the way we do for 4.x-HBase-###.

  1   2   3   4   5   6   7   8   9   10   >