Thanks everyone!
Happy to join the ranks, and I'm looking forward to helping out more :)
James Taylor wrote:
On behalf of the Apache Phoenix PMC, I'm pleased to announce that Josh
Elser has accepted our invitation to become a committer on the Apache
Phoenix project. He's done a
epareAndExecute" not "prepareAndExecuteBatch".
Josh Elser wrote:
Thanks, will fix this.
Plamen Paskov wrote:
Ah i found the error. It should be "sqlCommands": instead of
"sqlCommands",
The documentation syntax is wrong for this request type:
http://calcite.apache.org/avatica
*tl;dr*
* I'm removing ubuntu-us1 from all pools
* Phoenix-Flume ITs look busted
* UpsertValuesIT looks busted
* Something is weirdly wrong with Phoenix-4.x-HBase-1.1 in its entirety.
Details below...
It looks like we have a bunch of different reasons for the failures.
Starting with Phoenix-ma
Also, didn't mean to ignore you Sergey. I haven't seen anything at the
moment which pointed to getting more info from -X (general flakiness
from the ASF jenkins boxes is... the norm).
We can definitely do this if we think there is something concrete that
we're missing.
Sergey Soldatov wrote:
Hi Naveen,
The Protocol Buffer dependency on 2.5 is very unlikely to change in
Phoenix as that is directly inherited from HBase (as you can imagine,
these need to be kept in sync).
There are efforts, in both HBase and Phoenix, underway to provide
shaded-jars for each project which would allo
Congrats and well deserved, Ankit!
James Taylor wrote:
On behalf of the Apache Phoenix PMC, I'm pleased to announce that Ankit
Singhal has accepted our invitation to become a member of the Apache
Phoenix project management committee (PMC). Recently he's implemented two
of the most asked for feat
ache.commons.io.Charsets
which
was
introduced in 2.3. Easy way is to move dependency on
flume-ng
after
the dependencies on hbase/hadoop.
The last thing about ConcurrentHashMap - it definitely
means
that
the
code was compiled with 1.8 since 1.7 returns a simple Set
while
1.8
returns Ke
+1 VOTE is ongoing over on dev@calcite.a.o for an Avatica 1.8.0 (anyone
with a binding vote over there would be appreciated too) This would be a
nice gain for Phoenix-4.8 (perf improvements, new features, better docs,
etc).
I can try to help knock out some of those issues you mentioned as well
How did you install HDFS and HBase and what versions of each did you
use? It looks like you might somehow have incompatible libraries.
I also haven't seen any message from you on the hbase lists (user or
dev). Make sure you subscribe to the user@ list before posting.
Pranavan Theivendiram wro
:
Please find the answers inline.
On 2 June 2016 at 21:22, Josh Elser mailto:josh.el...@gmail.com>> wrote:
How did you install HDFS and HBase and what versions of each did you
use? It looks like you might somehow have incompatible libraries.
Hadoop - 2.6.4
Zookeeper - 3.4.8
Hbase -
6 at 22:04, Josh Elser mailto:josh.el...@gmail.com>> wrote:
Did you download tarballs from Apache? Some vendor?
If you downloaded the Apache HBase 1.2.1 binary tarball, you will
have hadoop-2.5.1 jars on the HBase classpath. It would be good to
make sure you have consistent v
A NoNode error is not a failure condition. HBase regularly makes
decisions on whether or not nodes actually exist in HBase...
Josh Elser wrote:
Please keep all conversations on the mailing list.
Pranavan Theivendiram wrote:
Hi Josh. I had hadoop-2.5.1 jars. I replaced the old jars with new
eport
problems and get involved, visit the project website at:
https://calcite.apache.org/avatica/
or the Apache Calcite project website:
https://calcite.apache.org/
Thanks to everyone involved!
Josh Elser, on behalf of the Apache Calcite team.
ursday EOD?
Checked with Rajesh too , PHOENIX-1734 is also ready for 4.x branches
and
will be committed by tomorrow.
Regards,
Ankit Singhal
On Wed, Jun 1, 2016 at 12:33 PM, Nick Dimiduk
wrote:
On Wed, Jun 1, 2016 at 10:58 AM, Josh Elser
wrote:
I can try to help knock out some of those issu
We can try, but, IMO, it's not likely that we'll get a very positive
answer from them.
Better use of time would probably be trying to identify if there are
certain nodes which are flakey (and just avoid them completely) and if
there is anything we can do to stabilize the tests (reduce number o
Just an FYI: I re-opened PHOENIX-3025. It seems like this broke PQS
somehow (PQS still expecting to find Guava in the o.a.phoenix.shaded
package). Might just be something to fix at build time (hopefully,
anyways) -- I'm looking at it now.
rajeshb...@apache.org wrote:
I think PHOENIX-3045 is b
-1 (non-binding) from me with my Phoenix hat on (avoiding putting on the
ASF member hat for now). Lots of wrong licensing stuff in here -- as-in,
this should very definitely not go out as a release. I hope the Phoenix
PMC steps up to -1 this release on their own.
*** Source release:
Good:
* M
LICENSE and
NOTICE files using templates and velocity macros. Sean Busbey did the
lion's share of the work. Refer to
https://issues.apache.org/jira/browse/HBASE-14085 . It was a significant
effort.
On Jul 17, 2016, at 10:53 AM, Josh Elser wrote:
-1 (non-binding) from me with my Phoenix h
On Jul 17, 2016, at 10:53 AM, Josh Elser wrote:
-1 (non-binding) from me with my Phoenix hat on (avoiding putting on the ASF
member hat for now). Lots of wrong licensing stuff in here -- as-in, this
should very definitely not go out as a release. I hope the Phoenix PMC steps up
to -1 this rel
You can check the dev list for the VOTE thread which contains a link to
the release candidate but it is not an official Apache Phoenix release yet.
Vasanth Bhat wrote:
Thanks a lot Ankit.
where do I download this from? I am looking at
http://mirror.fibergrid.in/apache/phoenix/don't seem
Ankit Singhal wrote:
@Josh, bq. Bad:
* SHA1 xsum is wrong. It looks like complete nonsense to me, but I
can't find the appropriate xsum in that file (which was
64208164580f3467cd2c8b51c0d9f8ac37f0c671)
In Phoenix , we don't use SHA1 , SHA files has only SHA-512 and
SHA-256 hashes
Sean Busbey wrote:
On Mon, Jul 18, 2016 at 12:05 PM, Ankit Singhal
wrote:
Now we have three options to go forward with 4.8 release (or whether to
include licenses and notices for the dependency used now or later):-
*Option 1:- Go with this RC0 for 4.8 release.*
-- As the build is func
(Moving this over to its own thread to avoid bogging down the VOTE further)
PMC, what say you? I have cycles to work on this now.
Original Message
Subject: Re: [VOTE] Release of Apache Phoenix 4.8.0-HBase-1.2 RC0
Date: Mon, 18 Jul 2016 14:43:54 -0400
From: Josh Elser
To: dev
issue. Option 1 is not a
good option. Let's go with another.
On Jul 18, 2016, at 1:53 PM, Josh Elser wrote:
(Moving this over to its own thread to avoid bogging down the VOTE further)
PMC, what say you? I have cycles to work on this now.
Original Message
Subject: Re: [VOT
t;>> >
>>> > 0.98: pass with four +1s
>>> > 1.0: pass with four +1s
>>> > 1.1: fail with two +1s
>>> > 1.2: pass with three +1s, one -1, and one non-binding -1
>>> >
>>> > This presumes I did not miss a vote c
legal/resolved.html#category-x
[2] https://issues.apache.org/jira/browse/PHOENIX-3101
[3] https://issues.apache.org/jira/browse/PHOENIX-3102
James Taylor wrote:
Ok, that's great then. We can just combine the separate vote emails into
one then. Much easier.
Thanks,
James
On Tuesday, July 19, 2016,
ppropriate.
Meanwhile, I'll run a few tests myself to make sure the code is still
working as intended :)
Josh Elser wrote:
A quick update from me for those not watching the JIRA issues:
I've found two LGPL dependencies that have been bundled in the binary
artifact which *must* not be incl
Sean Busbey was a fine gent and gave me some great feedback this
morning. I think it's in a good place -- does anyone else want to look
at it before I merge it?
Josh Elser wrote:
From a packaging perspective, I think this is good to go.
https://github.com/apache/phoenix/pull/183
I
at 11:16 AM, Josh Elser wrote:
Sean Busbey was a fine gent and gave me some great feedback this morning.
I think it's in a good place -- does anyone else want to look at it before
I merge it?
Josh Elser wrote:
From a packaging perspective, I think this is good to go.
https://github.
Yep, dev/make_rc.sh will build artifacts which, to the best of my
knowledge, are fully compliant with ASF guidelines.
No need to remove anything.
James Taylor wrote:
I believe Josh fixed all the licensing issues, including the ones for
the trace UI. Can you confirm, Josh?
I don't think PHOENI
I just filed https://issues.apache.org/jira/browse/PHOENIX-3136. This
one is pretty serious IMO and I plan to get a patch up and tested within
the next hour or so. Sorry for the last-minute-ness of it.
tl;dr The shading changes broke backwards wire compatibility of PQS due
to how the Avatica w
Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
just noticed that we have the same Maven versions on both the 4.8 and
4.x branch sets.
Ankit Singhal wrote:
Following 4 branches have been created and are now available for commits
targeted for 4.8.0 only.
4.8-HBase-0.98
in the release. Maybe we should just delete
the 4.8 branches and recreate them once the RC is up?
On Tue, Aug 2, 2016 at 8:28 AM, Josh Elser wrote:
Shouldn't we bump the 4.x and master branch to 4.9.0-HBase**-SNAPSHOT? I
just noticed that we have the same Maven versions on both the 4.8 and 4.x
+1 (non-binding)
* xsums/sigs match
* KEYS published and contains key used for signing
* `mvn apache-rat:check package` passes on each src tarball
* Skimmed L&N for each to verify contents looked correct (trusting
past-Josh for the most part, see caveat below).
The (non-blocker) worries/findin
Thank you all! I look forward to working more closely with everyone :D
James Taylor wrote:
On behalf of the Apache Phoenix PMC, I'm pleased to announce that Josh
Elser has accepted our invitation to become a member of the Apache Phoenix
PMC. Recently he found and fixed licensing-related i
+1 (binding)
* apache-rat:check OK
* Couldn't find any unexpected binaries
* Could build from source
* xsums/sigs OK
* Could run all UTs
Will try to do some more later today. Thanks all for getting this put
together.
On 10/4/17 3:46 AM, James Taylor wrote:
Hello Everyone,
This is a call for
+1 to the "getting lighter" sentiment.
Selectively bringing back stuff to 0.98 is a nice way to keep the burden
low.
On 10/10/17 1:32 PM, James Taylor wrote:
I'm -1 on a shim layer for 0.98. It would needlessly complicate the code
when all we need for the 0.98 branch are critical bug fixes. I
I'm still mulling this over, but my first reaction is that I think this
is an acceptable solution going forward (agreeing with your "lighter
burden" sentiments in the other thread).
Would kindly request a few days to give it some thought before we make
any decisions.
On 10/11/17 12:59 PM, Ja
Since 4.12.0 is out and we have the concurrent discussions about the
0.98, 1.1, and 1.2 HBase branches, do folks have a vision of how we get
to HBase 2.0.0?
The lack of chatter is pretty obvious that the Calcite work (the
previous impetus for Phoenix 5) has slowed. Once we get to an HBase
2.0
Congrats Vincent!
On 10/11/17 9:51 PM, James Taylor wrote:
On behalf of the Apache Phoenix PMC, I'm delighted to announce that Vincent
Poon has accepted our invitation to become a committer. He's had a big
impact in helping to stabilize our secondary index implementation,
including the creation
Congrats Ethan!
On 10/11/17 9:45 PM, James Taylor wrote:
On behalf of the Apache Phoenix PMC, I'm please to announce that Ethan Wang
has accepted our invitation to become a committer. He's behind some of the
great new 4.12 features of table sampling [1] and approximate count
distinct [2] along w
se an umbrella issue once we have a plan for the
version based on HBase 2.0
-Anoop-
On Thu, Oct 12, 2017 at 3:30 AM, Josh Elser wrote:
Since 4.12.0 is out and we have the concurrent discussions about the 0.98,
1.1, and 1.2 HBase branches, do folks have a vision of how we get to HBase
2.0.0?
The
5.0-HBase-2.0 the master branch
Thoughts?
On Fri, Oct 13, 2017 at 8:31 AM, Josh Elser wrote:
Thanks, Anoop!
I know Sergey, Ankit, and Rajeshbabu have been looking at this already.
While tracking it is good, I think we still need to come up with a plan
for where we're going to put that n
ill be the last release (though I'm still not
sure that DISCUSS thread has reached a conclusion).
On Wed, Oct 11, 2017 at 2:54 PM Josh Elser wrote:
I'm still mulling this over, but my first reaction is that I think this
is an acceptable solution going forward (agreeing with your "lig
release alpha4 which is supposed to be locked-down internal and external
API -- but better late than never.
Thanks,
St.Ack
1. https://docs.google.com/document/d/10cabwp_
aR3OmpHVoeh544YLC3KwqMD9KiTIrHZAmfec/edit#heading=h.7swwa1jl6wiw
On Wed, Oct 11, 2017 at 3:00 PM, Josh Elser wrote:
On 10/18/17 2:51 PM, Andrew Purtell wrote:
Hopefully, Phoenix will not find itself in a position where
business-critical things it's doing are being removed from API (and Phoenix
has no recourse to hack what it needs back in place).
I feel fairly confident this is going to happen given the rad
/test-failure).
I wanted to make sure that folks who had the time/interest to contribute
to the not-so-fun effort were able to ;). Will share a branch name when
I see it.
On 10/11/17 6:00 PM, Josh Elser wrote:
Since 4.12.0 is out and we have the concurrent discussions about the
0.98, 1.1, and
Just went ahead and did it. No problem from my POV.
On 10/31/17 1:54 PM, James Taylor wrote:
I propose we rename the 5.0-HBase-2.0 branch to 5.x-HBase-2.0 so that we
can do all 5.x based releases from this branch similar to the way we do for
4.x-HBase-###.
+1 (binding)
* Can build from source and run unit tests
* No new deps since 4.12 (implies L&N is still good)
* 4.13 tags are deployed and match
* No unexpected files in src releases
On 11/3/17 6:21 PM, James Taylor wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 4.13.0 RC0.
ylor wrote:
Thanks for the vote, Josh, but FYI there is a new dependency
with com.salesforce.i18n:i18n-util that went in with PHOENIX-4237.
On Fri, Nov 3, 2017 at 8:23 PM, Josh Elser wrote:
+1 (binding)
* Can build from source and run unit tests
* No new deps since 4.12 (implies L&N is still goo
let's fix this. Should be quick to do and if the only change then
everyone should be comfortable carrying forward their votes based on
functional testing.
On Mon, Nov 6, 2017 at 9:18 AM, Josh Elser wrote:
Thanks for the correction, James. This wasn't added to
dependencyManagement, s
+1
On 11/6/17 6:47 PM, James Taylor wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 4.13.0 RC1. This is the next
minor release of Phoenix 4, compatible with Apache HBase 0.98 and 1.3. The
release includes both a source-only release and a convenience binary
release for each su
If it's not too onerous, I think it would be good!
The 5.x-HBase-2.0 branch has definitely been stabilized recently (thanks
to the great work by Sergey, Ankit, and Rajeshbabu). If it is a pain
(e.g. PreCommit broken, Tests broken, other), we can just plan to review
it again later.
On 12/5/17
If you want to use Phoenix, please use Phoenix APIs to read and write
the data.
You are wholly responsible for understanding how to correctly write the
data given Phoenix's schema if you bypass it.
On 12/13/17 9:25 AM, Oussama BEN BACCAR wrote:
Hello Phoenixers,
I have a rowkey issue when i
+1 I've used that library with success in the past.
You may also find the list of Requests/Responses helpful:
https://calcite.apache.org/avatica/docs/protobuf_reference.html. There
is a single HTTP endpoint which these are submitted to. Looking at a
tcpdump of the thin JDBC driver or the sourc
Happy New Year folks!
I'd like to test the waters: what do people think about trying to get a
5.0.0 "beta" release out to the community before the end of January?
HBase is doing the same right now with 2.0.0. My thinking is that if
things are stable "enough", getting a base for people to use
PHOENIX-4515 PHOENIX-4516)
* Tephra integration: Needs a new release of Tephra with some fixes
Ankit helped with.
I plan to not consider these 5.0.0-alpha/beta release blockers, we'll
just call those out which we don't get tested/fixed.
On 1/2/18 1:08 PM, Josh Elser wrote:
Happy New
"base Phoenix".
On Thu, Jan 4, 2018 at 8:34 AM Josh Elser wrote:
Talked to Rajeshbabu and Ankit offline this morning.
Sounds like there are a few integration points which are still lacking:
* phoenix-hive: PHOENIX-4423
* phoenix-spark: untested (probably broken against newest Spark)
*
:57 AM, Josh Elser wrote:
Good point. Perhaps "alpha" would be a better label?
IIUC, the issue is that we need the HBase release, and then a Tephra
release, and then we can get Tephra fixed for Phoenix5. Perhaps Ankit can
provide some more color to the situation.
On 1/4/18 12:07 PM,
ranches? That'll probably help minimize the merge conflicts we see going
forward.
On Thu, Jan 18, 2018 at 1:03 PM, James Taylor
wrote:
Awesome! That's great work!!
On Thu, Jan 18, 2018 at 1:00 PM, Josh Elser wrote:
Hah, funny you should ask! I was just thinking that I should send out a
n
Hi Hidir,
In most (maybe all) cases, Phoenix (thick) driver configuration
properties can also be picked up off of the classpath via hbase-site.xml.
For tools that allow you to specify additional classpath elements, you
can add the directory containing hbase-site.xml with your configuration
p
Sorry, haven't been working through my inbox and I left a half-hearted
comment on a JIRA at James' ping.
My understanding is that the recent JIRA update that infra executed
broke our "old" PreCommit by changing some of the API that it was using.
Yetus 0.7.0 was just released which was intende
push out an RC.
- Josh
On Mon, Jan 22, 2018 at 7:32 PM, Josh Elser wrote:
> I don't think so. We (I use that loosely -- I'd hardly lump my contributions
> to this effort in the same room as the contributions of the others) have
> been moving fast to get back to functional s
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc0. This
release is only targeting Apache HBase 2.0 and is known to have lacking
functionality as compared to previous releases (e.g. transactional
tables, Hive integration, full local indexing support). It is presented
https://issues.apache.org/jira/browse/INFRA-15971
The 5.0.0-alpha rc0 crushed this limit with a whopping 410MB
bin-tarball. INFRA temporarily increased this limit for me to commit the
RC to the staging area, but I've asked them to increase our limit to 500MB.
This is probably a good time for
i, Feb 2, 2018 at 10:58 AM, Josh Elser wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc0. This release
is only targeting Apache HBase 2.0 and is known to have lacking
functionality as compared to previous releases (e.g. transactional
tables,
Hive integrati
know what to test and not
test in the next RC.
[1] https://phoenix.apache.org/release_notes.html
On Mon, Feb 5, 2018 at 2:32 PM, Josh Elser wrote:
Just put up a patch to 4582.
Any other comments from folks before I re-roll?
On 2/5/18 3:35 PM, James Taylor wrote:
-1. Need to fix PHOENIX-4582
KEY ...)? Looks like point-in-time queries don't work correctly if your
table is taking writes (PHOENIX-4378).
One possible way to confirm any other missing feature would be to look at
newly ignored tests and any failing unit tests in 5.0.
On Mon, Feb 5, 2018 at 3:22 PM, Josh Elser wrote
rc0 fails. Will re-roll with the driver-version fix and others since.
On 2/2/18 10:58 AM, Josh Elser wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc0. This
release is only targeting Apache HBase 2.0 and is known to have lacking
functionality as compared to
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc1. Please
notice that there are known issues with this release which deserve the
"alpha" designation. These are staged on the website[1]. (Atomic upsert
does work on my local installation with trivial testing)
Over rc0
s/RC0/RC1/ below. I wasn't very diligent with my copy-paste-fix :)
The git-commit SHA1 is correct.
Please take a look if you can today!
On 2/9/18 10:34 AM, Josh Elser wrote:
Hello Everyone,
This is a call for a vote on Apache Phoenix 5.0.0-alpha rc1. Please
notice that there are
FYI, even though 72 hours has already elapsed, I plan to leave this open
until Wednesday under hopes that some other folks will take a look
before then (as a part of the work-week).
Thanks in advance!
On 2/12/18 10:34 AM, Josh Elser wrote:
s/RC0/RC1/ below. I wasn't very diligent wi
Hi Xu,
What version of Java and Maven are you using?
I wouldn't be super worried about the test failures -- it's likely just
an indication that the unit test is reliant on something in the local
environment which isn't there on your computer (e.g. a default
krb5.conf). Ideally, we can figure
This vote passes with 3 (binding) +1's and 1 non-binding +1
Will start promoting shortly.
Big thank you to those who voted.
On 2/12/18 10:34 AM, Josh Elser wrote:
s/RC0/RC1/ below. I wasn't very diligent with my copy-paste-fix :)
The git-commit SHA1 is correct.
Please take a look
The Apache Phoenix PMC is happy to announce the release of Phoenix
5.0.0-alpha for Apache Hadoop 3 and Apache HBase 2.0. The release is
available for download at here[1].
Apache Phoenix enables OLTP and operational analytics in Hadoop for low
latency applications by combining the power of stan
Hiya,
Thanks to everyone who helped get 5.0.0-alpha out the door. A few
book-keeping things:
* I've updated JIRA, nuking the 5.x and 5.0 fixVersions, renaming 5.0.0
to 5.0.0-alpha, and renaming 5.1.0 to 5.0.0. 5.0.0 is the fixVersion you
want.
* Announcement has been sent out and I think I'v
lease, I set the
fixVersion to 5.1.0 (anticipating that that'll be the next release
version). Should we use a different fixVersion that that for these "to be
release" fixes?
On Thu, Feb 15, 2018 at 12:04 PM, Josh Elser wrote:
Hiya,
Thanks to everyone who helped get 5.0.0-alpha
Hiya,
I wanted to share this little design doc with you about some feature
work we've been thinking about. The following is a Google doc in which
anyone should be allowed to comment. Feel free to comment there, or here
on the thread.
https://s.apache.org/phoenix-query-log
The high-level goa
ckward compatibility - any tests in place to validate that nothing
>> gets broken from release to release?
>>
>> Thanks,
>> James
>>
>> On Mon, Apr 10, 2017 at 8:08 AM, Dimitri wrote:
>>>
>>> Hi,
>>>
>>> DB API 2.0 and SQLAlchemy are
ure out some automation here to make that
happen. IIRC you have something already with Docker. I'm less worried
about this part :)
> Lukas
>
>
>
> On Thu, Mar 1, 2018 at 8:38 PM, Josh Elser wrote:
>>
>> Obviously, I'm in favor of this. Thanks for bringing it up ag
Any feedback from folks? Not sure if the silence should be interpreted
as ambivalence or plain old being busy :)
On Mon, Feb 26, 2018 at 4:57 PM, Josh Elser wrote:
> Hiya,
>
> I wanted to share this little design doc with you about some feature work
> we've been thinking about.
would be nice to have query logging out of the box! And if
the features are implemented like your proposal, we can replace an ugly
hacks with built-in feature from our cluster.
Thanks,
- Youngwoo
On Fri, Mar 2, 2018 at 10:05 AM, Josh Elser wrote:
Any feedback from folks? Not sure if the sile
is stored at this level? Then at DEBUG, then TRACE. Maybe
timestamp, SQL, and explain are at INFO. DEBUG adds bound parameters and
scan metrics. TRACE adds RPCs and timing, snapshot metadata.
Thanks,
Nick
On Mon, Feb 26, 2018 at 1:57 PM, Josh Elser wrote:
Hiya,
I wanted to share this little de
is async to the
flow of the query i.e. a query shouldn't incur the cost of the write
happening to the query log table
Doing 2) will help out with 1)
On Fri, Mar 2, 2018 at 2:28 PM, Josh Elser wrote:
Thanks Nick and Andrew! These are great points.
* A TTL out of the box is a must
+1
On 3/8/18 7:02 AM, Ankit Singhal wrote:
Lukas Lalinsky has graciously agreed to contribute his work on python
library for accessing Phoenix to Apache Phoenix project.
The details of the project can be viewed at:-
http://python-phoenixdb.readthedocs.io/en/latest/
Code of the project:-
ht
Hi Mark,
As you may or may not have seen[1][2], the Apache Phoenix community has
been trying to adopt the Python PhoenixDB project. Upon inspect the
history of the repository, I noticed that you have some non-trivial
contributions to the project.
As such, you likely have rights to claim copy
t need to file a CCLA. Let me
know what else I can help with.
Thanks,
Mark
On Thu, Mar 8, 2018 at 11:54 AM, Josh Elser <mailto:els...@apache.org>> wrote:
Hi Mark,
As you may or may not have seen[1][2], the Apache Phoenix community
has been trying to adopt the Python Phoen
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver to the Apache Phoenix Query Server called "Python
PhoenixDB".
http://incubator.apache.org/ip-clearance/phoenix-phoenixdb.html
This is subject to the 72-hr lazy consensus window (2018/03/18 1700GMT).
Please
is, I understand that Mark and Lukas are the two contributors with
non-trivial contributions.
Craig
Yup, Craig says it all. Does that help, John?
John
On Thu, Mar 15, 2018 at 1:10 PM Josh Elser wrote:
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver t
Gotcha. Thanks for taking a look, John! Much appreciated.
On 3/16/18 4:22 PM, John D. Ament wrote:
Yeah, its just a bit weird. The IP clearance mentions he's a copyright
holder, but the file headers don't mention that. Its fine either way.
On Fri, Mar 16, 2018 at 1:23 PM Josh El
Oops, will do. I thought that got auto-updated generated.
Thanks for the catch, Craig.
On 3/16/18 3:53 PM, Craig Russell wrote:
Hi Josh,
When you get a chance, please update the index page
http://incubator.apache.org/ip-clearance/
Thanks,
Craig
On Mar 15, 2018, at 10:10 AM, Josh Elser
This (lazy-consensus) VOTE passes with no objections.
On 3/15/18 1:10 PM, Josh Elser wrote:
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver to the Apache Phoenix Query Server called "Python
PhoenixDB".
http://incubator.apache.org/ip-clearan
Hi all,
I've published a new website for the upcoming event in June in
California at [1][2] for the HBase and Phoenix websites, respectively. 1
& 2 are identical.
I've not yet updated any links on either website to link to the new
page. I'd appreciate if folks can give their feedback on anyt
ged (smile)
Best Regards,
Yu
On 21 March 2018 at 10:51, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
identical.
I've not yet updated any links on eith
ls is
available *on on* EasyChair", the double "on" should be merged (smile)
Best Regards,
Yu
On 21 March 2018 at 10:51, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectiv
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
identical.
I've not yet updated any l
ng
8:30 AM - 5:00 PM
HBaseCon and PhoenixCon
12:00 PM – 7:00 PM
Registration
6:00 PM – 8:00 PM
Meetups
Is this intentional?
2018-03-21 14:59 GMT+08:00 Stack :
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in Cal
On 3/21/18 12:44 PM, Stack wrote:
On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser wrote:
On 3/21/18 2:59 AM, Stack wrote:
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
Hi all,
I've published a new website for the upcoming event in June in California
at [1][2] for the HBas
.
2018-03-22 0:29 GMT+08:00 Josh Elser :
Hey Duo,
Thanks for digging into this. I am not surprised by it -- last I talked
to
the folks in charge of the website, they mentioned that they would
cross-advertise for us as well. Seems like their web-staff is a bit
faster
than I am though. I was
Thanks Josh for doing this.
Do they have to be conflated so? Each community is doing their own
conference. This page/announcement makes it look like they have been
squashed together.
Thanks,
S
You have any concrete suggestions I can change?
You have hbasecon+phoenixcon which to me reads as
1 - 100 of 1808 matches
Mail list logo
