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

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 pass just fine. Josh Elser wrote: FYI, currently bisect'ing this test hang. I am assuming it af

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 bra

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* r

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 A

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&N look

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

05BC C9A1 5A9D D0BE B8C5 C7CF E328. -- Lars From: Josh Elser 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 include K

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

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 numb

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 su

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

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 that

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

Fri (10/28). If there are no showstopper 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 wrote: I'd like to get updated to Avatica 1.9.0 for Phoenix 4.9.

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

27;ll vote :-) )? Thanks, James On Fri, Oct 28, 2016 at 8:08 AM, Josh Elser 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 1.9

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 wrote: Looks like Alan just voted, so it will pass once the 72hrs is up. I can make sure that

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 wrote: Looks like Alan just voted, so it will

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

proceed with the 4.9.0 RC. Thanks, James On Mon, Oct 31, 2016 at 6:15 AM, Josh Elser 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: 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 runnin

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 imple

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-bu

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&N) 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: Excessive ExecService RPCs with multi-threaded ingest

s from 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 wrote: If anyone is interested, I did hack on this some more over the weekend. https://github.com/joshelser/phoenix/tree/reduced-server

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 pla

Re: Precommit builds stuck due to no nodes

sets of nodes won't 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 b

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&N 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: [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 wrote:

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 To: dev@phoenix.apache.org

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 e

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 CH

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

[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 pho

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

https://github.com/tdunning/open-json On Thu, Feb 9, 2017 at 12:10 PM, Josh Elser 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 including (one d

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

t 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 wrote: Sweetness. Thanks for taking that on! Josh Mahonin wrote: Re: the flume dependency, I suspect we can swap out the org.json:json dependency with com.tdunning:js

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 and

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

, Josh Elser wrote: 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

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: [VOTE] Release of Apache Phoenix 4.10.0 RC1

+1 (binding) * xsums/sigs OK * can build from src * verified no new dependencies (for L&N) * 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: python-phoenixdb

ards, James On Thu, Mar 23, 2017 at 5:21 PM, Dimitri wrote: Hi, I make some update on my fork of Lukáš Lalinský phoenix python lib. I integrate sqlalchemy and correct some bug. you can find the code source on https://github.com/Pirionfr/pyPhoenix and it's available in https://pypi.python.org/p

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 his experience/expertise.

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 https://git-wip-us.apache.org/repos/asf?p=phoenix.g

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 at

Re: Question about Git tag for 4.8.2 release and RC2

h3g008te08mwbg/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

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

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, simila

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

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&N 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, Th

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

PreCommit busted again

Looking into it...

Re: PreCommit busted again

Seems like the dev/test-patch.sh files just don't even exist for the 4.x-HBase-0.98 branch. I'm a bit perplexed because it doesn't look like they ever actually existed on that branch. On 7/11/17 1:30 PM, Josh Elser wrote: Looking into it...

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

[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: [DISCUSS] Dropping 4.x-HBase-0.98?

and then I 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 wrote: 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

[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 0.98

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 copro

[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: 2019/08 board report

Fixed -- thanks. The lists.a.o got truncated when I was making the shortened URL, it seems. On 8/14/19 8:48 PM, Artem Ervits wrote: Access denied or not found on the url. On Wed, Aug 14, 2019, 11:24 AM Josh Elser wrote: Hi all, Sending the board report which I'm about to submit to yo

Re: [Question] Apache Calcite integration

No, the effort has effectively stalled. It was a significant undertaking to get to where the Calcite integration was left, but, more importantly, required significantly more efforts to complete it than were available. I would assume that there is more that what exists today would still be ge

Re: Apache phoenix CDH 6.x

Moving this message to dev@phoenix. private@phoenix is not the appropriate list. On 10/23/19 9:37 AM, Kubica, Michal wrote: Hello, I would like to ask if there is some plan to release .parcel file also for Cloudera CDH 6.x versions as for example for CDH 5.14, 5.13 and so on. (sorry if this i

[DISCUSS] Omid and Tephra podlings

Hiya folks, There's a discussion[1] on general@incubator about the Omid and Tephra podlings, their decrease in volume (commits, discussion, activity), and what to do about them. If you'd like to contribute to that discussion, please watch on general@incubator and the dev lists for those podlin

Re: [DISCUSS] Omid and Tephra podlings

ndexes are a promising feature, and could be compelling, and they need one of these transaction oracles. '0' because it would be unfair to commit someone else's time. I'm not around here much... but may be around more going forward. On Thu, Oct 24, 2019 at 10:14 AM Josh Elser w

Re: [DISCUSS] Omid and Tephra podlings

s and so have some familiarity with them. We also have some overlap in the committers with Omid. At a minimum we’d need to create new compat modules when necessary for future HBase releases. The alternative would be to rip out the transaction support which would be a mistake IMHO. On Fri, Oct 2

Re: [DISCUSS] Omid and Tephra podlings

Just noticed that the links Alan sent out do explicitly require a formal VOTE. Incoming... On 10/30/19 10:06 AM, Josh Elser wrote: I am OK with Tephra and Omid committers becoming Phoenix committers. We can send them a welcome package to remind them that Phoenix is a "review-then-c

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

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 the guidance of a TLP (e.g. the TLP's PMC) Per the Incubator g

Re: When Phoenix 5.x for HBase-2.x will be updated?

ASF policy states that we have to talk about unreleased code on the dev list, not the user list. Moving this over to the dev list as such :) On 11/4/19 8:41 AM, Alexander Batyrshin wrote: As I see there are many bug fixes and updates (consistent indexes) for 4.x Phoenix branch. So im curios wh

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

This vote passes with 10 (binding) +1's, (2 non-binding) +1's, 1 (binding) +0, and nothing else. Thanks for all who took the time to vote. On 10/30/19 11:27 AM, Josh Elser wrote: Hi, As was previously discussed[1][2], there is a motion to "adopt" the Tephra and Omid podl

Re: Precommit Jenkins build is broken

What have you been able to find so far, Chinmay? For example, * Does every PreCommit build fail? If not, are we limited to a certain host(s) that causes failure? * Do local builds still work? * What's different (maven+java versions) from the build hosts to local builds? With coordination fr

Re: Precommit Jenkins build is broken

eFull> It looks like the build issue can be fixed if we apply PHOENIX-5459 to 4.x branches since that would bump up the surefire plugin version + support running tests on JDK11. If PHOENIX-5459 is not be included in 4.x branches for some reason, we should at least bump up the surefire plugin v

FYI q4 2019 board report

Sorry for not running this past everyone prior to submission (I dropped the ball on getting a draft together before it was due). Please take a look at the report below, and let me know if there are any concerns :) ## Description: The mission of Phoenix is the creation and maintenance of soft

Re: Omid&Tephra -> Phoenix sub-project next steps

;s going on the whole way. Alan. On Thu, Nov 14, 2019 at 8:32 AM Josh Elser wrote: I'm a bit confused about where we go from this point. Given the doc[1] that Alan shared last time, we are good to move ahead with the logistical changes. Further, the next guide[2] simply says that VP

Re: Omid&Tephra -> Phoenix sub-project next steps

. The not well documented process includes making a pointer to where to find the graduated project. Should I make this https://phoenix.apache.org/ until such time as Pheonix established a different location? Regards, Dave On 2019/11/19 17:32:14, Josh Elser wrote: Thanks, Alan. Filed

Re: Omid&Tephra -> Phoenix sub-project next steps

I've made https://phoenix.apache.org/omid.html and https://phoenix.apache.org/tephra.html as temporary place-holders if you'd like to use those for the podling graduation. On 11/21/19 1:47 PM, Josh Elser wrote: Hey Dave, Let me make some pointers on our website while we get the o

Re: Phoenix spark java integration example

Hi Karthigeyan, I'm moving your message over to the users list in the hopes that a more broad audience might see your ask. The dev list is focused around the day-to-day development of Apache Phoenix. I don't believe I've seen any examples of the phoenix-spark module in Java. If you happen to

Re: [VOTE] Release of Apache Phoenix 4.15.0 RC1

(sorry for piling on the vote thread) I would think that allowing rollback should be the _default_ case, especially when we know that there is an incompatibility. On 11/23/19 11:27 AM, Chinmay Kulkarni wrote: Copying my comment from PHOENIX-5584: "On second thought, I actually think this is

[ACTION REQUIRED] Omid & Tephra Migration to Phoenix LDAP

Hi, As a part of the exit of the Incubator, we need to consolidate the Omid and Tephra LDAP groups (the system that controls podling membership, committer privileges, etc) with the Phoenix LDAP group. For all of those Omid and Tephra podling members who intend to continue to contribute to Om

New committer: Istvan Toth

Everyone, On behalf of the PMC, I'm pleased to announce Apache Phoenix's newest committer: Istvan Toth. Please join me in extending a warm welcome to Istvan -- congratulations on this recognition. Thank you for your contributions and we all look forward to more involvement in the future! -

Re: [ACTION REQUIRED] Omid & Tephra Migration to Phoenix LDAP

Omid and Tephra resources to move them under Phoenix. For those who notice this at a later date, please include me in the "To:" line so that I don't miss your request to retain your privileges. - Josh On 11/26/19 1:25 PM, Josh Elser wrote: Hi, As a part of the exit of the Incubator, w

Re: [ACTION REQUIRED] Omid & Tephra Migration to Phoenix LDAP

eful by themselves and should be separated out, such as the type encoders and the key-building, as well as the high performance interface into HBase via coprocessors... among others. -- Lars On Tuesday, December 3, 2019, 9:56:24 AM PST, Josh Elser wrote: Andreas, Gokul, Terence, and Yo

Omid and Tephra migration nearly done

Hi, Infra was hard at work last week. Current status: Repositories migrated: * https://gitbox.apache.org/repos/asf?p=phoenix-omid.git * https://gitbox.apache.org/repos/asf?p=phoenix-omid-site.git * https://gitbox.apache.org/repos/asf?p=phoenix-tephra.git * http://svn.apache.org/viewvc/phoenix/te

Re: Moving Phoenix master to Hbase 2.2

As much as possible, I'd like to avoid us getting into another situation with 5.x where we have multiple branches. My hope was/is that we can keep one Phoenix5 branch that works against an acceptable set of HBase branches. To me, that acceptable set of HBase branches is _a_ 2.1 and 2.2 release

Omid and Tephra migration infra tasks complete

I believe all of the tasks we asked Infra to complete for the purpose of "graduating" these two podlings into Phoenix is complete. That said, as far as I know, we are done from the Phoenix side of this. CC'ing Alan in case there are more Incubator things that we need to do to close up the podl

Re: Moving Phoenix master to Hbase 2.2

7;s getting deprecated anytime soon. So there will be at least two significant features that can only exist in some but not all of our 4.x and 5.x branches. Geoffrey On Thu, Dec 12, 2019 at 8:21 AM Josh Elser wrote: As much as possible, I'd like to avoid us getting into another situation

Re: [ANNOUNCE] New Committer: Xinyi Yan

Congrats Xinyi! On 1/2/20 12:56 PM, Geoffrey Jacoby wrote: On behalf of the PMC, I'm pleased to announce that Xinyi Yan has accepted the PMC's invitation to become a committer on Apache Phoenix. Xinyi has contributed patches in a wide variety of areas, improved logging, been an active code revie

Re: The integration tests in phoenix-hive are broken?

Thanks for fixing this, Toshi! On 1/7/20 4:34 AM, Toshihiro Suzuki wrote: 1. I filed this in PHOENIX-5662 . On Tue, Dec 24, 2019 at 6:20 PM Toshihiro Suzuki wrote: Hi folks! I'm working on PHOENIX-5619

Make sure to check website diff before commit (was: FAQ page is blank now)

o racks of servers over a beer). Thanks for those of you who are making the docs better every day :) Forwarded Message Subject: Re: FAQ page is blank now Date: Thu, 9 Jan 2020 11:10:22 -0500 From: Josh Elser To: u...@phoenix.apache.org Indeed it is. Looks like a dev had a

Re: Python2 EOL

I think converting them to Bash is the right thing to do. We're not doing anything fancy. On 1/9/20 5:10 PM, Andrew Purtell wrote: Some of the python scripts are glorified shell scripts and could be rewritten as such, such as the launch scripts for psql and sqlline and the pqs. I get that pytho

Re: Moving Phoenix master to Hbase 2.2

ight be a pretty good model. It supports various versions of HBase in a single branch and has similar issues as Phoenix (coprocessors, etc). -- Lars On Thursday, December 19, 2019, 7:07:51 PM GMT+1, Josh Elser < els...@apache.org> wrote: To clarify, you think that compat modules a

Re: Moving Phoenix master to Hbase 2.2

d model. It supports various versions of HBase in a single branch and has similar issues as Phoenix (coprocessors, etc). -- Lars     On Thursday, December 19, 2019, 7:07:51 PM GMT+1, Josh Elser < els...@apache.org> wrote:   To clarify, you think that compat modules are better than that sepa

Re: Python2 EOL

rk to do. -- Lars On Friday, January 10, 2020, 7:55:43 AM PST, Josh Elser wrote: I think converting them to Bash is the right thing to do. We're not doing anything fancy. On 1/9/20 5:10 PM, Andrew Purtell wrote: Some of the python scripts are glorified shell scripts and could be

Re: Committers please look at the Phoenix tests and fix your failures

How do we keep getting into this mess: unreliable QA, people ignoring QA, or something else? On 1/12/20 9:24 PM, la...@apache.org wrote: ... Not much else to say here... The tests have been failing again for a while... I will NOT fix them again this time! Sorry folks. -- Lars

Re: Moving Phoenix master to Hbase 2.2

al compatibility API that is switchable at run (startup) time without a performance hit remains to be seen. István On Tue, Jan 14, 2020 at 3:21 AM Josh Elser wrote: Agree that trying to wrangle branches is just too frustrating and error-prone. It would also be great if we could have a single Ph

Re: Python2 EOL

as just my assumption) was that they were created to provide/facilitate compatibility with Windows. - Gabriel On Tue, Jan 14, 2020 at 3:22 AM Josh Elser wrote: Do you recall why they were converted? I can also go digging in Jira/Mail archives. On 1/12/20 9:11 PM, la...@apache.org wrote: Heh. They

Re: Moving Phoenix master to Hbase 2.2

Thanks for sending out the reminder, Istvan! Those interested: please take a look ASAP or give a shout for more time to review. On it's current trajectory, I think the PR will be in a place to merge tomorrow (2020/02/05, US times). On 1/30/20 2:49 PM, Istvan Toth wrote: I have received a ton

Reminder: update reporter.a.o after a release

If you are the release manager for Phoenix, make sure you are adding the new release here as a final step: https://reporter.apache.org/addrelease.html?phoenix This is important in that it gives folks (e.g. ASF members and ASF board members) insight into the releases we're doing. It looks like

[DISCUSS] Feb 2020 board report

Yo, It's that time which is so nice, it comes four times a year: board report time! Things that are jumping out at me: * Omid & Tephra "adoption" * 4.15.0 released * HBase2 compat stuff landed to unblock next 5.x release Please tell me what else you think is worth mentioning. If you forgot

Re: [DISCUSS] Unifying the 4.x branches

Sounds like a good idea to me. On 2/6/20 8:40 AM, Istvan Toth wrote: Hello! Now that we have a working solution in master for handling different HBase minor versions, I think that we should think about applying the same template to 4.x., and unifying the 4.x-HBase-1.3, 1.4, and 1.5 branches. A

Re: [ANNOUNCE] New Phoenix committer Gokcen Iskender

Congratulations and welcome, Gokcen! On 2/10/20 1:55 PM, Geoffrey Jacoby wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Gokcen Iskender has accepted our invitation to become a committer on the Phoenix project. Gokcen has contributed many features and bug fixes as part o

Re: [DISCUSS] Feb 2020 board report

drop year-over-year but the dev and issues list have an increase of a similar percentage magnitude year-over-year. In general, I observe a steady stream of user questions and developers created and resolving Jira issues. On 2/6/20 8:11 PM, Josh Elser wrote: Yo, It's that time which is so

<    1   2   3   4   5   6   7   8   9   10   >