You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by Kevin Verhoeven <Ke...@ds-iq.com> on 2015/10/07 17:55:52 UTC
RE: setting up community repo of Phoenix for CDH5?
JM,
If possible, I’d also like to try your 4.5.2 Parcel. Any luck with Cloudera? This would be very useful if made available. Thanks for your time!
Kevin
From: James Heather [mailto:james.heather@mendeley.com]
Sent: Wednesday, September 30, 2015 5:22 AM
To: user@phoenix.apache.org
Subject: Re: setting up community repo of Phoenix for CDH5?
Hi JM,
Is there a way of getting hold of the parcel you built? I'm keen to try it!
Best wishes,
James
On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
Hi James,
I have been able to build a parcel and installed it on my own cluster. Build it with 4.5.2 that Andrew modified. I'm in touch with Cloudera to see what's the next steps. I will let you know very shortly...
JM
2015-09-21 6:25 GMT-04:00 James Heather <ja...@mendeley.com>>:
@JM how did you get on with the parcel building?
Has anyone managed to get 4.5 working on CDH5 now? I was going to stick with 4.3 on our cluster until we had a parcel, but I'm now needing to use pherf, and that doesn't seem to exist in 4.3.
James
On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
@James: I'm working on the parcel building ;) If not me I will try to find someone to do it. Stay tuned.
@Andrewy: It works for me that way, cool! I just have a signature issue where it says I have no signature. Will that be an issue?
Thanks all,
JM
2015-09-16 3:24 GMT-04:00 James Heather <ja...@mendeley.com>>:
Great! Thank you!
I'd wondered about parcel building. It did look as though a parcel is just a .tgz, containing the classes and a few bits of meta, so hopefully it's doable. It would be really nice if we could provide a working 4.5 parcel.
James
On 16 Sep 2015 01:02, "Andrew Purtell" <ap...@apache.org>> wrote:
I used dev/make_rc.sh, built with Maven 3.2.2, Java 7u79. Ubuntu build host.
On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc Spaggiari <je...@spaggiari.org>> wrote:
No, I don't know why. I will ask and see if I can get a respons on that. I have also started the thread for the Parcel. I will see if I find enough help to work on that.
Regarding the branch you made, I tried to build it but got the error below. what's the command to build it?
Thanks,
JM
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 17 seconds
[INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015
[INFO] Final Memory: 134M/1648M
[INFO] ------------------------------------------------------------------------
2015-09-15 19:55 GMT-04:00 Andrew Purtell <ap...@apache.org>>:
Cool, thanks J-M.
Do you know why support for query tracing was removed? If it's just a matter of porting it to the HTrace that ships with CDH, I can look at that.
On Tue, Sep 15, 2015 at 4:49 PM, Jean-Marc Spaggiari <je...@spaggiari.org>> wrote:
Nice! I will see if there is a way to build a parcel from that the same way there is a parcel for Apache Phoenix 4.3 in Cloudera Labs... Will clone what you did and try to build it locally...
2015-09-15 19:45 GMT-04:00 Andrew Purtell <an...@gmail.com>>:
I pushed updates to branch 4.5-HBase-1.0-cdh5 and the tag v4.5.2-cdh5.4.5 (1fcb5cf). This is the pending Phoenix 4.5.2 release, currently at RC1, likely to pass, that will build against CDH 5.4.5. If you want release tarballs I built from this, get them here:
Binary: http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
Source: http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
The source and these binaries incorporate changes from the Cloudera Labs fork of Phoenix (https://github.com/cloudera-labs/phoenix), licensed under the ASL v2, Neither the source or binary artifacts are in any way "official" or supported by the Apache Phoenix project. The source and artifacts are provided by me in a personal capacity for the convenience of would-be Phoenix users that also use CDH 5.4(.5). Please don't contact the Apache Phoenix project for any issues regarding this source and these binaries.
On Mon, Sep 14, 2015 at 10:52 AM, James Heather <ja...@mendeley.com>> wrote:
Done! Thanks for helping!
The branches in the repo mirror those in vanilla Phoenix. We shouldn't push any changes to the vanilla branches, but only to "*-cdh5" branches (or any temporary side branches we need to create).
The issue tracker will be very useful, yes.
James
On 14/09/15 17:22, Andrew Purtell wrote:
This is great James.
Since this is conveniently on Github, maybe we use the issue tracker there? Interested parties can set a watch. Would you be willing to add 'apurtell' as a collaborator on the repo? I will fork and send over PRs of course, but you might want help?
On Sep 14, 2015, at 6:21 AM, James Heather <ja...@mendeley.com>> wrote:
I've set up a repo at
https://github.com/chiastic-security/phoenix-for-cloudera
It is a fork of the vanilla Phoenix github mirror. I've created a branch called "4.5-HBase-1.0-cdh5", which we can use for making a CDH5-compatible version. I've not made any of the necessary changes so far.
I chose that branch, by the way, because it's the latest release, and is using the same version of HBase as CDH5.4. The master branch of the Phoenix repo is building a snapshot of (the forthcoming) Phoenix 4.6, against HBase 1.1... presumably there will also be a Phoenix 4.6 for HBase 1.0?
I'm not certain of the best way to manage this. Perhaps we need a new mailing list for those who want to help, to avoid cluttering this list up.
James
On 13/09/15 02:54, Jean-Marc Spaggiari wrote:
Exact. There is some some code change because of what has been back ported into CDH and what has not been. But overall, it should not be rocket science. Mostly method signatures...
Let us know when the repo is available so we can help...
Thanks,
JM
2015-09-12 18:38 GMT-04:00 Krishna <re...@gmail.com>>:
As explained here, there are some code changes too in addition to pom related changes.
http://stackoverflow.com/a/31934434/165130
On Friday, September 11, 2015, Andrew Purtell <an...@gmail.com>> wrote:
Or once parameterized, add a default off profile that redefines them all in one shot after the builder activates the profile on the maven command line with -P ...
On Sep 11, 2015, at 7:05 AM, Andrew Purtell <an...@gmail.com>> wrote:
The group IDs and versions can be parameterized in the POM so they can be overridden on the maven command line with -D. That would be easy and something I think we could get committed without any controversy.
On Sep 11, 2015, at 6:53 AM, James Heather <ja...@mendeley.com>> wrote:
Yes, my plan is to create a fork of the main repo, so that we can still merge new Phoenix code into the CDH-compatible version.
Before that, I do wonder whether it's possible to suggest a few changes to the main repo that would allow for compiling a CDH-compatible version, without needing to maintain a separate repo. The bulk of the changes are to dependencies in the pom, which suggests that it could be done to accept a switch to mvn build.
James
On 11/09/15 14:50, Andrew Purtell wrote:
The first step I think is a repo with code that compiles. Please initialize it by forking github.com/apache/phoenix<http://github.com/apache/phoenix> so we have common ancestors. Once we have a clear idea (by diff) what is required we can figure out if we can support compatibility in some way.
On Sep 9, 2015, at 11:00 PM, Krishna <re...@gmail.com>> wrote:
I can volunteer to spend some time on this.
CDH artifacts are available in Maven repo but from reading other threads on CDH-Phoenix compatibilty, it looks like there are some code changes to be made in Phoenix to successfully compile against CDH.
Here are questions to address:
1) How to maintain CDH compatible Phoenix code base?
2) Is having a CDH compatible branch even an option?
Krishna
On Friday, August 28, 2015, Andrew Purtell <an...@gmail.com>> wrote:
Yes I am interested. Assuming CDH artifacts are publicly available in a Maven repo somewhere, which I believe is the case, perhaps we (the Phoenix project/community) could set up a Jenkins job that builds against them and makes the resulting build artifacts available. They would never be an official release, just a best effort convenience. Would that work? I think little must be done besides compile against the CDH artifacts for binary compatibility.
> On Aug 28, 2015, at 11:19 AM, James Heather <ja...@mendeley.com>> wrote:
>
> Is anyone interested in helping with getting an up-to-date CDH5-compatible build of Phoenix up and running?
>
> Cloudera has a build of Phoenix 4.3 (https://github.com/cloudera-labs/phoenix), but this is now two versions behind, and there seems little desire at Cloudera to keep it updated.
>
> I imagine that by looking at the differences between vanilla 4.3 and cloudera labs 4.3, and with some guidance from this list, we could get a good idea of what would need to be modified in 4.5+ and keep a CDH5-compatible build up to date.
>
> Yes?
>
> James
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Drop in throughput
Posted by James Taylor <ja...@apache.org>.
Sumanta,
Hard to say what the cause is for the drop in throughput without more
information. It's not uncommon that a mixed workload is going to have some
impact in throughput, though. For example, HBase will be doing splits and
compactions which will impact scan performance. Also, you'll have multiple
HFiles that will need to be merged at read time as opposed to having a
single HFile. Have you profiled the system to see if anything stands out?
For the line you're seeing in your logs, there's another JIRA
(PHOENIX-1270) which I plan to implement that will prevent the pinging of
the server that checks whether a schema is up-to-date. The trade off will
be that schema changes to a table will not be seen until a cluster bounce.
Thanks,
James
On Tue, Oct 13, 2015 at 11:28 AM, Thomas D'Silva <td...@salesforce.com>
wrote:
> Sumanta,
>
> Phoenix resolves the table for every SELECT. For UPSERT it resolves
> the table once at commit time.
> We have a JIRA in the txn branch where if you specify an SCN it will
> cache the table and look it up from the cache
> https://issues.apache.org/jira/browse/PHOENIX-1812
> This will be available once we merge the txn branch back.
>
> Thanks,
> Thomas
>
> On Tue, Oct 13, 2015 at 12:00 AM, Sumanta Gh <su...@tcs.com> wrote:
> > Hi,
> > I was experimenting the reasons why there is significant drop in
> through-put
> > when I give mixed workload of 70% Upsert + 30% Selects over 100% Upserts
> or
> > 100% Selects.
> >
> > While doing that I find that the following line is getting printed every
> > time in my log :-
> >
> > "Re-resolved stale table MY_TABLE with seqNum 0 at timestamp
> 1443618964162
> > with 22 columns: [...]"
> >
> > Can it be avoided for each SQL query.
> >
> > regards,
> > Sumanta
> >
> > =====-----=====-----=====
> > Notice: The information contained in this e-mail
> > message and/or attachments to it may contain
> > confidential or privileged information. If you are
> > not the intended recipient, any dissemination, use,
> > review, distribution, printing or copying of the
> > information contained in this e-mail message
> > and/or attachments to it are strictly prohibited. If
> > you have received this communication in error,
> > please notify us by reply e-mail or telephone and
> > immediately and permanently delete the message
> > and any attachments. Thank you
>
Re: Drop in throughput
Posted by Thomas D'Silva <td...@salesforce.com>.
Sumanta,
Phoenix resolves the table for every SELECT. For UPSERT it resolves
the table once at commit time.
We have a JIRA in the txn branch where if you specify an SCN it will
cache the table and look it up from the cache
https://issues.apache.org/jira/browse/PHOENIX-1812
This will be available once we merge the txn branch back.
Thanks,
Thomas
On Tue, Oct 13, 2015 at 12:00 AM, Sumanta Gh <su...@tcs.com> wrote:
> Hi,
> I was experimenting the reasons why there is significant drop in through-put
> when I give mixed workload of 70% Upsert + 30% Selects over 100% Upserts or
> 100% Selects.
>
> While doing that I find that the following line is getting printed every
> time in my log :-
>
> "Re-resolved stale table MY_TABLE with seqNum 0 at timestamp 1443618964162
> with 22 columns: [...]"
>
> Can it be avoided for each SQL query.
>
> regards,
> Sumanta
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
Drop in throughput
Posted by Sumanta Gh <su...@tcs.com>.
Hi,
I was experimenting the reasons why there is significant drop in through-put when I give mixed workload of 70% Upsert + 30% Selects over 100% Upserts or 100% Selects.
While doing that I find that the following line is getting printed every time in my log :-
"Re-resolved stale table MY_TABLE with seqNum 0 at timestamp 1443618964162 with 22 columns: [...]"
Can it be avoided for each SQL query.
regards,
Sumanta
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
Re: setting up community repo of Phoenix for CDH5?
Posted by Dhruv Gohil <yo...@gmail.com>.
Hi JM,
Yes James is right, We are looking at 'parcel' building scripts.
Don't worry about 'reproducibility' at our end, we also like to get
our hands dirty to make something work at first!
Notes at back of tissue paper also works ;-) , we can iron out and
push to repo (at-least for centOS 6.x)
On Monday 12 October 2015 11:01 PM, Jean-Marc Spaggiari wrote:
> Hum. Unfortunatly it's not really a script but more manual work and
> Jenkins :( Not sure what I can share which might help to build that
> back :(
>
>
>
>
> -------- Forwarded Message --------
> Subject: Re: setting up community repo of Phoenix for CDH5?
> Date: Mon, 12 Oct 2015 16:14:08 +0100
> From: James Heather <ja...@mendeley.com>
> Reply-To: user@phoenix.apache.org
> To: user@phoenix.apache.org
>
>
>
> I imagine Dhruv meant the script or whatever you used to build the
> parcel. Is that available? Could we put it into the repo so that we
> can build parcels as and when we need them? That would be great.
>
> James
>
> On 12/10/15 15:49, Jean-Marc Spaggiari wrote:
>> Hi Dhruv,
>>
>> The sources are exactly what Andrew has pushed into the GitHub. I
>> have not done any modification to the code. Have you tried to clone
>> and build what he sent?
>>
>> JM
>>
>> 2015-10-12 7:14 GMT-04:00 Dhruv Gohil <yourfrienddhruv@gmail.com
>> <ma...@gmail.com>>:
>>
>> Hi JM,
>> Can you please share the source code of how to build 'the
>> parcel' ?
>> We want to package our owned patched phoenix as parcel for
>> different CDH version.
>> Will love to share custom CDH parcels like we already do for
>> HDP
>> (http://hortonworks-gallery.github.io/index.html?sort=asc&filter=ambari%20extensions)
>>
>> Thanks for the awesome work!
>>
>> Also,
>> Has anybody had success with this parcel? (we don't yet have
>> compatible CDH cluster yet, so waiting for any one guy's go ahead
>> to do so) ;-)
>>
>>
>> On Thursday 08 October 2015 10:37 PM, Jean-Marc Spaggiari wrote:
>>> Can you try this repo for your installation?
>>>
>>> http://server.distparser.com:81/parcels/
>>>
>>> Don't look at the name of the files... Even if it says 4.3.0
>>> it's 4.5.2 inside. Install is and launch the Phoenix command
>>> line to validate it.
>>>
>>> Please be aware that it's not at all supported by cloudera in
>>> anyway, not approved by them nor provided by them nor anything
>>> else by them ;)
>>>
>>> Those parcels work for me. I'm sure they will for you too.
>>> Please keep me posted.
>>>
>>> JM
>>>
>>> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven
>>> <Ke...@ds-iq.com>:
>>>
>>> JM,
>>>
>>> If possible, I’d also like to try your 4.5.2 Parcel. Any
>>> luck with Cloudera? This would be very useful if made
>>> available. Thanks for your time!
>>>
>>> Kevin
>>>
>>> *From:*James Heather [mailto:james.heather@mendeley.com]
>>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>>> *To:* user@phoenix.apache.org
>>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>>
>>> Hi JM,
>>>
>>> Is there a way of getting hold of the parcel you built? I'm
>>> keen to try it!
>>>
>>> Best wishes,
>>>
>>> James
>>>
>>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>>
>>> Hi James,
>>>
>>> I have been able to build a parcel and installed it on
>>> my own cluster. Build it with 4.5.2 that Andrew
>>> modified. I'm in touch with Cloudera to see what's the
>>> next steps. I will let you know very shortly...
>>>
>>> JM
>>>
>>> 2015-09-21 6:25 GMT-04:00 James Heather
>>> <james.heather@mendeley.com
>>> <ma...@mendeley.com>>:
>>>
>>> @JM how did you get on with the parcel building?
>>>
>>> Has anyone managed to get 4.5 working on CDH5 now? I
>>> was going to stick with 4.3 on our cluster until we
>>> had a parcel, but I'm now needing to use pherf, and
>>> that doesn't seem to exist in 4.3.
>>>
>>> James
>>>
>>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>>
>>> @James: I'm working on the parcel building ;) If
>>> not me I will try to find someone to do it. Stay
>>> tuned.
>>>
>>> @Andrewy: It works for me that way, cool! I just
>>> have a signature issue where it says I have no
>>> signature. Will that be an issue?
>>>
>>> Thanks all,
>>>
>>> JM
>>>
>>> 2015-09-16 3:24 GMT-04:00 James Heather
>>> <ja...@mendeley.com>:
>>>
>>> Great! Thank you!
>>>
>>> I'd wondered about parcel building. It did
>>> look as though a parcel is just a .tgz,
>>> containing the classes and a few bits of
>>> meta, so hopefully it's doable. It would be
>>> really nice if we could provide a working
>>> 4.5 parcel.
>>>
>>> James
>>>
>>> On 16 Sep 2015 01:02, "Andrew Purtell"
>>> <ap...@apache.org> wrote:
>>>
>>> I used dev/make_rc.sh, built with Maven
>>> 3.2.2, Java 7u79. Ubuntu build host.
>>>
>>> On Tue, Sep 15, 2015 at 4:58 PM,
>>> Jean-Marc Spaggiari
>>> <je...@spaggiari.org> wrote:
>>>
>>> No, I don't know why. I will ask and
>>> see if I can get a respons on that.
>>> I have also started the thread for
>>> the Parcel. I will see if I find
>>> enough help to work on that.
>>>
>>> Regarding the branch you made, I
>>> tried to build it but got the error
>>> below. what's the command to build it?
>>>
>>> Thanks,
>>>
>>> JM
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] FATAL ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] null
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> java.lang.NullPointerException
>>> at
>>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>>> at
>>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>>> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> at
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at
>>> java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> at
>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> at
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> at
>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 2 minutes 17 seconds
>>> [INFO] Finished at: Tue Sep 15
>>> 19:55:03 EDT 2015
>>> [INFO] Final Memory: 134M/1648M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> 2015-09-15 19:55 GMT-04:00 Andrew
>>> Purtell <ap...@apache.org>:
>>>
>>> Cool, thanks J-M.
>>>
>>> Do you know why support for
>>> query tracing was removed? If
>>> it's just a matter of porting it
>>> to the HTrace that ships with
>>> CDH, I can look at that.
>>>
>>> On Tue, Sep 15, 2015 at 4:49 PM,
>>> Jean-Marc Spaggiari
>>> <je...@spaggiari.org> wrote:
>>>
>>> Nice! I will see if there is
>>> a way to build a parcel from
>>> that the same way there is a
>>> parcel for Apache Phoenix
>>> 4.3 in Cloudera Labs... Will
>>> clone what you did and try
>>> to build it locally...
>>>
>>> 2015-09-15 19:45 GMT-04:00
>>> Andrew Purtell
>>> <an...@gmail.com>:
>>>
>>> I pushed updates to
>>> branch
>>> 4.5-HBase-1.0-cdh5 and
>>> the tag v4.5.2-cdh5.4.5
>>> (1fcb5cf). This is the
>>> pending Phoenix 4.5.2
>>> release, currently at
>>> RC1, likely to pass,
>>> that will build against
>>> CDH 5.4.5. If you want
>>> release tarballs I built
>>> from this, get them here:
>>>
>>> Binary:
>>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>>
>>> Source:
>>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>>
>>>
>>> The source and these
>>> binaries incorporate
>>> changes from the
>>> Cloudera Labs fork of
>>> Phoenix
>>> (https://github.com/cloudera-labs/phoenix),
>>> licensed under the ASL
>>> v2, Neither the source
>>> or binary artifacts are
>>> in any way "official" or
>>> supported by the Apache
>>> Phoenix project. The
>>> source and artifacts are
>>> provided by me in a
>>> personal capacity for
>>> the convenience of
>>> would-be Phoenix users
>>> that also use CDH
>>> 5.4(.5). Please don't
>>> contact the Apache
>>> Phoenix project for any
>>> issues regarding this
>>> source and these binaries.
>>>
>>>
>>>
>>> On Mon, Sep 14, 2015 at
>>> 10:52 AM, James Heather
>>> <ja...@mendeley.com>
>>> wrote:
>>>
>>> Done! Thanks for
>>> helping!
>>>
>>> The branches in the
>>> repo mirror those in
>>> vanilla Phoenix. We
>>> shouldn't push any
>>> changes to the
>>> vanilla branches,
>>> but only to "*-cdh5"
>>> branches (or any
>>> temporary side
>>> branches we need to
>>> create).
>>>
>>> The issue tracker
>>> will be very useful,
>>> yes.
>>>
>>> James
>>>
>>> On 14/09/15 17:22,
>>> Andrew Purtell wrote:
>>>
>>> This is great
>>> James.
>>>
>>> Since this is
>>> conveniently on
>>> Github, maybe we
>>> use the issue
>>> tracker there?
>>> Interested
>>> parties can set
>>> a watch. Would
>>> you be willing
>>> to add
>>> 'apurtell' as a
>>> collaborator on
>>> the repo? I will
>>> fork and send
>>> over PRs of
>>> course, but you
>>> might want help?
>>>
>>>
>>> On Sep 14, 2015,
>>> at 6:21 AM,
>>> James Heather
>>> <ja...@mendeley.com>
>>> wrote:
>>>
>>> I've set up
>>> a repo at
>>>
>>> https://github.com/chiastic-security/phoenix-for-cloudera
>>>
>>> It is a fork
>>> of the
>>> vanilla
>>> Phoenix
>>> github
>>> mirror. I've
>>> created a
>>> branch
>>> called
>>> "4.5-HBase-1.0-cdh5",
>>> which we can
>>> use for
>>> making a
>>> CDH5-compatible
>>> version.
>>> I've not
>>> made any of
>>> the
>>> necessary
>>> changes so far.
>>>
>>> I chose that
>>> branch, by
>>> the way,
>>> because it's
>>> the latest
>>> release, and
>>> is using the
>>> same version
>>> of HBase as
>>> CDH5.4. The
>>> master
>>> branch of
>>> the Phoenix
>>> repo is
>>> building a
>>> snapshot of
>>> (the
>>> forthcoming)
>>> Phoenix 4.6,
>>> against
>>> HBase 1.1...
>>> presumably
>>> there will
>>> also be a
>>> Phoenix 4.6
>>> for HBase 1.0?
>>>
>>> I'm not
>>> certain of
>>> the best way
>>> to manage
>>> this.
>>> Perhaps we
>>> need a new
>>> mailing list
>>> for those
>>> who want to
>>> help, to
>>> avoid
>>> cluttering
>>> this list up.
>>>
>>> James
>>>
>>> On 13/09/15
>>> 02:54,
>>> Jean-Marc
>>> Spaggiari wrote:
>>>
>>> Exact.
>>> There is
>>> some
>>> some
>>> code
>>> change
>>> because
>>> of what
>>> has been
>>> back
>>> ported
>>> into CDH
>>> and what
>>> has not
>>> been.
>>> But
>>> overall,
>>> it
>>> should
>>> not be
>>> rocket
>>> science.
>>> Mostly
>>> method
>>> signatures...
>>>
>>> Let us
>>> know
>>> when the
>>> repo is
>>> available so
>>> we can
>>> help...
>>>
>>> Thanks,
>>>
>>> JM
>>>
>>> 2015-09-12
>>> 18:38
>>> GMT-04:00 Krishna
>>> <re...@gmail.com>:
>>>
>>> As
>>> explained
>>> here, there
>>> are
>>> some
>>> code
>>> changes
>>> too
>>> in
>>> addition
>>> to
>>> pom
>>> related
>>> changes.
>>>
>>>
>>> http://stackoverflow.com/a/31934434/165130
>>>
>>>
>>>
>>> On
>>> Friday,
>>> September
>>> 11,
>>> 2015, Andrew
>>> Purtell
>>> <an...@gmail.com>
>>> wrote:
>>>
>>> Or
>>> once
>>> parameterized,
>>> add
>>> a default
>>> off
>>> profile
>>> that
>>> redefines
>>> them
>>> all
>>> in
>>> one
>>> shot
>>> after
>>> the
>>> builder
>>> activates
>>> the
>>> profile
>>> on
>>> the
>>> maven
>>> command
>>> line
>>> with
>>> -P
>>> ...
>>>
>>>
>>> On
>>> Sep
>>> 11,
>>> 2015,
>>> at
>>> 7:05
>>> AM,
>>> Andrew
>>> Purtell
>>> <an...@gmail.com>
>>> wrote:
>>>
>>> The
>>> group
>>> IDs
>>> and
>>> versions
>>> can
>>> be
>>> parameterized
>>> in
>>> the
>>> POM
>>> so
>>> they
>>> can
>>> be
>>> overridden
>>> on
>>> the
>>> maven
>>> command
>>> line
>>> with
>>> -D.
>>> That
>>> would
>>> be
>>> easy
>>> and
>>> something
>>> I think
>>> we
>>> could
>>> get
>>> committed
>>> without
>>> any
>>> controversy.
>>>
>>>
>>>
>>> On
>>> Sep
>>> 11,
>>> 2015,
>>> at
>>> 6:53
>>> AM,
>>> James
>>> Heather
>>> <ja...@mendeley.com>
>>> wrote:
>>>
>>> Yes,
>>> my
>>> plan
>>> is
>>> to
>>> create
>>> a fork
>>> of
>>> the
>>> main
>>> repo,
>>> so
>>> that
>>> we
>>> can
>>> still
>>> merge
>>> new
>>> Phoenix
>>> code
>>> into
>>> the
>>> CDH-compatible
>>> version.
>>>
>>> Before
>>> that,
>>> I do
>>> wonder
>>> whether
>>> it's
>>> possible
>>> to
>>> suggest
>>> a few
>>> changes
>>> to
>>> the
>>> main
>>> repo
>>> that
>>> would
>>> allow
>>> for
>>> compiling
>>> a CDH-compatible
>>> version,
>>> without
>>> needing
>>> to
>>> maintain
>>> a separate
>>> repo.
>>> The
>>> bulk
>>> of
>>> the
>>> changes
>>> are
>>> to
>>> dependencies
>>> in
>>> the
>>> pom,
>>> which
>>> suggests
>>> that
>>> it
>>> could
>>> be
>>> done
>>> to
>>> accept
>>> a switch
>>> to
>>> mvn
>>> build.
>>>
>>> James
>>>
>>> On
>>> 11/09/15
>>> 14:50,
>>> Andrew
>>> Purtell
>>> wrote:
>>>
>>> The
>>> first
>>> step
>>> I think
>>> is
>>> a repo
>>> with
>>> code
>>> that
>>> compiles.
>>> Please
>>> initialize
>>> it
>>> by
>>> forking
>>> github.com/apache/phoenix
>>> <http://github.com/apache/phoenix>
>>> so
>>> we
>>> have
>>> common
>>> ancestors.
>>> Once
>>> we
>>> have
>>> a clear
>>> idea
>>> (by
>>> diff)
>>> what
>>> is
>>> required
>>> we
>>> can
>>> figure
>>> out
>>> if
>>> we
>>> can
>>> support
>>> compatibility
>>> in
>>> some
>>> way.
>>>
>>>
>>> On
>>> Sep
>>> 9,
>>> 2015,
>>> at
>>> 11:00
>>> PM,
>>> Krishna
>>> <re...@gmail.com>
>>> wrote:
>>>
>>> I can
>>> volunteer
>>> to
>>> spend
>>> some
>>> time
>>> on
>>> this.
>>>
>>>
>>> CDH
>>> artifacts
>>> are
>>> available
>>> in
>>> Maven
>>> repo
>>> but
>>> from reading
>>> other
>>> threads
>>> on
>>> CDH-Phoenix
>>> compatibilty,
>>> it
>>> looks
>>> like
>>> there
>>> are
>>> some
>>> code
>>> changes
>>> to
>>> be
>>> made
>>> in
>>> Phoenix
>>> to
>>> successfully compile
>>> against
>>> CDH.
>>>
>>>
>>> Here
>>> are
>>> questions
>>> to
>>> address:
>>>
>>> 1)
>>> How
>>> to
>>> maintain
>>> CDH
>>> compatible
>>> Phoenix
>>> code
>>> base?
>>>
>>>
>>> 2)
>>> Is
>>> having
>>> a CDH
>>> compatible
>>> branch
>>> even
>>> an
>>> option?
>>>
>>>
>>> Krishna
>>>
>>>
>>>
>>> On
>>> Friday,
>>> August
>>> 28,
>>> 2015,
>>> Andrew
>>> Purtell
>>> <an...@gmail.com>
>>> wrote:
>>>
>>> Yes
>>> I am
>>> interested.
>>> Assuming
>>> CDH
>>> artifacts
>>> are
>>> publicly
>>> available
>>> in
>>> a Maven
>>> repo
>>> somewhere,
>>> which
>>> I believe
>>> is
>>> the
>>> case,
>>> perhaps
>>> we
>>> (the
>>> Phoenix
>>> project/community)
>>> could
>>> set
>>> up
>>> a Jenkins
>>> job
>>> that
>>> builds
>>> against
>>> them
>>> and
>>> makes
>>> the
>>> resulting
>>> build
>>> artifacts
>>> available.
>>> They
>>> would
>>> never
>>> be
>>> an
>>> official
>>> release,
>>> just
>>> a best
>>> effort
>>> convenience.
>>> Would
>>> that
>>> work?
>>> I think
>>> little
>>> must
>>> be
>>> done
>>> besides
>>> compile
>>> against
>>> the
>>> CDH
>>> artifacts
>>> for
>>> binary
>>> compatibility.
>>>
>>>
>>> > On
>>> Aug
>>> 28,
>>> 2015,
>>> at
>>> 11:19
>>> AM,
>>> James
>>> Heather
>>> <ja...@mendeley.com>
>>> wrote:
>>> >
>>> > Is
>>> anyone
>>> interested
>>> in
>>> helping
>>> with
>>> getting
>>> an
>>> up-to-date
>>> CDH5-compatible
>>> build
>>> of
>>> Phoenix
>>> up
>>> and
>>> running?
>>> >
>>> > Cloudera
>>> has
>>> a build
>>> of
>>> Phoenix
>>> 4.3
>>> (https://github.com/cloudera-labs/phoenix),
>>> but
>>> this
>>> is
>>> now
>>> two
>>> versions
>>> behind,
>>> and
>>> there
>>> seems
>>> little
>>> desire
>>> at
>>> Cloudera
>>> to
>>> keep
>>> it
>>> updated.
>>> >
>>> > I
>>> imagine
>>> that
>>> by
>>> looking
>>> at
>>> the
>>> differences
>>> between
>>> vanilla
>>> 4.3
>>> and
>>> cloudera
>>> labs
>>> 4.3,
>>> and
>>> with
>>> some
>>> guidance
>>> from
>>> this
>>> list,
>>> we
>>> could
>>> get
>>> a good
>>> idea
>>> of
>>> what
>>> would
>>> need
>>> to
>>> be
>>> modified
>>> in
>>> 4.5+
>>> and
>>> keep
>>> a CDH5-compatible
>>> build
>>> up
>>> to
>>> date.
>>> >
>>> > Yes?
>>> >
>>> > James
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>>
>>> - Andy
>>>
>>> Problems worthy of attack prove
>>> their worth by hitting back. -
>>> Piet Hein (via Tom White)
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>>
>>> - Andy
>>>
>>> Problems worthy of attack prove their
>>> worth by hitting back. - Piet Hein (via
>>> Tom White)
>>>
>>>
>>
>>
>
>
>
Re: setting up community repo of Phoenix for CDH5?
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Hum. Unfortunatly it's not really a script but more manual work and Jenkins
:( Not sure what I can share which might help to build that back :(
Re: setting up community repo of Phoenix for CDH5?
Posted by James Heather <ja...@mendeley.com>.
I imagine Dhruv meant the script or whatever you used to build the
parcel. Is that available? Could we put it into the repo so that we can
build parcels as and when we need them? That would be great.
James
On 12/10/15 15:49, Jean-Marc Spaggiari wrote:
> Hi Dhruv,
>
> The sources are exactly what Andrew has pushed into the GitHub. I have
> not done any modification to the code. Have you tried to clone and
> build what he sent?
>
> JM
>
> 2015-10-12 7:14 GMT-04:00 Dhruv Gohil <yourfrienddhruv@gmail.com
> <ma...@gmail.com>>:
>
> Hi JM,
> Can you please share the source code of how to build 'the
> parcel' ?
> We want to package our owned patched phoenix as parcel for
> different CDH version.
> Will love to share custom CDH parcels like we already do for
> HDP
> (http://hortonworks-gallery.github.io/index.html?sort=asc&filter=ambari%20extensions)
>
> Thanks for the awesome work!
>
> Also,
> Has anybody had success with this parcel? (we don't yet have
> compatible CDH cluster yet, so waiting for any one guy's go ahead
> to do so) ;-)
>
>
> On Thursday 08 October 2015 10:37 PM, Jean-Marc Spaggiari wrote:
>> Can you try this repo for your installation?
>>
>> http://server.distparser.com:81/parcels/
>>
>> Don't look at the name of the files... Even if it says 4.3.0 it's
>> 4.5.2 inside. Install is and launch the Phoenix command line to
>> validate it.
>>
>> Please be aware that it's not at all supported by cloudera in
>> anyway, not approved by them nor provided by them nor anything
>> else by them ;)
>>
>> Those parcels work for me. I'm sure they will for you too. Please
>> keep me posted.
>>
>> JM
>>
>> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven
>> <Kevin.Verhoeven@ds-iq.com <ma...@ds-iq.com>>:
>>
>> JM,
>>
>> If possible, I’d also like to try your 4.5.2 Parcel. Any luck
>> with Cloudera? This would be very useful if made available.
>> Thanks for your time!
>>
>> Kevin
>>
>> *From:*James Heather [mailto:james.heather@mendeley.com
>> <ma...@mendeley.com>]
>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>> *To:* user@phoenix.apache.org <ma...@phoenix.apache.org>
>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>
>> Hi JM,
>>
>> Is there a way of getting hold of the parcel you built? I'm
>> keen to try it!
>>
>> Best wishes,
>>
>> James
>>
>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>
>> Hi James,
>>
>> I have been able to build a parcel and installed it on my
>> own cluster. Build it with 4.5.2 that Andrew modified.
>> I'm in touch with Cloudera to see what's the next steps.
>> I will let you know very shortly...
>>
>> JM
>>
>> 2015-09-21 6:25 GMT-04:00 James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>:
>>
>> @JM how did you get on with the parcel building?
>>
>> Has anyone managed to get 4.5 working on CDH5 now? I
>> was going to stick with 4.3 on our cluster until we
>> had a parcel, but I'm now needing to use pherf, and
>> that doesn't seem to exist in 4.3.
>>
>> James
>>
>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>
>> @James: I'm working on the parcel building ;) If
>> not me I will try to find someone to do it. Stay
>> tuned.
>>
>> @Andrewy: It works for me that way, cool! I just
>> have a signature issue where it says I have no
>> signature. Will that be an issue?
>>
>> Thanks all,
>>
>> JM
>>
>> 2015-09-16 3:24 GMT-04:00 James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>:
>>
>> Great! Thank you!
>>
>> I'd wondered about parcel building. It did
>> look as though a parcel is just a .tgz,
>> containing the classes and a few bits of
>> meta, so hopefully it's doable. It would be
>> really nice if we could provide a working 4.5
>> parcel.
>>
>> James
>>
>> On 16 Sep 2015 01:02, "Andrew Purtell"
>> <apurtell@apache.org
>> <ma...@apache.org>> wrote:
>>
>> I used dev/make_rc.sh, built with Maven
>> 3.2.2, Java 7u79. Ubuntu build host.
>>
>> On Tue, Sep 15, 2015 at 4:58 PM,
>> Jean-Marc Spaggiari
>> <jean-marc@spaggiari.org
>> <ma...@spaggiari.org>> wrote:
>>
>> No, I don't know why. I will ask and
>> see if I can get a respons on that. I
>> have also started the thread for the
>> Parcel. I will see if I find enough
>> help to work on that.
>>
>> Regarding the branch you made, I
>> tried to build it but got the error
>> below. what's the command to build it?
>>
>> Thanks,
>>
>> JM
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.NullPointerException
>> at
>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>> at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at
>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at
>> java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at
>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at
>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2 minutes 17 seconds
>> [INFO] Finished at: Tue Sep 15
>> 19:55:03 EDT 2015
>> [INFO] Final Memory: 134M/1648M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> 2015-09-15 19:55 GMT-04:00 Andrew
>> Purtell <apurtell@apache.org
>> <ma...@apache.org>>:
>>
>> Cool, thanks J-M.
>>
>> Do you know why support for query
>> tracing was removed? If it's just
>> a matter of porting it to the
>> HTrace that ships with CDH, I can
>> look at that.
>>
>> On Tue, Sep 15, 2015 at 4:49 PM,
>> Jean-Marc Spaggiari
>> <jean-marc@spaggiari.org
>> <ma...@spaggiari.org>>
>> wrote:
>>
>> Nice! I will see if there is
>> a way to build a parcel from
>> that the same way there is a
>> parcel for Apache Phoenix 4.3
>> in Cloudera Labs... Will
>> clone what you did and try to
>> build it locally...
>>
>> 2015-09-15 19:45 GMT-04:00
>> Andrew Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>:
>>
>> I pushed updates to
>> branch 4.5-HBase-1.0-cdh5
>> and the tag
>> v4.5.2-cdh5.4.5
>> (1fcb5cf). This is the
>> pending Phoenix 4.5.2
>> release, currently at
>> RC1, likely to pass, that
>> will build against CDH
>> 5.4.5. If you want
>> release tarballs I built
>> from this, get them here:
>>
>> Binary:
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>
>> Source:
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>
>>
>> The source and these
>> binaries incorporate
>> changes from the Cloudera
>> Labs fork of Phoenix
>> (https://github.com/cloudera-labs/phoenix),
>> licensed under the ASL
>> v2, Neither the source or
>> binary artifacts are in
>> any way "official" or
>> supported by the Apache
>> Phoenix project. The
>> source and artifacts are
>> provided by me in a
>> personal capacity for the
>> convenience of would-be
>> Phoenix users that also
>> use CDH 5.4(.5). Please
>> don't contact the Apache
>> Phoenix project for any
>> issues regarding this
>> source and these binaries.
>>
>>
>>
>> On Mon, Sep 14, 2015 at
>> 10:52 AM, James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> Done! Thanks for helping!
>>
>> The branches in the
>> repo mirror those in
>> vanilla Phoenix. We
>> shouldn't push any
>> changes to the
>> vanilla branches, but
>> only to "*-cdh5"
>> branches (or any
>> temporary side
>> branches we need to
>> create).
>>
>> The issue tracker
>> will be very useful, yes.
>>
>> James
>>
>> On 14/09/15 17:22,
>> Andrew Purtell wrote:
>>
>> This is great James.
>>
>> Since this is
>> conveniently on
>> Github, maybe we
>> use the issue
>> tracker there?
>> Interested
>> parties can set a
>> watch. Would you
>> be willing to add
>> 'apurtell' as a
>> collaborator on
>> the repo? I will
>> fork and send
>> over PRs of
>> course, but you
>> might want help?
>>
>>
>> On Sep 14, 2015,
>> at 6:21 AM, James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> I've set up a
>> repo at
>>
>> https://github.com/chiastic-security/phoenix-for-cloudera
>>
>> It is a fork
>> of the
>> vanilla
>> Phoenix
>> github
>> mirror. I've
>> created a
>> branch called
>> "4.5-HBase-1.0-cdh5",
>> which we can
>> use for
>> making a
>> CDH5-compatible
>> version. I've
>> not made any
>> of the
>> necessary
>> changes so far.
>>
>> I chose that
>> branch, by
>> the way,
>> because it's
>> the latest
>> release, and
>> is using the
>> same version
>> of HBase as
>> CDH5.4. The
>> master branch
>> of the
>> Phoenix repo
>> is building a
>> snapshot of
>> (the
>> forthcoming)
>> Phoenix 4.6,
>> against HBase
>> 1.1...
>> presumably
>> there will
>> also be a
>> Phoenix 4.6
>> for HBase 1.0?
>>
>> I'm not
>> certain of
>> the best way
>> to manage
>> this. Perhaps
>> we need a new
>> mailing list
>> for those who
>> want to help,
>> to avoid
>> cluttering
>> this list up.
>>
>> James
>>
>> On 13/09/15
>> 02:54,
>> Jean-Marc
>> Spaggiari wrote:
>>
>> Exact.
>> There is
>> some some
>> code
>> change
>> because
>> of what
>> has been
>> back
>> ported
>> into CDH
>> and what
>> has not
>> been. But
>> overall,
>> it should
>> not be
>> rocket
>> science.
>> Mostly
>> method
>> signatures...
>>
>> Let us
>> know when
>> the repo
>> is
>> available
>> so we can
>> help...
>>
>> Thanks,
>>
>> JM
>>
>> 2015-09-12 18:38
>> GMT-04:00
>> Krishna
>> <research800@gmail.com
>> <ma...@gmail.com>>:
>>
>> As
>> explained
>> here,
>> there
>> are
>> some
>> code
>> changes
>> too
>> in
>> addition
>> to
>> pom
>> related
>> changes.
>>
>> http://stackoverflow.com/a/31934434/165130
>>
>>
>>
>> On
>> Friday,
>> September
>> 11,
>> 2015,
>> Andrew Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> Or once
>> parameterized,
>> add
>> a
>> default
>> off
>> profile
>> that
>> redefines
>> them
>> all
>> in one
>> shot
>> after
>> the
>> builder
>> activates
>> the
>> profile
>> on the
>> maven
>> command
>> line
>> with
>> -P ...
>>
>>
>>
>> On Sep
>> 11,
>> 2015,
>> at 7:05
>> AM,
>> Andrew
>> Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> The
>> group
>> IDs
>> and
>> versions
>> can
>> be
>> parameterized
>> in
>> the
>> POM
>> so
>> they
>> can
>> be
>> overridden
>> on
>> the
>> maven
>> command
>> line
>> with
>> -D.
>> That
>> would
>> be
>> easy
>> and
>> something
>> I think
>> we
>> could
>> get
>> committed
>> without
>> any
>> controversy.
>>
>>
>>
>> On
>> Sep
>> 11,
>> 2015,
>> at
>> 6:53
>> AM,
>> James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> Yes,
>> my
>> plan
>> is
>> to
>> create
>> a fork
>> of
>> the
>> main
>> repo,
>> so
>> that
>> we
>> can
>> still
>> merge
>> new
>> Phoenix
>> code
>> into
>> the
>> CDH-compatible
>> version.
>>
>> Before
>> that,
>> I do
>> wonder
>> whether
>> it's
>> possible
>> to
>> suggest
>> a few
>> changes
>> to
>> the
>> main
>> repo
>> that
>> would
>> allow
>> for
>> compiling
>> a CDH-compatible
>> version,
>> without
>> needing
>> to
>> maintain
>> a separate
>> repo.
>> The
>> bulk
>> of
>> the
>> changes
>> are
>> to
>> dependencies
>> in
>> the
>> pom,
>> which
>> suggests
>> that
>> it
>> could
>> be
>> done
>> to
>> accept
>> a switch
>> to
>> mvn
>> build.
>>
>> James
>>
>> On
>> 11/09/15
>> 14:50,
>> Andrew
>> Purtell
>> wrote:
>>
>> The
>> first
>> step
>> I think
>> is
>> a repo
>> with
>> code
>> that
>> compiles.
>> Please
>> initialize
>> it
>> by
>> forking
>> github.com/apache/phoenix
>> <http://github.com/apache/phoenix>
>> so
>> we
>> have
>> common
>> ancestors.
>> Once
>> we
>> have
>> a clear
>> idea
>> (by
>> diff)
>> what
>> is
>> required
>> we
>> can
>> figure
>> out
>> if
>> we
>> can
>> support
>> compatibility
>> in
>> some
>> way.
>>
>>
>> On
>> Sep
>> 9,
>> 2015,
>> at
>> 11:00
>> PM,
>> Krishna
>> <research800@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> I can
>> volunteer
>> to
>> spend
>> some
>> time
>> on
>> this.
>>
>>
>> CDH
>> artifacts
>> are
>> available
>> in
>> Maven
>> repo
>> but
>> from reading
>> other
>> threads
>> on
>> CDH-Phoenix
>> compatibilty,
>> it
>> looks
>> like
>> there
>> are
>> some
>> code
>> changes
>> to
>> be
>> made
>> in
>> Phoenix
>> to
>> successfully compile
>> against
>> CDH.
>>
>>
>> Here
>> are
>> questions
>> to
>> address:
>>
>> 1)
>> How
>> to
>> maintain
>> CDH
>> compatible
>> Phoenix
>> code
>> base?
>>
>>
>> 2)
>> Is
>> having
>> a CDH
>> compatible
>> branch
>> even
>> an
>> option?
>>
>>
>> Krishna
>>
>>
>>
>> On
>> Friday,
>> August
>> 28,
>> 2015,
>> Andrew
>> Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> Yes
>> I am
>> interested.
>> Assuming
>> CDH
>> artifacts
>> are
>> publicly
>> available
>> in
>> a Maven
>> repo
>> somewhere,
>> which
>> I believe
>> is
>> the
>> case,
>> perhaps
>> we
>> (the
>> Phoenix
>> project/community)
>> could
>> set
>> up
>> a Jenkins
>> job
>> that
>> builds
>> against
>> them
>> and
>> makes
>> the
>> resulting
>> build
>> artifacts
>> available.
>> They
>> would
>> never
>> be
>> an
>> official
>> release,
>> just
>> a best
>> effort
>> convenience.
>> Would
>> that
>> work?
>> I think
>> little
>> must
>> be
>> done
>> besides
>> compile
>> against
>> the
>> CDH
>> artifacts
>> for
>> binary
>> compatibility.
>>
>>
>> > On
>> Aug
>> 28,
>> 2015,
>> at
>> 11:19
>> AM,
>> James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>> >
>> > Is
>> anyone
>> interested
>> in
>> helping
>> with
>> getting
>> an
>> up-to-date
>> CDH5-compatible
>> build
>> of
>> Phoenix
>> up
>> and
>> running?
>> >
>> > Cloudera
>> has
>> a build
>> of
>> Phoenix
>> 4.3
>> (https://github.com/cloudera-labs/phoenix),
>> but
>> this
>> is
>> now
>> two
>> versions
>> behind,
>> and
>> there
>> seems
>> little
>> desire
>> at
>> Cloudera
>> to
>> keep
>> it
>> updated.
>> >
>> > I
>> imagine
>> that
>> by
>> looking
>> at
>> the
>> differences
>> between
>> vanilla
>> 4.3
>> and
>> cloudera
>> labs
>> 4.3,
>> and
>> with
>> some
>> guidance
>> from
>> this
>> list,
>> we
>> could
>> get
>> a good
>> idea
>> of
>> what
>> would
>> need
>> to
>> be
>> modified
>> in
>> 4.5+
>> and
>> keep
>> a CDH5-compatible
>> build
>> up
>> to
>> date.
>> >
>> > Yes?
>> >
>> > James
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove
>> their worth by hitting back. -
>> Piet Hein (via Tom White)
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their
>> worth by hitting back. - Piet Hein (via
>> Tom White)
>>
>>
>
>
Re: setting up community repo of Phoenix for CDH5?
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Hi Dhruv,
The sources are exactly what Andrew has pushed into the GitHub. I have not
done any modification to the code. Have you tried to clone and build what
he sent?
JM
2015-10-12 7:14 GMT-04:00 Dhruv Gohil <yo...@gmail.com>:
> Hi JM,
> Can you please share the source code of how to build 'the parcel' ?
> We want to package our owned patched phoenix as parcel for different
> CDH version.
> Will love to share custom CDH parcels like we already do for HDP (
> http://hortonworks-gallery.github.io/index.html?sort=asc&filter=ambari%20extensions
> )
>
> Thanks for the awesome work!
>
> Also,
> Has anybody had success with this parcel? (we don't yet have
> compatible CDH cluster yet, so waiting for any one guy's go ahead to do so)
> ;-)
>
>
> On Thursday 08 October 2015 10:37 PM, Jean-Marc Spaggiari wrote:
>
> Can you try this repo for your installation?
>
> http://server.distparser.com:81/parcels/
>
> Don't look at the name of the files... Even if it says 4.3.0 it's 4.5.2
> inside. Install is and launch the Phoenix command line to validate it.
>
> Please be aware that it's not at all supported by cloudera in anyway, not
> approved by them nor provided by them nor anything else by them ;)
>
> Those parcels work for me. I'm sure they will for you too. Please keep me
> posted.
>
> JM
>
> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven <Ke...@ds-iq.com>:
>
>> JM,
>>
>>
>>
>> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
>> Cloudera? This would be very useful if made available. Thanks for your time!
>>
>>
>>
>> Kevin
>>
>>
>>
>> *From:* James Heather [mailto:james.heather@mendeley.com]
>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>> *To:* user@phoenix.apache.org
>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>
>>
>>
>> Hi JM,
>>
>> Is there a way of getting hold of the parcel you built? I'm keen to try
>> it!
>>
>> Best wishes,
>>
>> James
>>
>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>
>> Hi James,
>>
>> I have been able to build a parcel and installed it on my own cluster.
>> Build it with 4.5.2 that Andrew modified. I'm in touch with Cloudera to see
>> what's the next steps. I will let you know very shortly...
>>
>> JM
>>
>>
>>
>> 2015-09-21 6:25 GMT-04:00 James Heather <ja...@mendeley.com>:
>>
>> @JM how did you get on with the parcel building?
>>
>> Has anyone managed to get 4.5 working on CDH5 now? I was going to stick
>> with 4.3 on our cluster until we had a parcel, but I'm now needing to use
>> pherf, and that doesn't seem to exist in 4.3.
>>
>> James
>>
>>
>>
>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>
>> @James: I'm working on the parcel building ;) If not me I will try to
>> find someone to do it. Stay tuned.
>>
>> @Andrewy: It works for me that way, cool! I just have a signature issue
>> where it says I have no signature. Will that be an issue?
>>
>> Thanks all,
>>
>> JM
>>
>>
>>
>> 2015-09-16 3:24 GMT-04:00 James Heather <ja...@mendeley.com>:
>>
>> Great! Thank you!
>>
>> I'd wondered about parcel building. It did look as though a parcel is
>> just a .tgz, containing the classes and a few bits of meta, so hopefully
>> it's doable. It would be really nice if we could provide a working 4.5
>> parcel.
>>
>> James
>>
>> On 16 Sep 2015 01:02, "Andrew Purtell" < <ap...@apache.org>
>> apurtell@apache.org> wrote:
>>
>> I used dev/make_rc.sh, built with Maven 3.2.2, Java 7u79. Ubuntu build
>> host.
>>
>>
>>
>>
>>
>> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc Spaggiari <
>> <je...@spaggiari.org> wrote:
>>
>> No, I don't know why. I will ask and see if I can get a respons on that.
>> I have also started the thread for the Parcel. I will see if I find enough
>> help to work on that.
>>
>> Regarding the branch you made, I tried to build it but got the error
>> below. what's the command to build it?
>>
>> Thanks,
>>
>> JM
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.NullPointerException
>> at
>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>> at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2 minutes 17 seconds
>> [INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015
>> [INFO] Final Memory: 134M/1648M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>>
>> 2015-09-15 19:55 GMT-04:00 Andrew Purtell < <ap...@apache.org>
>> apurtell@apache.org>:
>>
>> Cool, thanks J-M.
>>
>>
>>
>> Do you know why support for query tracing was removed? If it's just a
>> matter of porting it to the HTrace that ships with CDH, I can look at that.
>>
>>
>>
>>
>>
>> On Tue, Sep 15, 2015 at 4:49 PM, Jean-Marc Spaggiari <
>> <je...@spaggiari.org> wrote:
>>
>> Nice! I will see if there is a way to build a parcel from that the same
>> way there is a parcel for Apache Phoenix 4.3 in Cloudera Labs... Will clone
>> what you did and try to build it locally...
>>
>>
>>
>> 2015-09-15 19:45 GMT-04:00 Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com>:
>>
>> I pushed updates to branch 4.5-HBase-1.0-cdh5 and the tag v4.5.2-cdh5.4.5
>> (1fcb5cf). This is the pending Phoenix 4.5.2 release, currently at RC1,
>> likely to pass, that will build against CDH 5.4.5. If you want release
>> tarballs I built from this, get them here:
>>
>> Binary:
>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz>
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>
>> Source:
>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz>
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>
>>
>>
>>
>> The source and these binaries incorporate changes from the Cloudera Labs
>> fork of Phoenix ( <https://github.com/cloudera-labs/phoenix>
>> https://github.com/cloudera-labs/phoenix), licensed under the ASL v2,
>> Neither the source or binary artifacts are in any way "official" or
>> supported by the Apache Phoenix project. The source and artifacts are
>> provided by me in a personal capacity for the convenience of would-be
>> Phoenix users that also use CDH 5.4(.5). Please don't contact the Apache
>> Phoenix project for any issues regarding this source and these binaries.
>>
>>
>>
>>
>>
>> On Mon, Sep 14, 2015 at 10:52 AM, James Heather <
>> <ja...@mendeley.com> wrote:
>>
>> Done! Thanks for helping!
>>
>> The branches in the repo mirror those in vanilla Phoenix. We shouldn't
>> push any changes to the vanilla branches, but only to "*-cdh5" branches (or
>> any temporary side branches we need to create).
>>
>> The issue tracker will be very useful, yes.
>>
>> James
>>
>>
>>
>> On 14/09/15 17:22, Andrew Purtell wrote:
>>
>> This is great James.
>>
>>
>>
>> Since this is conveniently on Github, maybe we use the issue tracker
>> there? Interested parties can set a watch. Would you be willing to add
>> 'apurtell' as a collaborator on the repo? I will fork and send over PRs of
>> course, but you might want help?
>>
>>
>> On Sep 14, 2015, at 6:21 AM, James Heather < <ja...@mendeley.com>
>> james.heather@mendeley.com> wrote:
>>
>> I've set up a repo at
>>
>> <https://github.com/chiastic-security/phoenix-for-cloudera>
>> https://github.com/chiastic-security/phoenix-for-cloudera
>>
>> It is a fork of the vanilla Phoenix github mirror. I've created a branch
>> called "4.5-HBase-1.0-cdh5", which we can use for making a CDH5-compatible
>> version. I've not made any of the necessary changes so far.
>>
>> I chose that branch, by the way, because it's the latest release, and is
>> using the same version of HBase as CDH5.4. The master branch of the Phoenix
>> repo is building a snapshot of (the forthcoming) Phoenix 4.6, against HBase
>> 1.1... presumably there will also be a Phoenix 4.6 for HBase 1.0?
>>
>> I'm not certain of the best way to manage this. Perhaps we need a new
>> mailing list for those who want to help, to avoid cluttering this list up.
>>
>> James
>>
>> On 13/09/15 02:54, Jean-Marc Spaggiari wrote:
>>
>> Exact. There is some some code change because of what has been back
>> ported into CDH and what has not been. But overall, it should not be rocket
>> science. Mostly method signatures...
>>
>> Let us know when the repo is available so we can help...
>>
>> Thanks,
>>
>> JM
>>
>>
>>
>> 2015-09-12 18:38 GMT-04:00 Krishna < <re...@gmail.com>
>> research800@gmail.com>:
>>
>> As explained here, there are some code changes too in addition to pom
>> related changes.
>>
>>
>>
>> <http://stackoverflow.com/a/31934434/165130>
>> http://stackoverflow.com/a/31934434/165130
>>
>>
>>
>>
>>
>> On Friday, September 11, 2015, Andrew Purtell <
>> <an...@gmail.com> wrote:
>>
>> Or once parameterized, add a default off profile that redefines them all
>> in one shot after the builder activates the profile on the maven command
>> line with -P ...
>>
>>
>> On Sep 11, 2015, at 7:05 AM, Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com> wrote:
>>
>> The group IDs and versions can be parameterized in the POM so they can be
>> overridden on the maven command line with -D. That would be easy and
>> something I think we could get committed without any controversy.
>>
>>
>> On Sep 11, 2015, at 6:53 AM, James Heather < <ja...@mendeley.com>
>> james.heather@mendeley.com> wrote:
>>
>> Yes, my plan is to create a fork of the main repo, so that we can still
>> merge new Phoenix code into the CDH-compatible version.
>>
>> Before that, I do wonder whether it's possible to suggest a few changes
>> to the main repo that would allow for compiling a CDH-compatible version,
>> without needing to maintain a separate repo. The bulk of the changes are to
>> dependencies in the pom, which suggests that it could be done to accept a
>> switch to mvn build.
>>
>> James
>>
>> On 11/09/15 14:50, Andrew Purtell wrote:
>>
>> The first step I think is a repo with code that compiles. Please
>> initialize it by forking github.com/apache/phoenix so we have common
>> ancestors. Once we have a clear idea (by diff) what is required we can
>> figure out if we can support compatibility in some way.
>>
>>
>> On Sep 9, 2015, at 11:00 PM, Krishna < <re...@gmail.com>
>> research800@gmail.com> wrote:
>>
>> I can volunteer to spend some time on this.
>>
>>
>>
>> CDH artifacts are available in Maven repo but from reading other threads
>> on CDH-Phoenix compatibilty, it looks like there are some code changes to
>> be made in Phoenix to successfully compile against CDH.
>>
>>
>>
>> Here are questions to address:
>>
>> 1) How to maintain CDH compatible Phoenix code base?
>>
>> 2) Is having a CDH compatible branch even an option?
>>
>>
>> Krishna
>>
>>
>>
>>
>>
>> On Friday, August 28, 2015, Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com> wrote:
>>
>> Yes I am interested. Assuming CDH artifacts are publicly available in a
>> Maven repo somewhere, which I believe is the case, perhaps we (the Phoenix
>> project/community) could set up a Jenkins job that builds against them and
>> makes the resulting build artifacts available. They would never be an
>> official release, just a best effort convenience. Would that work? I think
>> little must be done besides compile against the CDH artifacts for binary
>> compatibility.
>>
>>
>> > On Aug 28, 2015, at 11:19 AM, James Heather <
>> <ja...@mendeley.com> wrote:
>> >
>> > Is anyone interested in helping with getting an up-to-date
>> CDH5-compatible build of Phoenix up and running?
>> >
>> > Cloudera has a build of Phoenix 4.3 (
>> <https://github.com/cloudera-labs/phoenix>
>> https://github.com/cloudera-labs/phoenix), but this is now two versions
>> behind, and there seems little desire at Cloudera to keep it updated.
>> >
>> > I imagine that by looking at the differences between vanilla 4.3 and
>> cloudera labs 4.3, and with some guidance from this list, we could get a
>> good idea of what would need to be modified in 4.5+ and keep a
>> CDH5-compatible build up to date.
>> >
>> > Yes?
>> >
>> > James
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
Re: setting up community repo of Phoenix for CDH5?
Posted by Dhruv Gohil <yo...@gmail.com>.
Hi JM,
Can you please share the source code of how to build 'the parcel' ?
We want to package our owned patched phoenix as parcel for
different CDH version.
Will love to share custom CDH parcels like we already do for HDP
(http://hortonworks-gallery.github.io/index.html?sort=asc&filter=ambari%20extensions)
Thanks for the awesome work!
Also,
Has anybody had success with this parcel? (we don't yet have
compatible CDH cluster yet, so waiting for any one guy's go ahead to do
so) ;-)
On Thursday 08 October 2015 10:37 PM, Jean-Marc Spaggiari wrote:
> Can you try this repo for your installation?
>
> http://server.distparser.com:81/parcels/
>
> Don't look at the name of the files... Even if it says 4.3.0 it's
> 4.5.2 inside. Install is and launch the Phoenix command line to
> validate it.
>
> Please be aware that it's not at all supported by cloudera in anyway,
> not approved by them nor provided by them nor anything else by them ;)
>
> Those parcels work for me. I'm sure they will for you too. Please keep
> me posted.
>
> JM
>
> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven <Kevin.Verhoeven@ds-iq.com
> <ma...@ds-iq.com>>:
>
> JM,
>
> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
> Cloudera? This would be very useful if made available. Thanks for
> your time!
>
> Kevin
>
> *From:*James Heather [mailto:james.heather@mendeley.com
> <ma...@mendeley.com>]
> *Sent:* Wednesday, September 30, 2015 5:22 AM
> *To:* user@phoenix.apache.org <ma...@phoenix.apache.org>
> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>
> Hi JM,
>
> Is there a way of getting hold of the parcel you built? I'm keen
> to try it!
>
> Best wishes,
>
> James
>
> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>
> Hi James,
>
> I have been able to build a parcel and installed it on my own
> cluster. Build it with 4.5.2 that Andrew modified. I'm in
> touch with Cloudera to see what's the next steps. I will let
> you know very shortly...
>
> JM
>
> 2015-09-21 6:25 GMT-04:00 James Heather
> <james.heather@mendeley.com <ma...@mendeley.com>>:
>
> @JM how did you get on with the parcel building?
>
> Has anyone managed to get 4.5 working on CDH5 now? I was
> going to stick with 4.3 on our cluster until we had a
> parcel, but I'm now needing to use pherf, and that doesn't
> seem to exist in 4.3.
>
> James
>
> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>
> @James: I'm working on the parcel building ;) If not
> me I will try to find someone to do it. Stay tuned.
>
> @Andrewy: It works for me that way, cool! I just have
> a signature issue where it says I have no signature.
> Will that be an issue?
>
> Thanks all,
>
> JM
>
> 2015-09-16 3:24 GMT-04:00 James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>:
>
> Great! Thank you!
>
> I'd wondered about parcel building. It did look as
> though a parcel is just a .tgz, containing the
> classes and a few bits of meta, so hopefully it's
> doable. It would be really nice if we could
> provide a working 4.5 parcel.
>
> James
>
> On 16 Sep 2015 01:02, "Andrew Purtell"
> <apurtell@apache.org <ma...@apache.org>>
> wrote:
>
> I used dev/make_rc.sh, built with Maven 3.2.2,
> Java 7u79. Ubuntu build host.
>
> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc
> Spaggiari <jean-marc@spaggiari.org
> <ma...@spaggiari.org>> wrote:
>
> No, I don't know why. I will ask and see
> if I can get a respons on that. I have
> also started the thread for the Parcel. I
> will see if I find enough help to work on
> that.
>
> Regarding the branch you made, I tried to
> build it but got the error below. what's
> the command to build it?
>
> Thanks,
>
> JM
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at
> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 17 seconds
> [INFO] Finished at: Tue Sep 15 19:55:03
> EDT 2015
> [INFO] Final Memory: 134M/1648M
> [INFO]
> ------------------------------------------------------------------------
>
> 2015-09-15 19:55 GMT-04:00 Andrew Purtell
> <apurtell@apache.org
> <ma...@apache.org>>:
>
> Cool, thanks J-M.
>
> Do you know why support for query
> tracing was removed? If it's just a
> matter of porting it to the HTrace
> that ships with CDH, I can look at that.
>
> On Tue, Sep 15, 2015 at 4:49 PM,
> Jean-Marc Spaggiari
> <jean-marc@spaggiari.org
> <ma...@spaggiari.org>> wrote:
>
> Nice! I will see if there is a way
> to build a parcel from that the
> same way there is a parcel for
> Apache Phoenix 4.3 in Cloudera
> Labs... Will clone what you did
> and try to build it locally...
>
> 2015-09-15 19:45 GMT-04:00 Andrew
> Purtell <andrew.purtell@gmail.com
> <ma...@gmail.com>>:
>
> I pushed updates to branch
> 4.5-HBase-1.0-cdh5 and the tag
> v4.5.2-cdh5.4.5 (1fcb5cf).
> This is the pending Phoenix
> 4.5.2 release, currently at
> RC1, likely to pass, that will
> build against CDH 5.4.5. If
> you want release tarballs I
> built from this, get them here:
>
> Binary:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>
> Source:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>
>
> The source and these binaries
> incorporate changes from the
> Cloudera Labs fork of Phoenix
> (https://github.com/cloudera-labs/phoenix),
> licensed under the ASL v2,
> Neither the source or binary
> artifacts are in any way
> "official" or supported by the
> Apache Phoenix project. The
> source and artifacts are
> provided by me in a personal
> capacity for the convenience
> of would-be Phoenix users that
> also use CDH 5.4(.5). Please
> don't contact the Apache
> Phoenix project for any issues
> regarding this source and
> these binaries.
>
>
>
> On Mon, Sep 14, 2015 at 10:52
> AM, James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> Done! Thanks for helping!
>
> The branches in the repo
> mirror those in vanilla
> Phoenix. We shouldn't push
> any changes to the vanilla
> branches, but only to
> "*-cdh5" branches (or any
> temporary side branches we
> need to create).
>
> The issue tracker will be
> very useful, yes.
>
> James
>
> On 14/09/15 17:22, Andrew
> Purtell wrote:
>
> This is great James.
>
> Since this is
> conveniently on
> Github, maybe we use
> the issue tracker
> there? Interested
> parties can set a
> watch. Would you be
> willing to add
> 'apurtell' as a
> collaborator on the
> repo? I will fork and
> send over PRs of
> course, but you might
> want help?
>
>
> On Sep 14, 2015, at
> 6:21 AM, James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> I've set up a repo at
>
> https://github.com/chiastic-security/phoenix-for-cloudera
>
> It is a fork of
> the vanilla
> Phoenix github
> mirror. I've
> created a branch
> called
> "4.5-HBase-1.0-cdh5",
> which we can use
> for making a
> CDH5-compatible
> version. I've not
> made any of the
> necessary changes
> so far.
>
> I chose that
> branch, by the
> way, because it's
> the latest
> release, and is
> using the same
> version of HBase
> as CDH5.4. The
> master branch of
> the Phoenix repo
> is building a
> snapshot of (the
> forthcoming)
> Phoenix 4.6,
> against HBase
> 1.1... presumably
> there will also be
> a Phoenix 4.6 for
> HBase 1.0?
>
> I'm not certain of
> the best way to
> manage this.
> Perhaps we need a
> new mailing list
> for those who want
> to help, to avoid
> cluttering this
> list up.
>
> James
>
> On 13/09/15 02:54,
> Jean-Marc
> Spaggiari wrote:
>
> Exact. There
> is some some
> code change
> because of
> what has been
> back ported
> into CDH and
> what has not
> been. But
> overall, it
> should not be
> rocket
> science.
> Mostly method
> signatures...
>
> Let us know
> when the repo
> is available
> so we can help...
>
> Thanks,
>
> JM
>
> 2015-09-12
> 18:38
> GMT-04:00
> Krishna
> <research800@gmail.com
> <ma...@gmail.com>>:
>
> As
> explained
> here,
> there are
> some code
> changes
> too in
> addition
> to pom
> related
> changes.
>
> http://stackoverflow.com/a/31934434/165130
>
>
>
> On Friday,
> September
> 11, 2015,
> Andrew
> Purtell
> <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> Or
> once
> parameterized,
> add a
> default off
> profile that
> redefines
> them
> all in
> one
> shot
> after
> the
> builder activates
> the
> profile on
> the
> maven
> command line
> with
> -P ...
>
>
> On Sep
> 11,
> 2015,
> at
> 7:05
> AM,
> Andrew
> Purtell <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> The group
> IDs and
> versions
> can be
> parameterized
> in
> the POM
> so
> they
> can be
> overridden
> on
> the maven
> command
> line
> with
> -D. That
> would
> be
> easy
> and something
> I
> think
> we
> could
> get committed
> without
> any controversy.
>
>
>
> On
> Sep 11,
> 2015,
> at
> 6:53
> AM, James
> Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> Yes,
> my
> plan
> is
> to
> create
> a fork
> of
> the
> main
> repo,
> so
> that
> we
> can
> still
> merge
> new
> Phoenix
> code
> into
> the
> CDH-compatible
> version.
>
> Before
> that,
> I do
> wonder
> whether
> it's
> possible
> to
> suggest
> a few
> changes
> to
> the
> main
> repo
> that
> would
> allow
> for
> compiling
> a CDH-compatible
> version,
> without
> needing
> to
> maintain
> a separate
> repo.
> The
> bulk
> of
> the
> changes
> are
> to
> dependencies
> in
> the
> pom,
> which
> suggests
> that
> it
> could
> be
> done
> to
> accept
> a switch
> to
> mvn
> build.
>
> James
>
> On
> 11/09/15
> 14:50,
> Andrew
> Purtell
> wrote:
>
> The
> first
> step
> I think
> is
> a repo
> with
> code
> that
> compiles.
> Please
> initialize
> it
> by
> forking
> github.com/apache/phoenix
> <http://github.com/apache/phoenix>
> so
> we
> have
> common
> ancestors.
> Once
> we
> have
> a clear
> idea
> (by
> diff)
> what
> is
> required
> we
> can
> figure
> out
> if
> we
> can
> support
> compatibility
> in
> some
> way.
>
>
> On
> Sep
> 9,
> 2015,
> at
> 11:00
> PM,
> Krishna
> <research800@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> I can
> volunteer
> to
> spend
> some
> time
> on
> this.
>
>
> CDH
> artifacts
> are
> available
> in
> Maven
> repo
> but
> from reading
> other
> threads
> on
> CDH-Phoenix
> compatibilty,
> it
> looks
> like
> there
> are
> some
> code
> changes
> to
> be
> made
> in
> Phoenix
> to
> successfully compile
> against
> CDH.
>
>
> Here
> are
> questions
> to
> address:
>
> 1)
> How
> to
> maintain
> CDH
> compatible
> Phoenix
> code
> base?
>
>
> 2)
> Is
> having
> a CDH
> compatible
> branch
> even
> an
> option?
>
>
> Krishna
>
>
>
> On
> Friday,
> August
> 28,
> 2015,
> Andrew
> Purtell
> <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> Yes
> I am
> interested.
> Assuming
> CDH
> artifacts
> are
> publicly
> available
> in
> a Maven
> repo
> somewhere,
> which
> I believe
> is
> the
> case,
> perhaps
> we
> (the
> Phoenix
> project/community)
> could
> set
> up
> a Jenkins
> job
> that
> builds
> against
> them
> and
> makes
> the
> resulting
> build
> artifacts
> available.
> They
> would
> never
> be
> an
> official
> release,
> just
> a best
> effort
> convenience.
> Would
> that
> work?
> I think
> little
> must
> be
> done
> besides
> compile
> against
> the
> CDH
> artifacts
> for
> binary
> compatibility.
>
>
> > On
> Aug
> 28,
> 2015,
> at
> 11:19
> AM,
> James
> Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
> >
> > Is
> anyone
> interested
> in
> helping
> with
> getting
> an
> up-to-date
> CDH5-compatible
> build
> of
> Phoenix
> up
> and
> running?
> >
> > Cloudera
> has
> a build
> of
> Phoenix
> 4.3
> (https://github.com/cloudera-labs/phoenix),
> but
> this
> is
> now
> two
> versions
> behind,
> and
> there
> seems
> little
> desire
> at
> Cloudera
> to
> keep
> it
> updated.
> >
> > I
> imagine
> that
> by
> looking
> at
> the
> differences
> between
> vanilla
> 4.3
> and
> cloudera
> labs
> 4.3,
> and
> with
> some
> guidance
> from
> this
> list,
> we
> could
> get
> a good
> idea
> of
> what
> would
> need
> to
> be
> modified
> in
> 4.5+
> and
> keep
> a CDH5-compatible
> build
> up
> to
> date.
> >
> > Yes?
> >
> > James
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their
> worth by hitting back. - Piet Hein
> (via Tom White)
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by
> hitting back. - Piet Hein (via Tom White)
>
>
Re: JM's 4.5.2 parcel for CDH5
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Good it hear it's not because of the parcel ;)
Let me know if it works...
JM
2015-10-12 11:16 GMT-04:00 James Heather <ja...@mendeley.com>:
> Hi JM,
>
> Looks as though this was a cock-up unrelated to Phoenix. Sorry for the
> noise.
>
> The EC2 instances tried to auto-upgrade the debian packages for CDH, and
> ended up in a broken state between 5.4.5 and 5.4.7 (and I don't mean we
> ended up with 5.4.6!). It's a cluster we're using for testing, so it's not
> a problem to tear it down and restart, and we're looking at ways to stop it
> happening in the future.
>
> James
>
>
> On 12/10/15 15:48, Jean-Marc Spaggiari wrote:
>
> Hi James,
>
> What do you have in your /var/log/cloudera-scm-server logs? Same for the
> agent. Any clue there?
>
> JM
>
> 2015-10-12 10:34 GMT-04:00 James Heather <ja...@mendeley.com>:
>
>> I can get CDH5 to download the new parcel that JM provided. When I try to
>> deactivate the old (Cloudera Labs) parcel, though, I get this rather
>> minimalistic error message.
>>
>> I thought it might be that it was still in use, so I stopped HBase and
>> ZooKeeper, and now it reports that no nodes are using the old parcel. But I
>> still get the same error when I try to deactivate.
>>
>> This is the same error that I get if I try to distribute the new parcel
>> to the nodes (which I'd hoped to be able to do before deactivating the old
>> one, to minimise downtime).
>>
>> Any clues?
>>
>> James
>>
>>
>>
>> On 08/10/15 18:07, Jean-Marc Spaggiari wrote:
>>
>> Can you try this repo for your installation?
>>
>> http://server.distparser.com:81/parcels/
>>
>> Don't look at the name of the files... Even if it says 4.3.0 it's 4.5.2
>> inside. Install is and launch the Phoenix command line to validate it.
>>
>> Please be aware that it's not at all supported by cloudera in anyway, not
>> approved by them nor provided by them nor anything else by them ;)
>>
>> Those parcels work for me. I'm sure they will for you too. Please keep me
>> posted.
>>
>> JM
>>
>> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven < <Ke...@ds-iq.com>
>> Kevin.Verhoeven@ds-iq.com>:
>>
>>> JM,
>>>
>>>
>>>
>>> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
>>> Cloudera? This would be very useful if made available. Thanks for your time!
>>>
>>>
>>>
>>> Kevin
>>>
>>>
>>>
>>> *From:* James Heather [mailto: <ja...@mendeley.com>
>>> james.heather@mendeley.com]
>>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>>> *To:* user@phoenix.apache.org
>>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>>
>>>
>>>
>>> Hi JM,
>>>
>>> Is there a way of getting hold of the parcel you built? I'm keen to try
>>> it!
>>>
>>> Best wishes,
>>>
>>> James
>>>
>>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>>
>>> Hi James,
>>>
>>> I have been able to build a parcel and installed it on my own cluster.
>>> Build it with 4.5.2 that Andrew modified. I'm in touch with Cloudera to see
>>> what's the next steps. I will let you know very shortly...
>>>
>>> JM
>>>
>>>
>>>
>>> 2015-09-21 6:25 GMT-04:00 James Heather < <ja...@mendeley.com>
>>> james.heather@mendeley.com>:
>>>
>>> @JM how did you get on with the parcel building?
>>>
>>> Has anyone managed to get 4.5 working on CDH5 now? I was going to stick
>>> with 4.3 on our cluster until we had a parcel, but I'm now needing to use
>>> pherf, and that doesn't seem to exist in 4.3.
>>>
>>> James
>>>
>>>
>>>
>>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>>
>>> @James: I'm working on the parcel building ;) If not me I will try to
>>> find someone to do it. Stay tuned.
>>>
>>> @Andrewy: It works for me that way, cool! I just have a signature issue
>>> where it says I have no signature. Will that be an issue?
>>>
>>> Thanks all,
>>>
>>> JM
>>>
>>>
>>>
>>> 2015-09-16 3:24 GMT-04:00 James Heather < <ja...@mendeley.com>
>>> james.heather@mendeley.com>:
>>>
>>> Great! Thank you!
>>>
>>> I'd wondered about parcel building. It did look as though a parcel is
>>> just a .tgz, containing the classes and a few bits of meta, so hopefully
>>> it's doable. It would be really nice if we could provide a working 4.5
>>> parcel.
>>>
>>> James
>>>
>>> On 16 Sep 2015 01:02, "Andrew Purtell" < <ap...@apache.org>
>>> apurtell@apache.org> wrote:
>>>
>>> I used dev/make_rc.sh, built with Maven 3.2.2, Java 7u79. Ubuntu build
>>> host.
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc Spaggiari <
>>> <je...@spaggiari.org> wrote:
>>>
>>> No, I don't know why. I will ask and see if I can get a respons on that.
>>> I have also started the thread for the Parcel. I will see if I find enough
>>> help to work on that.
>>>
>>> Regarding the branch you made, I tried to build it but got the error
>>> below. what's the command to build it?
>>>
>>> Thanks,
>>>
>>> JM
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] FATAL ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] null
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> java.lang.NullPointerException
>>> at
>>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>>> at
>>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>>> at
>>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> at
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> at
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 2 minutes 17 seconds
>>> [INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015
>>> [INFO] Final Memory: 134M/1648M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>>
>>>
>>> 2015-09-15 19:55 GMT-04:00 Andrew Purtell < <ap...@apache.org>
>>> apurtell@apache.org>:
>>>
>>> Cool, thanks J-M.
>>>
>>>
>>>
>>> Do you know why support for query tracing was removed? If it's just a
>>> matter of porting it to the HTrace that ships with CDH, I can look at that.
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Sep 15, 2015 at 4:49 PM, Jean-Marc Spaggiari <
>>> <je...@spaggiari.org> wrote:
>>>
>>> Nice! I will see if there is a way to build a parcel from that the same
>>> way there is a parcel for Apache Phoenix 4.3 in Cloudera Labs... Will clone
>>> what you did and try to build it locally...
>>>
>>>
>>>
>>> 2015-09-15 19:45 GMT-04:00 Andrew Purtell < <an...@gmail.com>
>>> andrew.purtell@gmail.com>:
>>>
>>> I pushed updates to branch 4.5-HBase-1.0-cdh5 and the tag
>>> v4.5.2-cdh5.4.5 (1fcb5cf). This is the pending Phoenix 4.5.2 release,
>>> currently at RC1, likely to pass, that will build against CDH 5.4.5. If you
>>> want release tarballs I built from this, get them here:
>>>
>>> Binary:
>>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz>
>>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>>
>>> Source:
>>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz>
>>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>>
>>>
>>>
>>>
>>> The source and these binaries incorporate changes from the Cloudera
>>> Labs fork of Phoenix ( <https://github.com/cloudera-labs/phoenix>
>>> https://github.com/cloudera-labs/phoenix), licensed under the ASL v2,
>>> Neither the source or binary artifacts are in any way "official" or
>>> supported by the Apache Phoenix project. The source and artifacts are
>>> provided by me in a personal capacity for the convenience of would-be
>>> Phoenix users that also use CDH 5.4(.5). Please don't contact the Apache
>>> Phoenix project for any issues regarding this source and these binaries.
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Sep 14, 2015 at 10:52 AM, James Heather <
>>> <ja...@mendeley.com> wrote:
>>>
>>> Done! Thanks for helping!
>>>
>>> The branches in the repo mirror those in vanilla Phoenix. We shouldn't
>>> push any changes to the vanilla branches, but only to "*-cdh5" branches (or
>>> any temporary side branches we need to create).
>>>
>>> The issue tracker will be very useful, yes.
>>>
>>> James
>>>
>>>
>>>
>>> On 14/09/15 17:22, Andrew Purtell wrote:
>>>
>>> This is great James.
>>>
>>>
>>>
>>> Since this is conveniently on Github, maybe we use the issue tracker
>>> there? Interested parties can set a watch. Would you be willing to add
>>> 'apurtell' as a collaborator on the repo? I will fork and send over PRs of
>>> course, but you might want help?
>>>
>>>
>>> On Sep 14, 2015, at 6:21 AM, James Heather <
>>> <ja...@mendeley.com> wrote:
>>>
>>> I've set up a repo at
>>>
>>> <https://github.com/chiastic-security/phoenix-for-cloudera>
>>> https://github.com/chiastic-security/phoenix-for-cloudera
>>>
>>> It is a fork of the vanilla Phoenix github mirror. I've created a branch
>>> called "4.5-HBase-1.0-cdh5", which we can use for making a CDH5-compatible
>>> version. I've not made any of the necessary changes so far.
>>>
>>> I chose that branch, by the way, because it's the latest release, and is
>>> using the same version of HBase as CDH5.4. The master branch of the Phoenix
>>> repo is building a snapshot of (the forthcoming) Phoenix 4.6, against HBase
>>> 1.1... presumably there will also be a Phoenix 4.6 for HBase 1.0?
>>>
>>> I'm not certain of the best way to manage this. Perhaps we need a new
>>> mailing list for those who want to help, to avoid cluttering this list up.
>>>
>>> James
>>>
>>> On 13/09/15 02:54, Jean-Marc Spaggiari wrote:
>>>
>>> Exact. There is some some code change because of what has been back
>>> ported into CDH and what has not been. But overall, it should not be rocket
>>> science. Mostly method signatures...
>>>
>>> Let us know when the repo is available so we can help...
>>>
>>> Thanks,
>>>
>>> JM
>>>
>>>
>>>
>>> 2015-09-12 18:38 GMT-04:00 Krishna < <re...@gmail.com>
>>> research800@gmail.com>:
>>>
>>> As explained here, there are some code changes too in addition to pom
>>> related changes.
>>>
>>>
>>>
>>> <http://stackoverflow.com/a/31934434/165130>
>>> http://stackoverflow.com/a/31934434/165130
>>>
>>>
>>>
>>>
>>>
>>> On Friday, September 11, 2015, Andrew Purtell <
>>> <an...@gmail.com> wrote:
>>>
>>> Or once parameterized, add a default off profile that redefines them all
>>> in one shot after the builder activates the profile on the maven command
>>> line with -P ...
>>>
>>>
>>> On Sep 11, 2015, at 7:05 AM, Andrew Purtell < <an...@gmail.com>
>>> andrew.purtell@gmail.com> wrote:
>>>
>>> The group IDs and versions can be parameterized in the POM so they can
>>> be overridden on the maven command line with -D. That would be easy and
>>> something I think we could get committed without any controversy.
>>>
>>>
>>> On Sep 11, 2015, at 6:53 AM, James Heather <
>>> <ja...@mendeley.com> wrote:
>>>
>>> Yes, my plan is to create a fork of the main repo, so that we can still
>>> merge new Phoenix code into the CDH-compatible version.
>>>
>>> Before that, I do wonder whether it's possible to suggest a few changes
>>> to the main repo that would allow for compiling a CDH-compatible version,
>>> without needing to maintain a separate repo. The bulk of the changes are to
>>> dependencies in the pom, which suggests that it could be done to accept a
>>> switch to mvn build.
>>>
>>> James
>>>
>>> On 11/09/15 14:50, Andrew Purtell wrote:
>>>
>>> The first step I think is a repo with code that compiles. Please
>>> initialize it by forking github.com/apache/phoenix so we have common
>>> ancestors. Once we have a clear idea (by diff) what is required we can
>>> figure out if we can support compatibility in some way.
>>>
>>>
>>> On Sep 9, 2015, at 11:00 PM, Krishna < <re...@gmail.com>
>>> research800@gmail.com> wrote:
>>>
>>> I can volunteer to spend some time on this.
>>>
>>>
>>>
>>> CDH artifacts are available in Maven repo but from reading other threads
>>> on CDH-Phoenix compatibilty, it looks like there are some code changes to
>>> be made in Phoenix to successfully compile against CDH.
>>>
>>>
>>>
>>> Here are questions to address:
>>>
>>> 1) How to maintain CDH compatible Phoenix code base?
>>>
>>> 2) Is having a CDH compatible branch even an option?
>>>
>>>
>>> Krishna
>>>
>>>
>>>
>>>
>>>
>>> On Friday, August 28, 2015, Andrew Purtell < <an...@gmail.com>
>>> andrew.purtell@gmail.com> wrote:
>>>
>>> Yes I am interested. Assuming CDH artifacts are publicly available in a
>>> Maven repo somewhere, which I believe is the case, perhaps we (the Phoenix
>>> project/community) could set up a Jenkins job that builds against them and
>>> makes the resulting build artifacts available. They would never be an
>>> official release, just a best effort convenience. Would that work? I think
>>> little must be done besides compile against the CDH artifacts for binary
>>> compatibility.
>>>
>>>
>>> > On Aug 28, 2015, at 11:19 AM, James Heather <
>>> <ja...@mendeley.com> wrote:
>>> >
>>> > Is anyone interested in helping with getting an up-to-date
>>> CDH5-compatible build of Phoenix up and running?
>>> >
>>> > Cloudera has a build of Phoenix 4.3 (
>>> <https://github.com/cloudera-labs/phoenix>
>>> https://github.com/cloudera-labs/phoenix), but this is now two versions
>>> behind, and there seems little desire at Cloudera to keep it updated.
>>> >
>>> > I imagine that by looking at the differences between vanilla 4.3 and
>>> cloudera labs 4.3, and with some guidance from this list, we could get a
>>> good idea of what would need to be modified in 4.5+ and keep a
>>> CDH5-compatible build up to date.
>>> >
>>> > Yes?
>>> >
>>> > James
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>>
>>> - Andy
>>>
>>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>>> (via Tom White)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Best regards,
>>>
>>> - Andy
>>>
>>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>>> (via Tom White)
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
Re: JM's 4.5.2 parcel for CDH5
Posted by James Heather <ja...@mendeley.com>.
Hi JM,
Looks as though this was a cock-up unrelated to Phoenix. Sorry for the
noise.
The EC2 instances tried to auto-upgrade the debian packages for CDH, and
ended up in a broken state between 5.4.5 and 5.4.7 (and I don't mean we
ended up with 5.4.6!). It's a cluster we're using for testing, so it's
not a problem to tear it down and restart, and we're looking at ways to
stop it happening in the future.
James
On 12/10/15 15:48, Jean-Marc Spaggiari wrote:
> Hi James,
>
> What do you have in your /var/log/cloudera-scm-server logs? Same for
> the agent. Any clue there?
>
> JM
>
> 2015-10-12 10:34 GMT-04:00 James Heather <james.heather@mendeley.com
> <ma...@mendeley.com>>:
>
> I can get CDH5 to download the new parcel that JM provided. When I
> try to deactivate the old (Cloudera Labs) parcel, though, I get
> this rather minimalistic error message.
>
> I thought it might be that it was still in use, so I stopped HBase
> and ZooKeeper, and now it reports that no nodes are using the old
> parcel. But I still get the same error when I try to deactivate.
>
> This is the same error that I get if I try to distribute the new
> parcel to the nodes (which I'd hoped to be able to do before
> deactivating the old one, to minimise downtime).
>
> Any clues?
>
> James
>
>
>
> On 08/10/15 18:07, Jean-Marc Spaggiari wrote:
>> Can you try this repo for your installation?
>>
>> http://server.distparser.com:81/parcels/
>>
>> Don't look at the name of the files... Even if it says 4.3.0 it's
>> 4.5.2 inside. Install is and launch the Phoenix command line to
>> validate it.
>>
>> Please be aware that it's not at all supported by cloudera in
>> anyway, not approved by them nor provided by them nor anything
>> else by them ;)
>>
>> Those parcels work for me. I'm sure they will for you too. Please
>> keep me posted.
>>
>> JM
>>
>> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven
>> <Kevin.Verhoeven@ds-iq.com <ma...@ds-iq.com>>:
>>
>> JM,
>>
>> If possible, I’d also like to try your 4.5.2 Parcel. Any luck
>> with Cloudera? This would be very useful if made available.
>> Thanks for your time!
>>
>> Kevin
>>
>> *From:*James Heather [mailto:james.heather@mendeley.com
>> <ma...@mendeley.com>]
>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>> *To:* user@phoenix.apache.org <ma...@phoenix.apache.org>
>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>
>> Hi JM,
>>
>> Is there a way of getting hold of the parcel you built? I'm
>> keen to try it!
>>
>> Best wishes,
>>
>> James
>>
>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>
>> Hi James,
>>
>> I have been able to build a parcel and installed it on my
>> own cluster. Build it with 4.5.2 that Andrew modified.
>> I'm in touch with Cloudera to see what's the next steps.
>> I will let you know very shortly...
>>
>> JM
>>
>> 2015-09-21 6:25 GMT-04:00 James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>:
>>
>> @JM how did you get on with the parcel building?
>>
>> Has anyone managed to get 4.5 working on CDH5 now? I
>> was going to stick with 4.3 on our cluster until we
>> had a parcel, but I'm now needing to use pherf, and
>> that doesn't seem to exist in 4.3.
>>
>> James
>>
>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>
>> @James: I'm working on the parcel building ;) If
>> not me I will try to find someone to do it. Stay
>> tuned.
>>
>> @Andrewy: It works for me that way, cool! I just
>> have a signature issue where it says I have no
>> signature. Will that be an issue?
>>
>> Thanks all,
>>
>> JM
>>
>> 2015-09-16 3:24 GMT-04:00 James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>:
>>
>> Great! Thank you!
>>
>> I'd wondered about parcel building. It did
>> look as though a parcel is just a .tgz,
>> containing the classes and a few bits of
>> meta, so hopefully it's doable. It would be
>> really nice if we could provide a working 4.5
>> parcel.
>>
>> James
>>
>> On 16 Sep 2015 01:02, "Andrew Purtell"
>> <apurtell@apache.org
>> <ma...@apache.org>> wrote:
>>
>> I used dev/make_rc.sh, built with Maven
>> 3.2.2, Java 7u79. Ubuntu build host.
>>
>> On Tue, Sep 15, 2015 at 4:58 PM,
>> Jean-Marc Spaggiari
>> <jean-marc@spaggiari.org
>> <ma...@spaggiari.org>> wrote:
>>
>> No, I don't know why. I will ask and
>> see if I can get a respons on that. I
>> have also started the thread for the
>> Parcel. I will see if I find enough
>> help to work on that.
>>
>> Regarding the branch you made, I
>> tried to build it but got the error
>> below. what's the command to build it?
>>
>> Thanks,
>>
>> JM
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.NullPointerException
>> at
>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>> at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at
>> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at
>> java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at
>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at
>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2 minutes 17 seconds
>> [INFO] Finished at: Tue Sep 15
>> 19:55:03 EDT 2015
>> [INFO] Final Memory: 134M/1648M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> 2015-09-15 19:55 GMT-04:00 Andrew
>> Purtell <apurtell@apache.org
>> <ma...@apache.org>>:
>>
>> Cool, thanks J-M.
>>
>> Do you know why support for query
>> tracing was removed? If it's just
>> a matter of porting it to the
>> HTrace that ships with CDH, I can
>> look at that.
>>
>> On Tue, Sep 15, 2015 at 4:49 PM,
>> Jean-Marc Spaggiari
>> <jean-marc@spaggiari.org
>> <ma...@spaggiari.org>>
>> wrote:
>>
>> Nice! I will see if there is
>> a way to build a parcel from
>> that the same way there is a
>> parcel for Apache Phoenix 4.3
>> in Cloudera Labs... Will
>> clone what you did and try to
>> build it locally...
>>
>> 2015-09-15 19:45 GMT-04:00
>> Andrew Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>:
>>
>> I pushed updates to
>> branch 4.5-HBase-1.0-cdh5
>> and the tag
>> v4.5.2-cdh5.4.5
>> (1fcb5cf). This is the
>> pending Phoenix 4.5.2
>> release, currently at
>> RC1, likely to pass, that
>> will build against CDH
>> 5.4.5. If you want
>> release tarballs I built
>> from this, get them here:
>>
>> Binary:
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>
>> Source:
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>
>>
>> The source and these
>> binaries incorporate
>> changes from the Cloudera
>> Labs fork of Phoenix
>> (https://github.com/cloudera-labs/phoenix),
>> licensed under the ASL
>> v2, Neither the source or
>> binary artifacts are in
>> any way "official" or
>> supported by the Apache
>> Phoenix project. The
>> source and artifacts are
>> provided by me in a
>> personal capacity for the
>> convenience of would-be
>> Phoenix users that also
>> use CDH 5.4(.5). Please
>> don't contact the Apache
>> Phoenix project for any
>> issues regarding this
>> source and these binaries.
>>
>>
>>
>> On Mon, Sep 14, 2015 at
>> 10:52 AM, James Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> Done! Thanks for helping!
>>
>> The branches in the
>> repo mirror those in
>> vanilla Phoenix. We
>> shouldn't push any
>> changes to the
>> vanilla branches, but
>> only to "*-cdh5"
>> branches (or any
>> temporary side
>> branches we need to
>> create).
>>
>> The issue tracker
>> will be very useful, yes.
>>
>> James
>>
>> On 14/09/15 17:22,
>> Andrew Purtell wrote:
>>
>> This is great James.
>>
>> Since this is
>> conveniently on
>> Github, maybe we
>> use the issue
>> tracker there?
>> Interested
>> parties can set a
>> watch. Would you
>> be willing to add
>> 'apurtell' as a
>> collaborator on
>> the repo? I will
>> fork and send
>> over PRs of
>> course, but you
>> might want help?
>>
>>
>> On Sep 14, 2015,
>> at 6:21 AM, James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> I've set up a
>> repo at
>>
>> https://github.com/chiastic-security/phoenix-for-cloudera
>>
>> It is a fork
>> of the
>> vanilla
>> Phoenix
>> github
>> mirror. I've
>> created a
>> branch called
>> "4.5-HBase-1.0-cdh5",
>> which we can
>> use for
>> making a
>> CDH5-compatible
>> version. I've
>> not made any
>> of the
>> necessary
>> changes so far.
>>
>> I chose that
>> branch, by
>> the way,
>> because it's
>> the latest
>> release, and
>> is using the
>> same version
>> of HBase as
>> CDH5.4. The
>> master branch
>> of the
>> Phoenix repo
>> is building a
>> snapshot of
>> (the
>> forthcoming)
>> Phoenix 4.6,
>> against HBase
>> 1.1...
>> presumably
>> there will
>> also be a
>> Phoenix 4.6
>> for HBase 1.0?
>>
>> I'm not
>> certain of
>> the best way
>> to manage
>> this. Perhaps
>> we need a new
>> mailing list
>> for those who
>> want to help,
>> to avoid
>> cluttering
>> this list up.
>>
>> James
>>
>> On 13/09/15
>> 02:54,
>> Jean-Marc
>> Spaggiari wrote:
>>
>> Exact.
>> There is
>> some some
>> code
>> change
>> because
>> of what
>> has been
>> back
>> ported
>> into CDH
>> and what
>> has not
>> been. But
>> overall,
>> it should
>> not be
>> rocket
>> science.
>> Mostly
>> method
>> signatures...
>>
>> Let us
>> know when
>> the repo
>> is
>> available
>> so we can
>> help...
>>
>> Thanks,
>>
>> JM
>>
>> 2015-09-12 18:38
>> GMT-04:00
>> Krishna
>> <research800@gmail.com
>> <ma...@gmail.com>>:
>>
>> As
>> explained
>> here,
>> there
>> are
>> some
>> code
>> changes
>> too
>> in
>> addition
>> to
>> pom
>> related
>> changes.
>>
>> http://stackoverflow.com/a/31934434/165130
>>
>>
>>
>> On
>> Friday,
>> September
>> 11,
>> 2015,
>> Andrew Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> Or once
>> parameterized,
>> add
>> a
>> default
>> off
>> profile
>> that
>> redefines
>> them
>> all
>> in one
>> shot
>> after
>> the
>> builder
>> activates
>> the
>> profile
>> on the
>> maven
>> command
>> line
>> with
>> -P ...
>>
>>
>>
>> On Sep
>> 11,
>> 2015,
>> at 7:05
>> AM,
>> Andrew
>> Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> The
>> group
>> IDs
>> and
>> versions
>> can
>> be
>> parameterized
>> in
>> the
>> POM
>> so
>> they
>> can
>> be
>> overridden
>> on
>> the
>> maven
>> command
>> line
>> with
>> -D.
>> That
>> would
>> be
>> easy
>> and
>> something
>> I think
>> we
>> could
>> get
>> committed
>> without
>> any
>> controversy.
>>
>>
>>
>> On
>> Sep
>> 11,
>> 2015,
>> at
>> 6:53
>> AM,
>> James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>>
>> Yes,
>> my
>> plan
>> is
>> to
>> create
>> a fork
>> of
>> the
>> main
>> repo,
>> so
>> that
>> we
>> can
>> still
>> merge
>> new
>> Phoenix
>> code
>> into
>> the
>> CDH-compatible
>> version.
>>
>> Before
>> that,
>> I do
>> wonder
>> whether
>> it's
>> possible
>> to
>> suggest
>> a few
>> changes
>> to
>> the
>> main
>> repo
>> that
>> would
>> allow
>> for
>> compiling
>> a CDH-compatible
>> version,
>> without
>> needing
>> to
>> maintain
>> a separate
>> repo.
>> The
>> bulk
>> of
>> the
>> changes
>> are
>> to
>> dependencies
>> in
>> the
>> pom,
>> which
>> suggests
>> that
>> it
>> could
>> be
>> done
>> to
>> accept
>> a switch
>> to
>> mvn
>> build.
>>
>> James
>>
>> On
>> 11/09/15
>> 14:50,
>> Andrew
>> Purtell
>> wrote:
>>
>> The
>> first
>> step
>> I think
>> is
>> a repo
>> with
>> code
>> that
>> compiles.
>> Please
>> initialize
>> it
>> by
>> forking
>> github.com/apache/phoenix
>> <http://github.com/apache/phoenix>
>> so
>> we
>> have
>> common
>> ancestors.
>> Once
>> we
>> have
>> a clear
>> idea
>> (by
>> diff)
>> what
>> is
>> required
>> we
>> can
>> figure
>> out
>> if
>> we
>> can
>> support
>> compatibility
>> in
>> some
>> way.
>>
>>
>> On
>> Sep
>> 9,
>> 2015,
>> at
>> 11:00
>> PM,
>> Krishna
>> <research800@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> I can
>> volunteer
>> to
>> spend
>> some
>> time
>> on
>> this.
>>
>>
>> CDH
>> artifacts
>> are
>> available
>> in
>> Maven
>> repo
>> but
>> from reading
>> other
>> threads
>> on
>> CDH-Phoenix
>> compatibilty,
>> it
>> looks
>> like
>> there
>> are
>> some
>> code
>> changes
>> to
>> be
>> made
>> in
>> Phoenix
>> to
>> successfully compile
>> against
>> CDH.
>>
>>
>> Here
>> are
>> questions
>> to
>> address:
>>
>> 1)
>> How
>> to
>> maintain
>> CDH
>> compatible
>> Phoenix
>> code
>> base?
>>
>>
>> 2)
>> Is
>> having
>> a CDH
>> compatible
>> branch
>> even
>> an
>> option?
>>
>>
>> Krishna
>>
>>
>>
>> On
>> Friday,
>> August
>> 28,
>> 2015,
>> Andrew
>> Purtell
>> <andrew.purtell@gmail.com
>> <ma...@gmail.com>>
>> wrote:
>>
>> Yes
>> I am
>> interested.
>> Assuming
>> CDH
>> artifacts
>> are
>> publicly
>> available
>> in
>> a Maven
>> repo
>> somewhere,
>> which
>> I believe
>> is
>> the
>> case,
>> perhaps
>> we
>> (the
>> Phoenix
>> project/community)
>> could
>> set
>> up
>> a Jenkins
>> job
>> that
>> builds
>> against
>> them
>> and
>> makes
>> the
>> resulting
>> build
>> artifacts
>> available.
>> They
>> would
>> never
>> be
>> an
>> official
>> release,
>> just
>> a best
>> effort
>> convenience.
>> Would
>> that
>> work?
>> I think
>> little
>> must
>> be
>> done
>> besides
>> compile
>> against
>> the
>> CDH
>> artifacts
>> for
>> binary
>> compatibility.
>>
>>
>> > On
>> Aug
>> 28,
>> 2015,
>> at
>> 11:19
>> AM,
>> James
>> Heather
>> <james.heather@mendeley.com
>> <ma...@mendeley.com>>
>> wrote:
>> >
>> > Is
>> anyone
>> interested
>> in
>> helping
>> with
>> getting
>> an
>> up-to-date
>> CDH5-compatible
>> build
>> of
>> Phoenix
>> up
>> and
>> running?
>> >
>> > Cloudera
>> has
>> a build
>> of
>> Phoenix
>> 4.3
>> (https://github.com/cloudera-labs/phoenix),
>> but
>> this
>> is
>> now
>> two
>> versions
>> behind,
>> and
>> there
>> seems
>> little
>> desire
>> at
>> Cloudera
>> to
>> keep
>> it
>> updated.
>> >
>> > I
>> imagine
>> that
>> by
>> looking
>> at
>> the
>> differences
>> between
>> vanilla
>> 4.3
>> and
>> cloudera
>> labs
>> 4.3,
>> and
>> with
>> some
>> guidance
>> from
>> this
>> list,
>> we
>> could
>> get
>> a good
>> idea
>> of
>> what
>> would
>> need
>> to
>> be
>> modified
>> in
>> 4.5+
>> and
>> keep
>> a CDH5-compatible
>> build
>> up
>> to
>> date.
>> >
>> > Yes?
>> >
>> > James
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove
>> their worth by hitting back. -
>> Piet Hein (via Tom White)
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their
>> worth by hitting back. - Piet Hein (via
>> Tom White)
>>
>>
>
>
Re: JM's 4.5.2 parcel for CDH5
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Hi James,
What do you have in your /var/log/cloudera-scm-server logs? Same for the
agent. Any clue there?
JM
2015-10-12 10:34 GMT-04:00 James Heather <ja...@mendeley.com>:
> I can get CDH5 to download the new parcel that JM provided. When I try to
> deactivate the old (Cloudera Labs) parcel, though, I get this rather
> minimalistic error message.
>
> I thought it might be that it was still in use, so I stopped HBase and
> ZooKeeper, and now it reports that no nodes are using the old parcel. But I
> still get the same error when I try to deactivate.
>
> This is the same error that I get if I try to distribute the new parcel to
> the nodes (which I'd hoped to be able to do before deactivating the old
> one, to minimise downtime).
>
> Any clues?
>
> James
>
>
>
> On 08/10/15 18:07, Jean-Marc Spaggiari wrote:
>
> Can you try this repo for your installation?
>
> http://server.distparser.com:81/parcels/
>
> Don't look at the name of the files... Even if it says 4.3.0 it's 4.5.2
> inside. Install is and launch the Phoenix command line to validate it.
>
> Please be aware that it's not at all supported by cloudera in anyway, not
> approved by them nor provided by them nor anything else by them ;)
>
> Those parcels work for me. I'm sure they will for you too. Please keep me
> posted.
>
> JM
>
> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven <Ke...@ds-iq.com>:
>
>> JM,
>>
>>
>>
>> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
>> Cloudera? This would be very useful if made available. Thanks for your time!
>>
>>
>>
>> Kevin
>>
>>
>>
>> *From:* James Heather [mailto:james.heather@mendeley.com]
>> *Sent:* Wednesday, September 30, 2015 5:22 AM
>> *To:* user@phoenix.apache.org
>> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>>
>>
>>
>> Hi JM,
>>
>> Is there a way of getting hold of the parcel you built? I'm keen to try
>> it!
>>
>> Best wishes,
>>
>> James
>>
>> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>>
>> Hi James,
>>
>> I have been able to build a parcel and installed it on my own cluster.
>> Build it with 4.5.2 that Andrew modified. I'm in touch with Cloudera to see
>> what's the next steps. I will let you know very shortly...
>>
>> JM
>>
>>
>>
>> 2015-09-21 6:25 GMT-04:00 James Heather <ja...@mendeley.com>:
>>
>> @JM how did you get on with the parcel building?
>>
>> Has anyone managed to get 4.5 working on CDH5 now? I was going to stick
>> with 4.3 on our cluster until we had a parcel, but I'm now needing to use
>> pherf, and that doesn't seem to exist in 4.3.
>>
>> James
>>
>>
>>
>> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>>
>> @James: I'm working on the parcel building ;) If not me I will try to
>> find someone to do it. Stay tuned.
>>
>> @Andrewy: It works for me that way, cool! I just have a signature issue
>> where it says I have no signature. Will that be an issue?
>>
>> Thanks all,
>>
>> JM
>>
>>
>>
>> 2015-09-16 3:24 GMT-04:00 James Heather <ja...@mendeley.com>:
>>
>> Great! Thank you!
>>
>> I'd wondered about parcel building. It did look as though a parcel is
>> just a .tgz, containing the classes and a few bits of meta, so hopefully
>> it's doable. It would be really nice if we could provide a working 4.5
>> parcel.
>>
>> James
>>
>> On 16 Sep 2015 01:02, "Andrew Purtell" < <ap...@apache.org>
>> apurtell@apache.org> wrote:
>>
>> I used dev/make_rc.sh, built with Maven 3.2.2, Java 7u79. Ubuntu build
>> host.
>>
>>
>>
>>
>>
>> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc Spaggiari <
>> <je...@spaggiari.org> wrote:
>>
>> No, I don't know why. I will ask and see if I can get a respons on that.
>> I have also started the thread for the Parcel. I will see if I find enough
>> help to work on that.
>>
>> Regarding the branch you made, I tried to build it but got the error
>> below. what's the command to build it?
>>
>> Thanks,
>>
>> JM
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.NullPointerException
>> at
>> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
>> at
>> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
>> at
>> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> at
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2 minutes 17 seconds
>> [INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015
>> [INFO] Final Memory: 134M/1648M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>>
>> 2015-09-15 19:55 GMT-04:00 Andrew Purtell < <ap...@apache.org>
>> apurtell@apache.org>:
>>
>> Cool, thanks J-M.
>>
>>
>>
>> Do you know why support for query tracing was removed? If it's just a
>> matter of porting it to the HTrace that ships with CDH, I can look at that.
>>
>>
>>
>>
>>
>> On Tue, Sep 15, 2015 at 4:49 PM, Jean-Marc Spaggiari <
>> <je...@spaggiari.org> wrote:
>>
>> Nice! I will see if there is a way to build a parcel from that the same
>> way there is a parcel for Apache Phoenix 4.3 in Cloudera Labs... Will clone
>> what you did and try to build it locally...
>>
>>
>>
>> 2015-09-15 19:45 GMT-04:00 Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com>:
>>
>> I pushed updates to branch 4.5-HBase-1.0-cdh5 and the tag v4.5.2-cdh5.4.5
>> (1fcb5cf). This is the pending Phoenix 4.5.2 release, currently at RC1,
>> likely to pass, that will build against CDH 5.4.5. If you want release
>> tarballs I built from this, get them here:
>>
>> Binary:
>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz>
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>>
>> Source:
>> <http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz>
>> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>>
>>
>>
>>
>> The source and these binaries incorporate changes from the Cloudera Labs
>> fork of Phoenix ( <https://github.com/cloudera-labs/phoenix>
>> https://github.com/cloudera-labs/phoenix), licensed under the ASL v2,
>> Neither the source or binary artifacts are in any way "official" or
>> supported by the Apache Phoenix project. The source and artifacts are
>> provided by me in a personal capacity for the convenience of would-be
>> Phoenix users that also use CDH 5.4(.5). Please don't contact the Apache
>> Phoenix project for any issues regarding this source and these binaries.
>>
>>
>>
>>
>>
>> On Mon, Sep 14, 2015 at 10:52 AM, James Heather <
>> <ja...@mendeley.com> wrote:
>>
>> Done! Thanks for helping!
>>
>> The branches in the repo mirror those in vanilla Phoenix. We shouldn't
>> push any changes to the vanilla branches, but only to "*-cdh5" branches (or
>> any temporary side branches we need to create).
>>
>> The issue tracker will be very useful, yes.
>>
>> James
>>
>>
>>
>> On 14/09/15 17:22, Andrew Purtell wrote:
>>
>> This is great James.
>>
>>
>>
>> Since this is conveniently on Github, maybe we use the issue tracker
>> there? Interested parties can set a watch. Would you be willing to add
>> 'apurtell' as a collaborator on the repo? I will fork and send over PRs of
>> course, but you might want help?
>>
>>
>> On Sep 14, 2015, at 6:21 AM, James Heather < <ja...@mendeley.com>
>> james.heather@mendeley.com> wrote:
>>
>> I've set up a repo at
>>
>> <https://github.com/chiastic-security/phoenix-for-cloudera>
>> https://github.com/chiastic-security/phoenix-for-cloudera
>>
>> It is a fork of the vanilla Phoenix github mirror. I've created a branch
>> called "4.5-HBase-1.0-cdh5", which we can use for making a CDH5-compatible
>> version. I've not made any of the necessary changes so far.
>>
>> I chose that branch, by the way, because it's the latest release, and is
>> using the same version of HBase as CDH5.4. The master branch of the Phoenix
>> repo is building a snapshot of (the forthcoming) Phoenix 4.6, against HBase
>> 1.1... presumably there will also be a Phoenix 4.6 for HBase 1.0?
>>
>> I'm not certain of the best way to manage this. Perhaps we need a new
>> mailing list for those who want to help, to avoid cluttering this list up.
>>
>> James
>>
>> On 13/09/15 02:54, Jean-Marc Spaggiari wrote:
>>
>> Exact. There is some some code change because of what has been back
>> ported into CDH and what has not been. But overall, it should not be rocket
>> science. Mostly method signatures...
>>
>> Let us know when the repo is available so we can help...
>>
>> Thanks,
>>
>> JM
>>
>>
>>
>> 2015-09-12 18:38 GMT-04:00 Krishna < <re...@gmail.com>
>> research800@gmail.com>:
>>
>> As explained here, there are some code changes too in addition to pom
>> related changes.
>>
>>
>>
>> <http://stackoverflow.com/a/31934434/165130>
>> http://stackoverflow.com/a/31934434/165130
>>
>>
>>
>>
>>
>> On Friday, September 11, 2015, Andrew Purtell <
>> <an...@gmail.com> wrote:
>>
>> Or once parameterized, add a default off profile that redefines them all
>> in one shot after the builder activates the profile on the maven command
>> line with -P ...
>>
>>
>> On Sep 11, 2015, at 7:05 AM, Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com> wrote:
>>
>> The group IDs and versions can be parameterized in the POM so they can be
>> overridden on the maven command line with -D. That would be easy and
>> something I think we could get committed without any controversy.
>>
>>
>> On Sep 11, 2015, at 6:53 AM, James Heather < <ja...@mendeley.com>
>> james.heather@mendeley.com> wrote:
>>
>> Yes, my plan is to create a fork of the main repo, so that we can still
>> merge new Phoenix code into the CDH-compatible version.
>>
>> Before that, I do wonder whether it's possible to suggest a few changes
>> to the main repo that would allow for compiling a CDH-compatible version,
>> without needing to maintain a separate repo. The bulk of the changes are to
>> dependencies in the pom, which suggests that it could be done to accept a
>> switch to mvn build.
>>
>> James
>>
>> On 11/09/15 14:50, Andrew Purtell wrote:
>>
>> The first step I think is a repo with code that compiles. Please
>> initialize it by forking github.com/apache/phoenix so we have common
>> ancestors. Once we have a clear idea (by diff) what is required we can
>> figure out if we can support compatibility in some way.
>>
>>
>> On Sep 9, 2015, at 11:00 PM, Krishna < <re...@gmail.com>
>> research800@gmail.com> wrote:
>>
>> I can volunteer to spend some time on this.
>>
>>
>>
>> CDH artifacts are available in Maven repo but from reading other threads
>> on CDH-Phoenix compatibilty, it looks like there are some code changes to
>> be made in Phoenix to successfully compile against CDH.
>>
>>
>>
>> Here are questions to address:
>>
>> 1) How to maintain CDH compatible Phoenix code base?
>>
>> 2) Is having a CDH compatible branch even an option?
>>
>>
>> Krishna
>>
>>
>>
>>
>>
>> On Friday, August 28, 2015, Andrew Purtell < <an...@gmail.com>
>> andrew.purtell@gmail.com> wrote:
>>
>> Yes I am interested. Assuming CDH artifacts are publicly available in a
>> Maven repo somewhere, which I believe is the case, perhaps we (the Phoenix
>> project/community) could set up a Jenkins job that builds against them and
>> makes the resulting build artifacts available. They would never be an
>> official release, just a best effort convenience. Would that work? I think
>> little must be done besides compile against the CDH artifacts for binary
>> compatibility.
>>
>>
>> > On Aug 28, 2015, at 11:19 AM, James Heather <
>> <ja...@mendeley.com> wrote:
>> >
>> > Is anyone interested in helping with getting an up-to-date
>> CDH5-compatible build of Phoenix up and running?
>> >
>> > Cloudera has a build of Phoenix 4.3 (
>> <https://github.com/cloudera-labs/phoenix>
>> https://github.com/cloudera-labs/phoenix), but this is now two versions
>> behind, and there seems little desire at Cloudera to keep it updated.
>> >
>> > I imagine that by looking at the differences between vanilla 4.3 and
>> cloudera labs 4.3, and with some guidance from this list, we could get a
>> good idea of what would need to be modified in 4.5+ and keep a
>> CDH5-compatible build up to date.
>> >
>> > Yes?
>> >
>> > James
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
JM's 4.5.2 parcel for CDH5
Posted by James Heather <ja...@mendeley.com>.
I can get CDH5 to download the new parcel that JM provided. When I try
to deactivate the old (Cloudera Labs) parcel, though, I get this rather
minimalistic error message.
I thought it might be that it was still in use, so I stopped HBase and
ZooKeeper, and now it reports that no nodes are using the old parcel.
But I still get the same error when I try to deactivate.
This is the same error that I get if I try to distribute the new parcel
to the nodes (which I'd hoped to be able to do before deactivating the
old one, to minimise downtime).
Any clues?
James
On 08/10/15 18:07, Jean-Marc Spaggiari wrote:
> Can you try this repo for your installation?
>
> http://server.distparser.com:81/parcels/
>
> Don't look at the name of the files... Even if it says 4.3.0 it's
> 4.5.2 inside. Install is and launch the Phoenix command line to
> validate it.
>
> Please be aware that it's not at all supported by cloudera in anyway,
> not approved by them nor provided by them nor anything else by them ;)
>
> Those parcels work for me. I'm sure they will for you too. Please keep
> me posted.
>
> JM
>
> 2015-10-07 11:55 GMT-04:00 Kevin Verhoeven <Kevin.Verhoeven@ds-iq.com
> <ma...@ds-iq.com>>:
>
> JM,
>
> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
> Cloudera? This would be very useful if made available. Thanks for
> your time!
>
> Kevin
>
> *From:*James Heather [mailto:james.heather@mendeley.com
> <ma...@mendeley.com>]
> *Sent:* Wednesday, September 30, 2015 5:22 AM
> *To:* user@phoenix.apache.org <ma...@phoenix.apache.org>
> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>
> Hi JM,
>
> Is there a way of getting hold of the parcel you built? I'm keen
> to try it!
>
> Best wishes,
>
> James
>
> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>
> Hi James,
>
> I have been able to build a parcel and installed it on my own
> cluster. Build it with 4.5.2 that Andrew modified. I'm in
> touch with Cloudera to see what's the next steps. I will let
> you know very shortly...
>
> JM
>
> 2015-09-21 6:25 GMT-04:00 James Heather
> <james.heather@mendeley.com <ma...@mendeley.com>>:
>
> @JM how did you get on with the parcel building?
>
> Has anyone managed to get 4.5 working on CDH5 now? I was
> going to stick with 4.3 on our cluster until we had a
> parcel, but I'm now needing to use pherf, and that doesn't
> seem to exist in 4.3.
>
> James
>
> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>
> @James: I'm working on the parcel building ;) If not
> me I will try to find someone to do it. Stay tuned.
>
> @Andrewy: It works for me that way, cool! I just have
> a signature issue where it says I have no signature.
> Will that be an issue?
>
> Thanks all,
>
> JM
>
> 2015-09-16 3:24 GMT-04:00 James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>:
>
> Great! Thank you!
>
> I'd wondered about parcel building. It did look as
> though a parcel is just a .tgz, containing the
> classes and a few bits of meta, so hopefully it's
> doable. It would be really nice if we could
> provide a working 4.5 parcel.
>
> James
>
> On 16 Sep 2015 01:02, "Andrew Purtell"
> <apurtell@apache.org <ma...@apache.org>>
> wrote:
>
> I used dev/make_rc.sh, built with Maven 3.2.2,
> Java 7u79. Ubuntu build host.
>
> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc
> Spaggiari <jean-marc@spaggiari.org
> <ma...@spaggiari.org>> wrote:
>
> No, I don't know why. I will ask and see
> if I can get a respons on that. I have
> also started the thread for the Parcel. I
> will see if I find enough help to work on
> that.
>
> Regarding the branch you made, I tried to
> build it but got the error below. what's
> the command to build it?
>
> Thanks,
>
> JM
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at
> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 17 seconds
> [INFO] Finished at: Tue Sep 15 19:55:03
> EDT 2015
> [INFO] Final Memory: 134M/1648M
> [INFO]
> ------------------------------------------------------------------------
>
> 2015-09-15 19:55 GMT-04:00 Andrew Purtell
> <apurtell@apache.org
> <ma...@apache.org>>:
>
> Cool, thanks J-M.
>
> Do you know why support for query
> tracing was removed? If it's just a
> matter of porting it to the HTrace
> that ships with CDH, I can look at that.
>
> On Tue, Sep 15, 2015 at 4:49 PM,
> Jean-Marc Spaggiari
> <jean-marc@spaggiari.org
> <ma...@spaggiari.org>> wrote:
>
> Nice! I will see if there is a way
> to build a parcel from that the
> same way there is a parcel for
> Apache Phoenix 4.3 in Cloudera
> Labs... Will clone what you did
> and try to build it locally...
>
> 2015-09-15 19:45 GMT-04:00 Andrew
> Purtell <andrew.purtell@gmail.com
> <ma...@gmail.com>>:
>
> I pushed updates to branch
> 4.5-HBase-1.0-cdh5 and the tag
> v4.5.2-cdh5.4.5 (1fcb5cf).
> This is the pending Phoenix
> 4.5.2 release, currently at
> RC1, likely to pass, that will
> build against CDH 5.4.5. If
> you want release tarballs I
> built from this, get them here:
>
> Binary:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>
> Source:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>
>
> The source and these binaries
> incorporate changes from the
> Cloudera Labs fork of Phoenix
> (https://github.com/cloudera-labs/phoenix),
> licensed under the ASL v2,
> Neither the source or binary
> artifacts are in any way
> "official" or supported by the
> Apache Phoenix project. The
> source and artifacts are
> provided by me in a personal
> capacity for the convenience
> of would-be Phoenix users that
> also use CDH 5.4(.5). Please
> don't contact the Apache
> Phoenix project for any issues
> regarding this source and
> these binaries.
>
>
>
> On Mon, Sep 14, 2015 at 10:52
> AM, James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> Done! Thanks for helping!
>
> The branches in the repo
> mirror those in vanilla
> Phoenix. We shouldn't push
> any changes to the vanilla
> branches, but only to
> "*-cdh5" branches (or any
> temporary side branches we
> need to create).
>
> The issue tracker will be
> very useful, yes.
>
> James
>
> On 14/09/15 17:22, Andrew
> Purtell wrote:
>
> This is great James.
>
> Since this is
> conveniently on
> Github, maybe we use
> the issue tracker
> there? Interested
> parties can set a
> watch. Would you be
> willing to add
> 'apurtell' as a
> collaborator on the
> repo? I will fork and
> send over PRs of
> course, but you might
> want help?
>
>
> On Sep 14, 2015, at
> 6:21 AM, James Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> I've set up a repo at
>
> https://github.com/chiastic-security/phoenix-for-cloudera
>
> It is a fork of
> the vanilla
> Phoenix github
> mirror. I've
> created a branch
> called
> "4.5-HBase-1.0-cdh5",
> which we can use
> for making a
> CDH5-compatible
> version. I've not
> made any of the
> necessary changes
> so far.
>
> I chose that
> branch, by the
> way, because it's
> the latest
> release, and is
> using the same
> version of HBase
> as CDH5.4. The
> master branch of
> the Phoenix repo
> is building a
> snapshot of (the
> forthcoming)
> Phoenix 4.6,
> against HBase
> 1.1... presumably
> there will also be
> a Phoenix 4.6 for
> HBase 1.0?
>
> I'm not certain of
> the best way to
> manage this.
> Perhaps we need a
> new mailing list
> for those who want
> to help, to avoid
> cluttering this
> list up.
>
> James
>
> On 13/09/15 02:54,
> Jean-Marc
> Spaggiari wrote:
>
> Exact. There
> is some some
> code change
> because of
> what has been
> back ported
> into CDH and
> what has not
> been. But
> overall, it
> should not be
> rocket
> science.
> Mostly method
> signatures...
>
> Let us know
> when the repo
> is available
> so we can help...
>
> Thanks,
>
> JM
>
> 2015-09-12
> 18:38
> GMT-04:00
> Krishna
> <research800@gmail.com
> <ma...@gmail.com>>:
>
> As
> explained
> here,
> there are
> some code
> changes
> too in
> addition
> to pom
> related
> changes.
>
> http://stackoverflow.com/a/31934434/165130
>
>
>
> On Friday,
> September
> 11, 2015,
> Andrew
> Purtell
> <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> Or
> once
> parameterized,
> add a
> default off
> profile that
> redefines
> them
> all in
> one
> shot
> after
> the
> builder activates
> the
> profile on
> the
> maven
> command line
> with
> -P ...
>
>
> On Sep
> 11,
> 2015,
> at
> 7:05
> AM,
> Andrew
> Purtell <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> The group
> IDs and
> versions
> can be
> parameterized
> in
> the POM
> so
> they
> can be
> overridden
> on
> the maven
> command
> line
> with
> -D. That
> would
> be
> easy
> and something
> I
> think
> we
> could
> get committed
> without
> any controversy.
>
>
>
> On
> Sep 11,
> 2015,
> at
> 6:53
> AM, James
> Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
>
> Yes,
> my
> plan
> is
> to
> create
> a fork
> of
> the
> main
> repo,
> so
> that
> we
> can
> still
> merge
> new
> Phoenix
> code
> into
> the
> CDH-compatible
> version.
>
> Before
> that,
> I do
> wonder
> whether
> it's
> possible
> to
> suggest
> a few
> changes
> to
> the
> main
> repo
> that
> would
> allow
> for
> compiling
> a CDH-compatible
> version,
> without
> needing
> to
> maintain
> a separate
> repo.
> The
> bulk
> of
> the
> changes
> are
> to
> dependencies
> in
> the
> pom,
> which
> suggests
> that
> it
> could
> be
> done
> to
> accept
> a switch
> to
> mvn
> build.
>
> James
>
> On
> 11/09/15
> 14:50,
> Andrew
> Purtell
> wrote:
>
> The
> first
> step
> I think
> is
> a repo
> with
> code
> that
> compiles.
> Please
> initialize
> it
> by
> forking
> github.com/apache/phoenix
> <http://github.com/apache/phoenix>
> so
> we
> have
> common
> ancestors.
> Once
> we
> have
> a clear
> idea
> (by
> diff)
> what
> is
> required
> we
> can
> figure
> out
> if
> we
> can
> support
> compatibility
> in
> some
> way.
>
>
> On
> Sep
> 9,
> 2015,
> at
> 11:00
> PM,
> Krishna
> <research800@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> I can
> volunteer
> to
> spend
> some
> time
> on
> this.
>
>
> CDH
> artifacts
> are
> available
> in
> Maven
> repo
> but
> from reading
> other
> threads
> on
> CDH-Phoenix
> compatibilty,
> it
> looks
> like
> there
> are
> some
> code
> changes
> to
> be
> made
> in
> Phoenix
> to
> successfully compile
> against
> CDH.
>
>
> Here
> are
> questions
> to
> address:
>
> 1)
> How
> to
> maintain
> CDH
> compatible
> Phoenix
> code
> base?
>
>
> 2)
> Is
> having
> a CDH
> compatible
> branch
> even
> an
> option?
>
>
> Krishna
>
>
>
> On
> Friday,
> August
> 28,
> 2015,
> Andrew
> Purtell
> <andrew.purtell@gmail.com
> <ma...@gmail.com>>
> wrote:
>
> Yes
> I am
> interested.
> Assuming
> CDH
> artifacts
> are
> publicly
> available
> in
> a Maven
> repo
> somewhere,
> which
> I believe
> is
> the
> case,
> perhaps
> we
> (the
> Phoenix
> project/community)
> could
> set
> up
> a Jenkins
> job
> that
> builds
> against
> them
> and
> makes
> the
> resulting
> build
> artifacts
> available.
> They
> would
> never
> be
> an
> official
> release,
> just
> a best
> effort
> convenience.
> Would
> that
> work?
> I think
> little
> must
> be
> done
> besides
> compile
> against
> the
> CDH
> artifacts
> for
> binary
> compatibility.
>
>
> > On
> Aug
> 28,
> 2015,
> at
> 11:19
> AM,
> James
> Heather
> <james.heather@mendeley.com
> <ma...@mendeley.com>>
> wrote:
> >
> > Is
> anyone
> interested
> in
> helping
> with
> getting
> an
> up-to-date
> CDH5-compatible
> build
> of
> Phoenix
> up
> and
> running?
> >
> > Cloudera
> has
> a build
> of
> Phoenix
> 4.3
> (https://github.com/cloudera-labs/phoenix),
> but
> this
> is
> now
> two
> versions
> behind,
> and
> there
> seems
> little
> desire
> at
> Cloudera
> to
> keep
> it
> updated.
> >
> > I
> imagine
> that
> by
> looking
> at
> the
> differences
> between
> vanilla
> 4.3
> and
> cloudera
> labs
> 4.3,
> and
> with
> some
> guidance
> from
> this
> list,
> we
> could
> get
> a good
> idea
> of
> what
> would
> need
> to
> be
> modified
> in
> 4.5+
> and
> keep
> a CDH5-compatible
> build
> up
> to
> date.
> >
> > Yes?
> >
> > James
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their
> worth by hitting back. - Piet Hein
> (via Tom White)
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by
> hitting back. - Piet Hein (via Tom White)
>
>
Re: setting up community repo of Phoenix for CDH5?
Posted by Jean-Marc Spaggiari <je...@spaggiari.org>.
Can you try this repo for your installation?
http://server.distparser.com:81/parcels/
Don't look at the name of the files... Even if it says 4.3.0 it's 4.5.2
inside. Install is and launch the Phoenix command line to validate it.
Please be aware that it's not at all supported by cloudera in anyway, not
approved by them nor provided by them nor anything else by them ;)
Those parcels work for me. I'm sure they will for you too. Please keep me
posted.
JM
2015-10-07 11:55 GMT-04:00 Kevin Verhoeven <Ke...@ds-iq.com>:
> JM,
>
>
>
> If possible, I’d also like to try your 4.5.2 Parcel. Any luck with
> Cloudera? This would be very useful if made available. Thanks for your time!
>
>
>
> Kevin
>
>
>
> *From:* James Heather [mailto:james.heather@mendeley.com]
> *Sent:* Wednesday, September 30, 2015 5:22 AM
> *To:* user@phoenix.apache.org
> *Subject:* Re: setting up community repo of Phoenix for CDH5?
>
>
>
> Hi JM,
>
> Is there a way of getting hold of the parcel you built? I'm keen to try it!
>
> Best wishes,
>
> James
>
> On 21/09/15 14:00, Jean-Marc Spaggiari wrote:
>
> Hi James,
>
> I have been able to build a parcel and installed it on my own cluster.
> Build it with 4.5.2 that Andrew modified. I'm in touch with Cloudera to see
> what's the next steps. I will let you know very shortly...
>
> JM
>
>
>
> 2015-09-21 6:25 GMT-04:00 James Heather <ja...@mendeley.com>:
>
> @JM how did you get on with the parcel building?
>
> Has anyone managed to get 4.5 working on CDH5 now? I was going to stick
> with 4.3 on our cluster until we had a parcel, but I'm now needing to use
> pherf, and that doesn't seem to exist in 4.3.
>
> James
>
>
>
> On 16/09/15 12:46, Jean-Marc Spaggiari wrote:
>
> @James: I'm working on the parcel building ;) If not me I will try to find
> someone to do it. Stay tuned.
>
> @Andrewy: It works for me that way, cool! I just have a signature issue
> where it says I have no signature. Will that be an issue?
>
> Thanks all,
>
> JM
>
>
>
> 2015-09-16 3:24 GMT-04:00 James Heather <ja...@mendeley.com>:
>
> Great! Thank you!
>
> I'd wondered about parcel building. It did look as though a parcel is just
> a .tgz, containing the classes and a few bits of meta, so hopefully it's
> doable. It would be really nice if we could provide a working 4.5 parcel.
>
> James
>
> On 16 Sep 2015 01:02, "Andrew Purtell" <ap...@apache.org> wrote:
>
> I used dev/make_rc.sh, built with Maven 3.2.2, Java 7u79. Ubuntu build
> host.
>
>
>
>
>
> On Tue, Sep 15, 2015 at 4:58 PM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org> wrote:
>
> No, I don't know why. I will ask and see if I can get a respons on that. I
> have also started the thread for the Parcel. I will see if I find enough
> help to work on that.
>
> Regarding the branch you made, I tried to build it but got the error
> below. what's the command to build it?
>
> Thanks,
>
> JM
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.plugin.surefire.report.DefaultReporterFactory.mergeFromOtherFactories(DefaultReporterFactory.java:82)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:182)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1019)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:853)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:751)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 17 seconds
> [INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015
> [INFO] Final Memory: 134M/1648M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> 2015-09-15 19:55 GMT-04:00 Andrew Purtell <ap...@apache.org>:
>
> Cool, thanks J-M.
>
>
>
> Do you know why support for query tracing was removed? If it's just a
> matter of porting it to the HTrace that ships with CDH, I can look at that.
>
>
>
>
>
> On Tue, Sep 15, 2015 at 4:49 PM, Jean-Marc Spaggiari <
> jean-marc@spaggiari.org> wrote:
>
> Nice! I will see if there is a way to build a parcel from that the same
> way there is a parcel for Apache Phoenix 4.3 in Cloudera Labs... Will clone
> what you did and try to build it locally...
>
>
>
> 2015-09-15 19:45 GMT-04:00 Andrew Purtell <an...@gmail.com>:
>
> I pushed updates to branch 4.5-HBase-1.0-cdh5 and the tag v4.5.2-cdh5.4.5
> (1fcb5cf). This is the pending Phoenix 4.5.2 release, currently at RC1,
> likely to pass, that will build against CDH 5.4.5. If you want release
> tarballs I built from this, get them here:
>
> Binary:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-bin.tar.gz
>
> Source:
> http://apurtell.s3.amazonaws.com/phoenix/phoenix-4.5.2-cdh5.4.5-src.tar.gz
>
>
>
>
> The source and these binaries incorporate changes from the Cloudera Labs
> fork of Phoenix (https://github.com/cloudera-labs/phoenix), licensed
> under the ASL v2, Neither the source or binary artifacts are in any way
> "official" or supported by the Apache Phoenix project. The source and
> artifacts are provided by me in a personal capacity for the convenience of
> would-be Phoenix users that also use CDH 5.4(.5). Please don't contact the
> Apache Phoenix project for any issues regarding this source and these
> binaries.
>
>
>
>
>
> On Mon, Sep 14, 2015 at 10:52 AM, James Heather <
> james.heather@mendeley.com> wrote:
>
> Done! Thanks for helping!
>
> The branches in the repo mirror those in vanilla Phoenix. We shouldn't
> push any changes to the vanilla branches, but only to "*-cdh5" branches (or
> any temporary side branches we need to create).
>
> The issue tracker will be very useful, yes.
>
> James
>
>
>
> On 14/09/15 17:22, Andrew Purtell wrote:
>
> This is great James.
>
>
>
> Since this is conveniently on Github, maybe we use the issue tracker
> there? Interested parties can set a watch. Would you be willing to add
> 'apurtell' as a collaborator on the repo? I will fork and send over PRs of
> course, but you might want help?
>
>
> On Sep 14, 2015, at 6:21 AM, James Heather <ja...@mendeley.com>
> wrote:
>
> I've set up a repo at
>
> https://github.com/chiastic-security/phoenix-for-cloudera
>
> It is a fork of the vanilla Phoenix github mirror. I've created a branch
> called "4.5-HBase-1.0-cdh5", which we can use for making a CDH5-compatible
> version. I've not made any of the necessary changes so far.
>
> I chose that branch, by the way, because it's the latest release, and is
> using the same version of HBase as CDH5.4. The master branch of the Phoenix
> repo is building a snapshot of (the forthcoming) Phoenix 4.6, against HBase
> 1.1... presumably there will also be a Phoenix 4.6 for HBase 1.0?
>
> I'm not certain of the best way to manage this. Perhaps we need a new
> mailing list for those who want to help, to avoid cluttering this list up.
>
> James
>
> On 13/09/15 02:54, Jean-Marc Spaggiari wrote:
>
> Exact. There is some some code change because of what has been back ported
> into CDH and what has not been. But overall, it should not be rocket
> science. Mostly method signatures...
>
> Let us know when the repo is available so we can help...
>
> Thanks,
>
> JM
>
>
>
> 2015-09-12 18:38 GMT-04:00 Krishna <re...@gmail.com>:
>
> As explained here, there are some code changes too in addition to pom
> related changes.
>
>
>
> http://stackoverflow.com/a/31934434/165130
>
>
>
>
>
> On Friday, September 11, 2015, Andrew Purtell <an...@gmail.com>
> wrote:
>
> Or once parameterized, add a default off profile that redefines them all
> in one shot after the builder activates the profile on the maven command
> line with -P ...
>
>
> On Sep 11, 2015, at 7:05 AM, Andrew Purtell <an...@gmail.com>
> wrote:
>
> The group IDs and versions can be parameterized in the POM so they can be
> overridden on the maven command line with -D. That would be easy and
> something I think we could get committed without any controversy.
>
>
> On Sep 11, 2015, at 6:53 AM, James Heather <ja...@mendeley.com>
> wrote:
>
> Yes, my plan is to create a fork of the main repo, so that we can still
> merge new Phoenix code into the CDH-compatible version.
>
> Before that, I do wonder whether it's possible to suggest a few changes to
> the main repo that would allow for compiling a CDH-compatible version,
> without needing to maintain a separate repo. The bulk of the changes are to
> dependencies in the pom, which suggests that it could be done to accept a
> switch to mvn build.
>
> James
>
> On 11/09/15 14:50, Andrew Purtell wrote:
>
> The first step I think is a repo with code that compiles. Please
> initialize it by forking github.com/apache/phoenix so we have common
> ancestors. Once we have a clear idea (by diff) what is required we can
> figure out if we can support compatibility in some way.
>
>
> On Sep 9, 2015, at 11:00 PM, Krishna <re...@gmail.com> wrote:
>
> I can volunteer to spend some time on this.
>
>
>
> CDH artifacts are available in Maven repo but from reading other threads
> on CDH-Phoenix compatibilty, it looks like there are some code changes to
> be made in Phoenix to successfully compile against CDH.
>
>
>
> Here are questions to address:
>
> 1) How to maintain CDH compatible Phoenix code base?
>
> 2) Is having a CDH compatible branch even an option?
>
>
> Krishna
>
>
>
>
>
> On Friday, August 28, 2015, Andrew Purtell <an...@gmail.com>
> wrote:
>
> Yes I am interested. Assuming CDH artifacts are publicly available in a
> Maven repo somewhere, which I believe is the case, perhaps we (the Phoenix
> project/community) could set up a Jenkins job that builds against them and
> makes the resulting build artifacts available. They would never be an
> official release, just a best effort convenience. Would that work? I think
> little must be done besides compile against the CDH artifacts for binary
> compatibility.
>
>
> > On Aug 28, 2015, at 11:19 AM, James Heather <ja...@mendeley.com>
> wrote:
> >
> > Is anyone interested in helping with getting an up-to-date
> CDH5-compatible build of Phoenix up and running?
> >
> > Cloudera has a build of Phoenix 4.3 (
> https://github.com/cloudera-labs/phoenix), but this is now two versions
> behind, and there seems little desire at Cloudera to keep it updated.
> >
> > I imagine that by looking at the differences between vanilla 4.3 and
> cloudera labs 4.3, and with some guidance from this list, we could get a
> good idea of what would need to be modified in 4.5+ and keep a
> CDH5-compatible build up to date.
> >
> > Yes?
> >
> > James
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
>
>
>
>
>
>
> --
>
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
>
>
>
>
>
>
>
>