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 :(
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 :
> @JM
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"
@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
@J-M, don't worry about signing the output, it won't be an issue.
On Wed, Sep 16, 2015 at 4:46 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> 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
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 :
> I pushed updates to branch
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-m...@spaggiari.org> wrote:
> Nice! I will see if there is a way to
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
On Mon, Sep 14, 2015 at 9:21 AM, James Heather
wrote:
> 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.
Just my opinion, but maybe a tag in the email subject,
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
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,
Sorry, yes, it does make a couple of very minor source changes.
I do wonder whether ultimately we'll be able to get those into the main
repo as conditionals somehow, but let's get the repo up and running first.
James
On 13 Sep 2015 8:47 am, "James Heather" wrote:
>
OK, I'd held off doing it on Friday because I'd thought it might be doable
just as dependency changes in the pom. I'll set the repo up tomorrow when
I'm back in the office.
The SO page doesn't talk about specific code changes, but perhaps they're
implicit in the replacement of the jar files.
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
wrote:
> Or once parameterized, add a default off profile that redefines them all
> in one
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
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,
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 wrote:
>
Let me know when you have setup the repo; I am aware of the code changes to
make for CDH compatibility. stack overflow also has details.
On Wed, Sep 9, 2015 at 11:08 PM, James Heather
wrote:
> Thanks! I'll set up a repo today, and we can see how far we get with it.
>
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
Thanks! I'll set up a repo today, and we can see how far we get with it.
Another recent thread points to a stack overflow answer with some clues.
On 10 Sep 2015 7:00 am, "Krishna" wrote:
> I can volunteer to spend some time on this.
>
> CDH artifacts are available in
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
21 matches
Mail list logo