Hi Faisal,
That's an interesting idea - thanks for filing a JIRA for it. This
isn't currently supported, nor would it be feasible with out existing
equi-hash join mechanism which relies on 1) one side of the join being
small enough to fit into memory, and 2) being able to do a map lookup
from one
-defined funtion without building
the phoenix jar?
Please do reply
Thanks
Ramya.S
From: James Taylor [mailto:jamestay...@apache.org]
Sent: Sat 5/31/2014 10:33 AM
To: u...@phoenix.incubator.apache.org
Subject: Re: Pattern Matching using Phoenix
Our
Phoenix doesn't currently support HBase 0.96, but only 0.98.1+.
Thanks,
James
On Wednesday, July 2, 2014, Jeffrey Zhong jzh...@hortonworks.com wrote:
Have you put phoenix-core-*.jar into your hbase region server master
classpath and restart your region server master?
-Jeffrey
On 7/2/14
Rajeshbabu has submitted a pull request for local indexes to go into
master. It'd be great if a few other folks good give it a look:
https://github.com/apache/phoenix/pull/1
@JeffreyZ? @Jesse?
Thanks,
James
Hi Anil,
Try using CAST to explicitly cast the result to an unsigned date, like
this: CAST(TO_DATE(someDate) AS UNSIGNED_DATE)
Thanks,
James
On Wed, Jul 9, 2014 at 8:38 PM, anil gupta anilgupt...@gmail.com wrote:
Hi All,
Phoenix has a DataType Unsigned_Date but now i am unable to use these
=TO_DATE('2012-12-23', '-MM-dd')
and id='1234' limit 50;
I tried this query and i didn't get correct results. I have data in the
table where dummy_date = 2012-12-23.
~Anil
On Wed, Jul 9, 2014 at 12:13 PM, James Taylor jamestay...@apache.org
javascript:;
wrote:
Not sure
, 2014 at 11:18 AM
Subject: Re: How can we add new keywords to Phoenix?
To: James Taylor jamestay...@apache.org
Dear James,
KEYWORD is some kind of properties for an attribute which we added in our
project.
Say for example i want to select the last approved value for a specific
attribute from
I have a fix for this attached here:
https://issues.apache.org/jira/browse/PHOENIX-1016
https://issues.apache.org/jira/browse/PHOENIX-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
On Wednesday, July 16, 2014, Jeffrey Zhong (JIRA) j...@apache.org wrote:
[
Hi Ahmed,
First, take at look at this FAQ if you haven't already seen it:
http://phoenix.apache.org/faq.html#How_I_map_Phoenix_table_to_an_existing_HBase_table
If you're mapping to an existing HBase table, then the serialization
that was done to create the existing data must match the
Good question, Gabriel. I believe that the deleted cells are cleaned
up after a second major compaction with the KEEP_DELETED_CELLS option
enabled. Lars H. implemented this option, so he can comment more, but
AFAIK he couldn't figure out how to get them to be collected on the
first major
Thanks for following up on this, Gabriel. I don't know what went
wrong, but you're right, we need to fix it. @Jesse - any ideas?
Thanks,
James
On Fri, Jul 25, 2014 at 6:02 AM, Gabriel Reid gabriel.r...@gmail.com wrote:
Hi guys,
There was a mail on the user list today (see archive at
Thanks. We just need to declare the PDataType.pad(Object,int) method as
PDataType.pad(Object, Integer). The method has never been called on non
fixed length types (where getMaxLength() returns null).
I can make the change.
On Tue, Jul 29, 2014 at 11:18 PM, Samarth Jain samarth.j...@gmail.com
Getting ready to roll the first RC tomorrow. Please let me know if you
have any outstanding fixes you'd like to get in.
Thanks,
James
Hi Daniel,
The intent is that the table's sequence number increases when a
structural changes is made to the table (including adding an index to
it). So in this case, here's what should happen, assuming the sequence
number of the tables starts at 1):
- add index I to T. The sequence number of T
-965 please? It is really
short and if it is ok, add this fix to 3.1 version?
Thanks,
Vaclav
On 08/13/2014 01:25 AM, James Taylor wrote:
Hi everyone,
This is a call for a vote on Apache Phoenix 3.1.0 RC1. This is the
next minor release of Phoenix compatible with the 0.94 branch of
Apache
On the first connection to the cluster when you've installed Phoenix
2.2.3 and were previously using Phoenix 2.2.2, Phoenix will upgrade
your Phoenix tables to use the new coprocessor names
(org.apache.phoenix.*) instead of the old coprocessor names
(com.salesforce.phoenix.*).
Thanks,
James
On
Hi Jody,
Thanks for reporting this. These are bugs, as the client should detect
and retry automatically in these cases when necessary. What version of
Phoenix are you using? Would you mind giving it a shot in 3.1/4.1.
We'll have an RC out on Monday at the latest.
Thanks,
James
On Fri, Aug 15,
Source of site is in svn: https://svn.apache.org/repos/asf/phoenix
Most pages are generated at build time from markdown. The Team page is
at ./site/source/src/site/markdown/team.md. So just edit the markdown
and run ./build.sh to regenerate the html. Then check-in both the .md
file and the .html
IMHO, I don't think we have the bandwidth to maintain any more
branches. I'm also not sure this fits the criteria for a lazy
consensus vote.
The original intent of the 4.0 branch was meant to host all 4.x
releases. In general releases are compatible in the following manner:
- a minor release must
wrote:
+1. 4.0 named as 4.x or 4, 3.0 named as 3.x or 3
On Thu, Aug 21, 2014 at 10:48 AM, Andrew Purtell apurt...@apache.org
wrote:
On Thu, Aug 21, 2014 at 10:34 AM, James Taylor jamestay...@apache.org
wrote:
The original intent of the 4.0 branch was meant to host all 4.x
releases
+1
On Thu, Aug 21, 2014 at 11:13 AM, Jesse Yates jesse.k.ya...@gmail.com wrote:
+1
---
Jesse Yates
@jesse_yates
jyates.github.com
On Thu, Aug 21, 2014 at 11:11 AM, Andrew Purtell apurt...@apache.org
wrote:
I propose the following actions be taken after the next release
Hi everyone,
This is a call for a vote on Apache Phoenix 3.1.0 RC2. This is the
next minor release of Phoenix compatible with the 0.94 branch of
Apache HBase and will be our first release as a top level project. The
release includes both a source-only release and a convenience binary
release.
The
Hi everyone,
This is a call for a vote on Apache Phoenix 4.1.0 RC0. This is the
next minor release of Phoenix compatible with the 0.98 branch of
Apache HBase and will be our second release as a top level project. The
release includes both a source-only release and a convenience binary
release.
In
release.
//mujtaba
On Thu, Aug 21, 2014 at 4:14 PM, James Taylor jamestay...@apache.org
javascript:;
wrote:
Hi everyone,
This is a call for a vote on Apache Phoenix 4.1.0 RC0. This is the
next minor release of Phoenix compatible with the 0.98 branch of
Apache HBase
created... it doesn't seem to be explicity specified in
phoenix-assembly or top-level phoenix pom (but I'm probably just blind).
---
Jesse Yates
@jesse_yates
jyates.github.com
On Fri, Aug 22, 2014 at 1:57 PM, James Taylor jamestay...@apache.org
wrote:
We build separate
AM, James Taylor wrote:
Vote will be open for at least 72 hours. Please vote:
[X] +1 approve
Steven.
jar.
Thanks,
-Jeffrey
On 8/23/14, 4:54 PM, James Taylor jamestay...@apache.org wrote:
Thanks, Jeffrey. Did you do any testing against HDP 2.1? So the
phoenix-4.1.0-server*.jar are out of date? Or we include jars that
aren't necessary? Would you mind filing a JIRA?
James
On Sat, Aug 23
Hi everyone,
This is a call for a vote on Apache Phoenix 3.1.0 RC3. This is the
next minor release of Phoenix compatible with the 0.94 branch of
Apache HBase and will be our first release as a top level project. The
release includes both a source-only release and a convenience binary
release.
The
Hi everyone,
This is a call for a vote on Apache Phoenix 4.1.0 RC1. This is the
next minor release of Phoenix compatible with the 0.98 branch of
Apache HBase and will be our second release as a top level project.
The release includes both a source-only release and a convenience
binary release.
+1
On Thu, Aug 28, 2014 at 10:09 AM, Mujtaba Chohan mujt...@apache.org wrote:
+1.
1. Verified deployment on cluster.
2. Verified performance is on par with last release.
//mujtaba
On Thu, Aug 28, 2014 at 4:46 AM, Steven Noels stev...@satisa.be wrote:
Vote will be open for at least 72
+1
On Thu, Aug 28, 2014 at 12:59 PM, Eli Levine elilev...@gmail.com wrote:
+1 from me. Ran this through an internal Salesforce integration test suite
and things look good.
On Thu, Aug 28, 2014 at 10:08 AM, Mujtaba Chohan mujt...@apache.org wrote:
+1.
1. Verified deployment on cluster.
Hello,
This issue was fixed with PHOENIX-1188 which is in our 3.1/4.1
release. Would you mind trying on the newly released version?
There's a configuration parameter, phoenix.query.scanResultChunkSize,
that controls after how many rows chunking starts. The default value
is 2999, so if the total
Hello everyone,
On behalf of the Apache Phoenix team, I'm pleased to announce the
immediate availability of our 3.1 and 4.1 releases:
http://phoenix.apache.org/download.html
These include many bug fixes along with support for nested/derived
tables, tracing, and local indexing. For details of the
On behalf of the Apache Phoenix PMC, I'm pleased to announce that
Rajeshbabu Chintaguntla has been added as a committer to the Apache
Phoenix project. He's responsible for adding local indexing[1] to our
recent 4.1 release, a complementary secondary index strategy to global
indexing for
+1. Anyone have any connections that'll help us get added?
James
On Mon, Sep 1, 2014 at 10:24 PM, anil gupta anilgupt...@gmail.com wrote:
Hi All,
For years, I have been using this nice user friendly search-hadoop.com
website to search for mail threads related to Hadoop projects.
It would be
On behalf of the Apache Phoenix PMC, I'm pleased to announce that Ravi
Magham has been added as a committer to the Apache Phoenix project.
He's been the force behind much of our integration with other Apache
projects such as the Pig Loader [1], our Flume plugin [2], and the
work-in-progress Sqoop
, Sep 1, 2014 at 10:35 PM, James Taylor jamestay...@apache.org wrote:
+1. Anyone have any connections that'll help us get added?
James
On Mon, Sep 1, 2014 at 10:24 PM, anil gupta anilgupt...@gmail.com wrote:
Hi All,
For years, I have been using this nice user friendly search-hadoop.com
website
Good news on this - they're going to add Apache Phoenix.
Thanks,
James
On Monday, September 1, 2014, James Taylor jamestay...@apache.org wrote:
Looks like there's a form you can fill in to request Phoenix be added
- you need to fill it in under Other here:
https://docs.google.com
Hi Jaywong,
Rather than disable the underlying HBase table through a non Phoenix
API, I'd recommend using the DROP INDEX command if you no longer want
the index: http://phoenix.apache.org/language/index.html#drop_index
In general, it's not a good idea to bypass the Phoenix API as that'll
cause
That's a typo - the max precision is 38. Would you mind filing a JIRA so we
don't forget to update it?
Thanks,
James
On Monday, September 15, 2014, Chagarlamudi, Prasanth
prasanth.chagarlam...@epsilon.com wrote:
Good afternoon,
Is the max precision of DECIMAL data type 18 or is it a typo?
I
Take a look at my blog on how SequenceIQ setup a Docker for
Phoenix+HBase to make it super easy to get started:
https://blogs.apache.org/phoenix/entry/getting_started_with_phoenix_just
Thanks,
James
We've already got a lot of great fixes, perf improvements, and feature
enhancements in the 3.0/4.0 branch. I'd like to propose that we cut an
RC for 3.2/4.2 at the end of week.
Thoughts?
Thanks,
James
Hello,
We've been planning on dropping hadoop1 support for our 4.x releases
for a while now and it looks like it'll happen in 4.2. It'd be nice if
we could do the same for our 3.x releases, as the more similar the two
branches are, the less time it takes to keep them in sync.
Is anyone out there
Please make sure you get anything checked in you need before then.
Thanks,
James
Is https://issues.apache.org/jira/browse/PHOENIX-1233 a showstopper
and should we fix it for our 3.2/4.2 release?
Thanks,
James
Hi everyone,
This is a call for a vote on Apache Phoenix 3.2.0 RC0. This is the
next minor release of Phoenix compatible with the 0.94 branch of
Apache HBase. The release includes both a source-only release and a
convenience binary release.
In addition to 50+ bug fixes, the following new features
Hi everyone,
This is a call for a vote on Apache Phoenix 4.2.0 RC0. This is the
next minor release of Phoenix compatible with the 0.98 branch of
Apache HBase with feature parity against the upcoming Phoenix 3.2
release. The release includes both a source-only release and a
convenience binary
rat
* Verified contents of source distribution vs tag in git
* Successfully ran full integration test suite
I noticed the same references to the incubator as in the 3.2 RC, but
again no reason to sink the release.
- Gabriel
On Wed, Oct 22, 2014 at 6:21 PM, James Taylor jamestay
(may include phoenix-1381 phoenix-1379 as well)
in 4.2.1.
Thanks,
-Jeffrey
On 10/26/14, 12:23 AM, James Taylor jamestay...@apache.org
javascript:; wrote:
Jeffrey,
Do you suggest we roll a new RC with your patch and fixes for (1) (2)?
Thanks,
James
On Sat, Oct 25, 2014 at 9:55 PM
We're rolling a new RC now with fixes for the issues found.
Thanks,
James
On Sun, Oct 26, 2014 at 9:49 AM, James Taylor jamestay...@apache.org wrote:
Let's cut a new RC on Monday.
Thanks,
James
On Sunday, October 26, 2014, Jeffrey Zhong jzh...@hortonworks.com wrote:
I think it’s better
MESSAGE-
Hash: SHA1
+1
Vaclav;
On 10/22/2014 06:14 PM, James Taylor wrote:
Hi everyone, This is a call for a vote on Apache Phoenix 3.2.0 RC0.
This is the next minor release of Phoenix compatible with the 0.94
branch of Apache HBase. The release includes both a source-only
release
Hi everyone,
This is a call for a vote on Apache Phoenix 3.2.0 RC1. This is the
next minor release of Phoenix compatible with the 0.94 branch of
Apache HBase with feature parity against the upcoming Phoenix 4.2.0
release. The release includes both a source-only release and a
convenience binary
Hi everyone,
This is a call for a vote on Apache Phoenix 4.2.0 RC1. This is the
next minor release of Phoenix compatible with the 0.98 branch of
Apache HBase with feature parity against the upcoming Phoenix 3.2.0
release. The release includes both a source-only release and a
convenience binary
Hi Mike,
Yes, the bit configuration is different in Phoenix to ensure that the
sort order of the binary representation matches the natural sort order
of the data. This improves Phoenix performance by allowing many more
query optimizations than would otherwise be possible.
You can convert
:
+1 to release
* Verified signatures and checksums
* Ran rat
* Verified contents of source distribution vs tag in git
* Successfully ran full integration test suite
On Wed, Oct 29, 2014 at 12:49 AM, James Taylor jamestay...@apache.org
javascript:; wrote:
Hi everyone,
This is a call
+1
Eat, lived, breathed Phoenix for the past two months. :-)
On Fri, Oct 31, 2014 at 11:34 AM, lars hofhansl la...@apache.org wrote:
+1
Build from source against 0.98 built from source.Inserted 2^24 rows.
Performed various queries. All good.
-- Lars
From: James Taylor jamestay
The vote for the release of Apache Phoenix 3.2.0 RC1 is now closed and
has passed with 4 binding +1s and no 0 or -1s:
Ted Yu
Ramkrishna S. Vasudevan*
Gabriel Reid*
Mujtaba Chohan*
James Taylor*
*=binding
We'll push out the new release to maven on Monday. Thanks to those who voted.
James
The vote for the release of Apache Phoenix 4.2.0 RC1 is now closed and
has passed with 8 binding +1s and no 0 or -1s:
Eli Levine*
Ted Yu
Ramkrishna S. Vasudevan*
Jeffrey Zhong*
Gabriel Reid*
Mujtaba Chohan*
Rajeshbabu Chintaguntla
Lars Hofhansl*
James Taylor*
*=binding
We'll push out the new
Hi JM,
The phoenix.query.threadPoolSize corresponds to the client-side
ThreadPoolExecutor size. All threads on the client-side come out of
this pool. As new threads are spawned, they get new names using an
AtomicLong that is incremented each time - see
org.apache.phoenix.job.JobManager.
Are you
We've found a number of issues in 4.2.0 that we have fixes for
already. I'd like to check in a fix for PHOENIX-1402 (Don't
recalculate stats on split) and then cut an RC tomorrow AM.
Any other issues folks would like to see in the patch?
Thanks,
James
Hello everyone,
This is a call for a vote on Apache Phoenix 4.2.1 RC0. This is a bug
fix/patch release of Phoenix 4.2, compatible with the 0.98 branch of
Apache HBase with feature parity against the Phoenix 3.2 release. The
release includes both a source-only release and a convenience binary
Hi everyone,
This is a call for a vote on Apache Phoenix 3.2.1 RC0. This is a bug
fix/patch release of Phoenix 3.2, compatible with the 0.94 branch of
Apache HBase with feature parity against the Phoenix 4.2 release. The
release includes both a source-only release and a convenience binary
release.
Thanks for the patch, Radu. It looks good to me. How about filing a
JIRA and attaching the patch? It'd be good if Gabriel gave it a look
too.
James
On Fri, Nov 7, 2014 at 2:51 PM, Radu Marias radumar...@gmail.com wrote:
I will
On Nov 8, 2014 12:47 AM, Ted Yu yuzhih...@gmail.com wrote:
, 2014 at 8:54 PM, James Taylor jamestay...@apache.org
wrote:
Hello everyone,
This is a call for a vote on Apache Phoenix 4.2.1 RC0. This is a
bug
fix/patch release of Phoenix 4.2, compatible with the 0.98 branch
of
Apache HBase with feature parity against the Phoenix
gabriel.r...@gmail.com wrote:
+1 to release
* Verified signatures and checksums
* Ran rat
* Verified contents of source distribution vs tag in git
* Successfully ran full integration test suite
On Fri, Nov 7, 2014 at 9:42 PM, James Taylor jamestay...@apache.org wrote:
Hi everyone,
This is a call
Please let me know if you'd like something in there that's not already planned.
Thanks,
James
Hello everyone,
This is a call for a vote on Apache Phoenix 4.2.1 RC1. This is a bug
fix/patch release of Phoenix 4.2, compatible with the 0.98 branch of
Apache HBase with feature parity against the Phoenix 3.2 release. The
release includes both a source-only release and a convenience binary
propose we sink the RC, remove the upgrade code from 4.2, and push it to
4.3. That means the sequence table will not be pre-split in 4.2.
Let's discuss, I won't -1 the RC until we do.
Thanks.
-- Lars
From: James Taylor jamestay...@apache.org
To: dev@phoenix.apache.org dev
, we can call it a new requirement, and still do that in
4.2. The release is not out, so we can fix it now.
This does break things, as we've seen. I would like to discuss it here.
Since we did not finish voting - if we wanted to change this, now is the
time.
-- Lars
From: James Taylor
it or leave it. :)
Thanks.
-- Lars
From: James Taylor jamestay...@apache.org
To: lars hofhansl la...@apache.org
Cc: dev@phoenix.apache.org dev@phoenix.apache.org; Andrew Purtell
andrew.purt...@gmail.com; James Taylor jamestay...@apache.org
Sent: Sunday, November
I don't see that. I guess it was in another
response. So can we set phoenix.sequence.saltBuckets to 0 by default then in
this release?
On Nov 16, 2014, at 2:02 PM, James Taylor jamestay...@apache.org wrote:
As Jeffrey pointed out, there's already a way to turn off the upgrade
- just set
+1
On Sat, Nov 15, 2014 at 8:54 AM, Steven Noels stev...@apache.org wrote:
On Thu, Nov 13, 2014, at 08:35 PM, James Taylor wrote:
Vote will be open for at least 72 hours. Please vote:
[X] +1 approve
Steven.
The vote for the release of Apache Phoenix 3.2.1 RC1 is now closed and
has passed with 3 binding +1s and no 0 or -1s:
Gabriel Reid*
Steven Noels*
James Taylor*
*=binding
We'll push out the new release to maven. Thanks to those who voted.
James
On Mon, Nov 17, 2014 at 9:34 PM, James Taylor
On Mon, Nov 17, 2014 at 9:35 PM, James Taylor jamestay...@apache.org wrote:
The vote for the release of Apache Phoenix 3.2.1 RC1 is now closed and
has passed with 3 binding +1s and no 0 or -1s:
Gabriel Reid*
Steven Noels*
James Taylor*
*=binding
We'll push out the new release to maven
We've always asked in the past that you upgrade separately from one
minor release to the next (i.e. from 4.0.0 to 4.1.0 and then to
4.2.1), but I like Jeffrey's idea to improve this.
Thanks,
James
On Fri, Nov 21, 2014 at 5:37 PM, Jeffrey Zhong jzh...@hortonworks.com wrote:
Actually this is a
To add to what Samarth said, please take a look also at the unit tests
in QueryMoreIT as they give you a pretty good idea on how to implement
paged queries in a scalable manner over big data.
Thanks,
James
On Sun, Nov 23, 2014 at 7:33 PM, Samarth Jain samarth.j...@gmail.com wrote:
Supporting
I'd like to propose that we start the vote for a 3.2.2 and 4.2.2 patch
release as we have some important fixes committed already. I was
thinking we could start the vote this Wednesday. Please let me know if
there's any pending work you'd like to get in before then.
Thanks,
James
with a release, etc, but I was
thinking it would be good to be able to pull this directly from Jira
(some other projects have a release note field), and I was wondering
if anyone had any suggestions on this.
- Gabriel
On Mon, Dec 1, 2014 at 7:29 PM, James Taylor jamestay...@apache.org wrote
Hello everyone,
This is a call for a vote on Apache Phoenix 4.2.2 RC0. This is a bug
fix/patch release of Phoenix 4.2, compatible with the 0.98 branch of
Apache HBase with feature parity against the Phoenix 3.2 release. The
release includes both a source-only release and a convenience binary
Hello everyone,
This is a call for a vote on Apache Phoenix 3.2.2 RC0. This is a bug
fix/patch release of Phoenix 3.2, compatible with the 0.94 branch of
Apache HBase with feature parity against the Phoenix 4.2 release. The
release includes both a source-only release and a convenience binary
On behalf of the Apache Phoenix PMC, I'm pleased to announce that
Samarth Jain has accepted our invitation to become a committer on the
Apache Phoenix project. He's been a steady contributor over the past
year and we're looking forward to many more future contributions.
Great job, Samarth!
Dimiduk ndimi...@gmail.com wrote:
On Thu, Dec 4, 2014 at 11:11 AM, James Taylor jamestay...@apache.org
wrote:
Wow, this is fantastic, Nick. Big +1.
Thanks for the enthusiasm James :)
You're welcome to coopt and use the type-system branch in the Apache
Phoenix git repo if that's helpful
The vote for the release of Apache Phoenix 4.2.2 RC0 is now closed and
has passed with 6 binding +1s and no 0 or -1s:
Eli Levine*
Ted Yu
Gabriel Reid*
Mujtaba Chohan*
James Taylor*
Lars Hofhansl*
Ramkrishna S. Vasudevan*
*=binding
We'll push out the new release to maven shortly. Thanks to those
The vote for the release of Apache Phoenix 3.2.2 RC0 is now closed and
has passed with 3 binding +1s and no 0 or -1s:
Gabriel Reid*
Mujtaba Chohan*
James Taylor*
*=binding
We'll push out the new release to maven shortly. Thanks to those who voted.
On Mon, Dec 8, 2014 at 12:33 PM, James Taylor
, James Taylor jamestay...@apache.org
wrote:
+1 on using PInteger, PLong, etc. to disambiguate.
+1 on limiting to purely structural changes initially.
If it can be b/w compatible (with all tests passing), I'd vote to put
it in 4.x and master. The longer we can keep 4.1 and master
Hello Phoenix users,
We'd like to get an idea of how many users are still relying on the
Phoenix 3.x releases that work with HBase 0.94. We've been diligently
maintaining feature parity (as much as possible) between the 3.x
releases and 4.x releases, but the cost of continuing to do so is
becoming
The Apache Phoenix team is pleased to announce the immediate
availability of the 4.2.2/3.2.2 release. For details of the release,
see our release announcement[1].
The Apache Phoenix team
[1] https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_2_2
HBase 0.96 is not supported by Phoenix - only HBase 0.98.1 and above.
The CDH 5.1 releases package HBase 0.98, so these are ok.
On Mon, Dec 15, 2014 at 10:31 PM, su...@certusnet.com.cn
su...@certusnet.com.cn wrote:
Hi,all
Just want to confirm the appropriate versions of phoenix for
We've got a lot of great stuff in 4.3 already:
- 60 bug fixes (which includes fixes from 4.2.1 and 4.2.2)
- many-to-many join support
- map-reduce integration
- improvements to date/time column handling for CSV loading
- groundwork for future type system improvements
- local index perf fix
A
Would our 4.2.2 binaries continue to work with releases of HBase
containing this change?
On Tue, Dec 30, 2014 at 3:14 PM, Enis Söztutar enis@gmail.com wrote:
Thanks Andrew,
Once HBASE-12028 is committed it should be easy enough to make the changes
in Phoenix to be able to compile with
that.
How many versions of HBase = 0.98.10 do you think would need to be binary
compatible with 4.2.2?
On Dec 30, 2014, at 3:23 PM, James Taylor jamestay...@apache.org wrote:
Would our 4.2.2 binaries continue to work with releases of HBase
containing this change?
On Tue, Dec 30, 2014 at 3:14 PM
Thanks, Andrew. I filed PHOENIX-1569 as well.
On Tue, Dec 30, 2014 at 4:34 PM, Andrew Purtell apurt...@apache.org wrote:
Thanks for the feedback James. I filed HBASE-12787 in response.
On Tue, Dec 30, 2014 at 3:49 PM, James Taylor jamestay...@apache.org
wrote:
bq. How many versions of HBase
I'd like to propose we can a 3.3/4.3 RCs on Tuesday. Will that give
folks enough time to complete any outstanding work?
Thanks,
James
Gabriel,
I agree. The way you've outlined it is more correct. I suspect ALTER
TABLE DROP COLUMN may suffer from a similar issue. Please file a JIRA
when you have a chance.
Thanks,
James
On Tue, Jan 13, 2015 at 12:14 PM, Gabriel Reid gabriel.r...@gmail.com wrote:
I've encountered what appears (to
Hello community,
Our new Who is Using Apache Phoenix page is live [1]. Thank you very
much for all your excellent use case descriptions and quotes. Please
let me know if I've missed your company and you'd like to be added.
Thanks,
James (on behalf of The Apache Phoenix team)
[1]
I'm excited to announce the first ever Apache Phoenix meetup, hosted
by salesforce.com in San Francisco on Tuesday, February 24th @ 6pm.
More details here:
http://www.meetup.com/San-Francisco-Apache-Phoenix-Meetup/events/220009583/
Please ping me if you're interested in presenting your companies
Hello everyone,
This is a call for a vote on Apache Phoenix 4.3.0 RC0. This is the
next minor release of Phoenix 4, compatible with the 0.98 branch of
Apache HBase. The release includes both a source-only release and a
convenience binary release.
Highlights of the release include:
- functional
Please let me know if there is any outstanding work that needs to be
in 4.3, as I'd like to cut our first RC today.
Thanks,
James
Hello everyone,
This is a call for a vote on Apache Phoenix 3.3.0 RC2. This is the
next minor release of the Phoenix 3.x code line, compatible with the
0.94 branch of Apache HBase. The previous RC was sunk due to
PHOENIX-1669, PHOENIX-1588, and PHOENIX-1654 which are now fixed. The
release
New RC coming shortly.
On Thu, Feb 12, 2015 at 4:59 PM, Sergey Belousov
sergey.belou...@gmail.com wrote:
+1
we are running on snapshot build #578 now due to some critical for us fixes
so it long awaited release.
On Tue, Feb 10, 2015 at 10:25 PM, James Taylor jamestay...@apache.org
wrote
1 - 100 of 10887 matches
Mail list logo
