Re: Phoenix and Cloudera

Completely concur with this, demand Phoenix packaging and support from your vendor of choice! (smile) On Fri, Jul 18, 2014 at 9:30 AM, James Taylor wrote: > Thanks for the positive feedback, Mike. I wouldn't counter this > argument, I'd agree with it. The more Cloudera customers that ask for >

Re: Error when using Pig Storage: Found interface org.apache.hadoop.mapreduce.TaskAttemptContext, but class was expected

I don't think an Apache project should spend precious bandwidth tracking the various and sundry redistributors of Apache ecosystem projects. This is putting the cart before the horse. The horse is the Apache upstream projects. The cart is the commercial distributions leveraging the Apache ecosystem

Re: Error when using Pig Storage: Found interface org.apache.hadoop.mapreduce.TaskAttemptContext, but class was expected

of them will add spark-like support for >>> CDH and HDP to advance the project. >>> >>> And I don't mention the POM thing to pick on someone. The majority of >>> HBase users are not going to be able to use Phoenix because they run a >>> commercial d

Re: First steps: Could not find or load main class sqlline.SqlLine

On Tue, Aug 26, 2014 at 9:40 AM, Jean-Marc Spaggiari < jean-m...@spaggiari.org> wrote: > Ok. Looked into sqlline.py code, exported PHOENIX_LIB_DIR to the right > directory, and it now works... > ​You were using the Bigtop package? Please consider filing a Bigtop JIRA.​ -- Best regards, -

Re: Connecting Hbase to Elasticsearch with Phoenix

Thanks for writing in with this pointer Alex! On Wed, Sep 10, 2014 at 11:11 AM, Alex Kamil wrote: > I posted step-by-step instructions here on using Apache Hbase/Phoenix with > Elasticsearch JDBC River. > > This might be useful to Elasticsearch users who want to use Hbase as a > primary data stor

Re: Phoenix response time

Certainly the EMR support makes it easy to deploy a test cluster to kick around the tires. On Sat, Sep 6, 2014 at 10:03 AM, James Taylor wrote: > I don't have experience running Phoenix in AWS. Andrew Purtell is a > good person to ask. I'm curious if our support under their EM

Re: Phoenix client maven dependencies

On Thu, Sep 18, 2014 at 3:01 PM, James Taylor wrote: > I see. That makes sense, but it's more of an HBase request than a > Phoenix request. If HBase had a "client-only" pom, then Phoenix could > have a "client-only" pom as well. > > Thanks, > James If you specify only the 'hbase-client' Maven mod

Re: Phoenix client maven dependencies

See PHOENIX-1272 On Mon, Sep 22, 2014 at 9:31 AM, James Taylor wrote: > +1 to doing the same for hbase-testing-util. Thanks for the analysis, Andrew! > > James > > On Mon, Sep 22, 2014 at 9:18 AM, Andrew Purtell wrote: >> On Thu, Sep 18, 2014 at 3:01 PM, James Taylor w

Re: Phoenix client maven dependencies

uld, though we could continue it in the 4.X line for > compatibility's sake. > > --- > Jesse Yates > @jesse_yates > jyates.github.com > > On Mon, Sep 22, 2014 at 9:31 AM, James Taylor > wrote: >> >> +1 to doing the same for hbase-testing-util. Thanks for the analysis

Re: anyone relying on hadoop1 still?

Hoya isn't HBase or Phoenix. It's a separate project, now named Slider, now in incubation at Apache, see http://incubator.apache.org/projects/slider.html On Thu, Sep 25, 2014 at 10:58 PM, Flavio Pompermaier wrote: > So Hoya is a different thing from Hbase on hadoop 2? > > On Sep 25, 2014 11:23 PM

Re: use phoenix table as a message queue

On Mon, Oct 27, 2014 at 9:42 PM, Li Li wrote: > I want to use a phoenix as a message queue. ​In general it's not advisable to use a database as a message queue. Use one of the purpose built systems for message queuing, there are many alternatives. ​ -- Best regards, - Andy Problems wort

Re: Replication?

You also need to replicate the Phoenix system tables. It's still necessary to run DDL operations on both clusters to keep Phoenix schema and HBase tables in sync. Use IF EXISTS or IF NOT EXISTS to avoid DDL statement failures. Phoenix should do the right thing. If not, it's a bug. The sequence tab

Re: Problems building Phoenix 4.2.2 with BigTop

I think I know what is going on. The Phoenix POM defines the property "snappy.version", and sets it to "0.3", this is the version of org.iq80.snappy we want. However, I bet the Bigtop build scaffold launches the Phoenix build with "snappy.version" set to "1.0.4.1". We should probably fix that with

Re: Phoenix 4.2.2 install against CDH 5.3

You are using a Java 6 based runtime but Java 7 is required (51.0 is the class file version for Java 7.) Your options are: 1. Install and use a Java 7 runtime. 2. Patch the Phoenix POM to specify a target compilation version of 1.6 and build Phoenix from source. This may not work if any 7ish l

Re: Phoenix 4.2.2 install against CDH 5.3

That's great! Thanks for letting us know. On Mon, Jan 5, 2015 at 11:56 AM, Abraham Tom wrote: > upgrading my java worked > > On Sat, Jan 3, 2015 at 10:16 AM, Andrew Purtell > wrote: > >> You are using a Java 6 based runtime but Java 7 is required (51.0 is the >&g

[ANNOUNCE] HBase 0.98.10.1 is now available for download

Apache HBase 0.98.10.1 is now available for download. Get it from an Apache mirror [1] or Maven repository. The list of changes in this release can be found in the release notes [2][3] or following this announcement. Thanks to all who contributed to this release. Best, The HBase Dev Team 1. htt

Re: Phoenix with Hbase Transparent Encryption of Data At Rest

Thanks for reporting this issue! At first glance it looks like an HBase bug, please see https://issues.apache.org/jira/browse/HBASE-13096 for further investigation. On Tue, Feb 24, 2015 at 9:52 AM, Dhaval Rami wrote: > An FYI, > > I tried using phoenix in hBase with Transparent Encryption of Dat

Re: Fwd: java.lang.IllegalAccessError: com/google/protobuf/HBaseZeroCopyByteString

This is HBASE-8 (https://issues.apache.org/jira/browse/HBASE-8). Looks like someone else wrote in that Oozie wasn't working for them. You should follow up on the HBase issue tracker, although no promises, it may be an Oozie problem, but this is not a Phoenix issue. On Mon, Mar 16, 2015 at

[ANNOUNCE] HBase 0.98.12.1 is now available for download

Apache HBase 0.98.12.1 is now available for download. Get it from an Apache mirror [1] or Maven repository. This is a patch release containing an important security fix for CVE-2015-1836 (Apache HBase remote denial of service, information integrity, and information disclosure vulnerability). All d

[ANNOUNCE] HBase 1.0.1.1 is now available for download

Apache HBase 1.0.1.1 is now available for download. Get it from an Apache mirror [1] or Maven repository. This is a patch release containing an important security fix for CVE-2015-1836 (Apache HBase remote denial of service, information integrity, and information disclosure vulnerability). All dep

CVE-2015-1836: Apache HBase remote denial of service, information integrity, and information disclosure vulnerability

CVE-2015-1836: Apache HBase remote denial of service, information integrity, and information disclosure vulnerability. Severity: Important Vendor: The Apache Software Foundation Versions Affected: HBase 0.98.0 - 0.98.12 HBase 1.0.0 - 1.0.1 HBase 1.1.0 The unsupported HBase 0.96 versions are al

[ANNOUNCE] HBase 1.1.0.1 is now available for download

Apache HBase 1.1.0.1 is now available for download. Get it from an Apache mirror [1] or Maven repository. This is a patch release containing an important security fix for CVE-2015-1836 (Apache HBase remote denial of service, information integrity, and information disclosure vulnerability). All dep

Re: HBase's checkAndPut, Timestamp in Phoenix-Spark API

Hi, Over on HBase we are working on direct integration with spark. That may (or may not) be a better option when you already have code using the HBase API directly. Please see https://issues.apache.org/jira/browse/HBASE-13992 On Saturday, July 18, 2015, Josh Mahonin wrote: > Hi, > > The phoeni

Re: setting up community repo of Phoenix for CDH5?

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 offi

Re: Phoenix query server user authentication?

I think instead of the change as proposed it would be cleaner and more flexible to introduce a plug point in the query server for authentication. Then there could be reusable plugins for extracting the common SSO tokens (like JWT or SAML) and validating them against the common identity providers

Re: setting up community repo of Phoenix for CDH5?

t 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 wrote: >> Yes I am interested. Assum

Re: setting up community repo of Phoenix for CDH5?

eeding 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

Re: setting up community repo of Phoenix for CDH5?

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 wrote: > > The group IDs and versions can be parameterized in the POM so

Re: setting up community repo of Phoenix for CDH5?

>> Let us know when the repo is available so we can help... >> >> Thanks, >> >> JM >> >> 2015-09-12 18:38 GMT-04:00 Krishna : >>> As explained here, there are some code changes too in addition to pom >>> related changes. >>> >>&

Re: setting up community repo of Phoenix for CDH5?

y 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 w

Re: setting up community repo of Phoenix for CDH5?

re 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 4.5-HBase-1.0-cdh5 and the tag

Re: setting up community repo of Phoenix for CDH5?

-- > [INFO] Total time: 2 minutes 17 seconds > [INFO] Finished at: Tue Sep 15 19:55:03 EDT 2015 > [INFO] Final Memory: 134M/1648M > [INFO] > > &

Re: setting up community repo of Phoenix for CDH5?

el 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

Re: [ANNOUNCE] Welcome our newest Committer Dumindu Buddhika

Congratulations and welcome! On Thu, Sep 17, 2015 at 9:18 PM, Vasudevan, Ramkrishna S < ramkrishna.s.vasude...@intel.com> wrote: > Hi All > > > > Please welcome our newest committer Dumindu Buddhika to the Apache Phoenix > team. Dumindu, a student and an intern in the GSoC program, has > cont

Re: [ANNOUNCE] New Apache Phoenix committer - Jan Fernando

Congratulations Jan, and welcome! On Tue, Sep 29, 2015 at 11:23 AM, Eli Levine wrote: > On behalf of the Apache Phoenix project I am happy to welcome Jan Fernando > as a committer. Jan has been an active user and contributor to Phoenix in > the last couple of years. Some of his major contributi

Re: Column level security in phoenix hbase

Depending on what you need this is something we've talked about implementing but haven't done so yet. The subject line of your mail says column level security but in the body of your mail you mention cell level security instead. Which do you mean? Or both? They are distinct mechanisms. It woul

Re: Error installing Phoenix

Try building Phoenix from https://github.com/chiastic-security/phoenix-for-cloudera and install the resulting server jar. CDH includes some local changes to HBase which cause binary compatibility issues. > On Nov 3, 2015, at 7:09 AM, Michael Mior wrote: > > I have a working HBase installati

Announcing phoenix-for-cloudera 4.6.0

Today I pushed a new branch '4.6-HBase-1.0-cdh5' and the tag 'v4.6.0-cdh5.4.5' (58fcfa6) to https://github.com/chiastic-security/phoenix-for-cloudera. This is the Phoenix 4.6.0 release, modified to build against CDH 5.4.5 and possibly (but not tested) subsequent CDH releases. If you want release t

Re: [DISCUSS] discontinue 4-x HBase 1.0 releases?

That's my understanding as well. On Tue, Nov 17, 2015 at 10:56 AM, Nick Dimiduk wrote: > FYI, HBase has recently decided to discontinue the 1.0.x line. I believe > the pending 1.0.3 release is expected to be the last. > > On Wed, Sep 30, 2015 at 10:36 AM, James Taylor > wrote: > >> Thanks for

Re: [DISCUSS] discontinue 4-x HBase 1.0 releases?

s Taylor wrote: > Until the CDH distro moves off of 1.0, we'll likely want to continue > releasing Phoenix on top of it (even if there are no further HBase 1.0 > releases). That's assuming our CDH Phoenix users want the new features and > bug fixes we're developing. > >

Re: Help tuning for bursts of high traffic?

Kumar - I believe you mentioned you are seeing this in a cluster of ~20 regionservers. Zack - Yours is smaller yet, at 9. These clusters are small enough to make getting stack dumps through the HBase debug servlet during periods of unusually slow response possible. Perhaps you can write a script

Re: Help tuning for bursts of high traffic?

xRuntime.getOverAllReadRequestMetrics(), and other methods with Metrics > in the name. > -I'll look into this > > 12) There's also tracing, which is end-to-end client/server, but it's in a > bit on the raw side still: > https://phoenix.apache.org/tracing.htmlhttps://phoeni

Re: Announcing phoenix-for-cloudera 4.6.0

extRaw(java.util.List,org.apache.hadoop.hbase.regionserver.ScannerContext) > in org.apache.hadoop.hbase.regionserver.RegionScanner > > >> On Fri, Jan 15, 2016 at 6:20 PM, Krishna wrote: >> >> Thanks Andrew. Are binaries available for CDH5.5.x? >> >> On Tue, Nov 3

Re: Announcing phoenix-for-cloudera 4.6.0

Looking today On Tue, Jan 26, 2016 at 11:00 PM, Kumar Palaniappan < kpalaniap...@marinsoftware.com> wrote: > Andrew, any updates? Seem HBase-11544 impacted the Phoenix and CDH 5.5.1 > isnt working. > > On Sun, Jan 17, 2016 at 11:25 AM, Andrew Purtell > wrote: > >

Re: Announcing phoenix-for-cloudera 4.6.0

and integration tests for me (except a silly date test that hardcodes the expected year to 2015). On Thu, Jan 28, 2016 at 11:23 AM, Andrew Purtell wrote: > Looking today > > > On Tue, Jan 26, 2016 at 11:00 PM, Kumar Palaniappan < > kpalaniap...@marinsoftware.com> wrote: >

Re: Announcing phoenix-for-cloudera 4.6.0

oudera/tree/4.6-HBase-1.0-cdh5.5 > >> On Thu, Jan 28, 2016 at 6:51 PM, Andrew Purtell wrote: >> I pushed a new branch for CDH 5.5 (5.5.1) as >> https://github.com/chiastic-security/phoenix-for-cloudera/tree/4.6-HBase-1.0-cdh5.5 >> and renamed the branch for CDH

Re: Hbase on EMR for phoenix

Bigtop packages HBase 0.98 and is something Phoenix still supports. The latest HBase release is 1.1. I think Bigtop will be moving up to HBase 1.1 soon. Phoenix supports that version as well. On Thu, Feb 4, 2016 at 4:48 PM, j pimmel wrote: > Thanks for the update James. > > Is the latest HBase

Re: java core dump

You might also consider moving back down to 7u79 > On Feb 15, 2016, at 10:35 AM, Jonathan Leech wrote: > > Has anyone else seen this? Happening under load in jdk 1.7.0_80 / phoenix > 4.5.2 - cloudera labs. Based on the source code, It seems the JVM is calling > the wrong toObject(), and then

Re: Write path blocked by MetaDataEndpoint acquiring region lock

Is 1000 a good default? On Wed, Feb 17, 2016 at 9:42 AM, Nick Dimiduk wrote: > Thanks for the context Arun. > > For what it's worth, I greatly increased the batch size (from default > 1,000 to 500,000), which i believe reduced contention on the lock and > allowed ingest to catch up. > > On Tue,

Re: YCSB with Phoenix?

The brianfrankcooper github repo (https://github.com/brianfrankcooper/YCSB) is still the "official" home of YCSB as far as I know. YCSB ships with a JDBC client driver. Just use that with the Phoenix client jar on the classpath and the correct connection string for Phoenix. What patch is this J

Re: YCSB with Phoenix?

Never mind that last question. Check the email thread and ye shall find the answer... > On Feb 19, 2016, at 11:10 AM, Andrew Purtell wrote: > > The brianfrankcooper github repo (https://github.com/brianfrankcooper/YCSB) > is still the "official" home of YCSB as far as I

Re: Retiring empty regions

> the shell and find the empty ones, another to merge a given region into a neighbor. We've run them without incident, looks like it all works fine. One thing we did notice is that the AM leaves the old "retired" regions around in its counts -- the master status page shows a large number of "Other

Re: phoenix on non-apache hbase

> is cloudera's hbase 1.2.0-cdh5.7.0 that different from apache HBase 1.2.0? Yes As is the Cloudera HBase in 5.6, 5.5, 5.4, ... quite different from Apache HBase in coprocessor and RPC internal extension APIs. We have made some ports of Apache Phoenix releases to CDH here: https://github.com

Re: phoenix on non-apache hbase

ut in yours too? Does it work if > you did? > > Thanks, > Ben > > >> On Jun 9, 2016, at 7:47 PM, Andrew Purtell wrote: >> >> > is cloudera's hbase 1.2.0-cdh5.7.0 that different from apache HBase 1.2.0? >> >> Yes >> >> As is t

Re: phoenix on non-apache hbase

l on CDH 5.5.2, can I just use your custom version? Phoenix >> is one of the reasons that we are blocked from upgrading to CDH 5.7.1. Thus, >> CDH 5.7.1 is only on our test cluster. One of our developers wants to try >> out the Phoenix Spark plugin. Did you try it out in yours too? Do

Re: Phoenix has slow response times compared to HBase

On Sep 3, 2016, at 10:09 AM, James Taylor wrote: > > > Why not 0.98.21? > I think it's just because Mujtaba already had 0.98.17 on that particular box. > I don't expect for this particular benchmark it would change anything, though. > >> On Sat, Sep 3, 2016 at

Re:

Phoenix has to be patched to work with Cloudera's HBase derivative. You might try https://github.com/chiastic-security/phoenix-for-cloudera/tree/4.9-HBase-1.2-cdh5.9 Check out this tree and build. The procedure for building is the same (https://phoenix.apache.org/building.html) This will pick u

Re: Still having issues

If you are using CDH, Phoenix has to be patched to work with Cloudera's HBase derivative. You might try https://github.com/ chiastic-security/phoenix-for-cloudera/tree/4.9-HBase-1.2-cdh5.9 Check out this

Re: Phoenix 4.9 on Hbase 1.3.0

Look at the fix versions on HBASE-17587 for a released or soon to be released version containing the fix. > On Mar 21, 2017, at 8:30 AM, James Taylor wrote: > > The bug is HBASE-17587. > Thanks, > James > >> On Tue, Mar 21, 2017 at 7:54 AM Mike Prendergast >> wrote: >> According to the link

Upcoming HBase/Phoenix in Hyderabad

Greetings HBase and Phoenix users. If you are in the neighborhood there will be a HBase/Phoenix meetup in Hyderabad, India this Friday. Apologies for the short notice. For more information, please see https://www.meetup.com/HBase-Phoenix-in-Hyderabad -- Best regards, Andrew

Re: Phoenix system tables in multitenant setup

There is some work in progress* to make it so only global read privilege on some SYSTEM tables will be necessary for clients to continue to function normally for DML operations. For DDL operations, the embedded Phoenix metadata service (MetaDataEndpoint) will modify system tables on behalf of a sui

Anonymous survey: Apache HBase 1.x Usage

Please take this anonymous survey ​ to ​ let us know what version of Apache HBase 1.x you are using in production now or are planning to use in production in the next year or so. Multiple choices are allowed. ​There is no "I'm not using 1.x" choice. Consider upgrading! (smile) https://www.survey

Re: Anonymous survey: Apache HBase 1.x Usage

Response to the survey so far. I think it confirms our expectations. Multiple choice was allowed so percentage will not add up to 100%. 1.0: 8% 1.1: 21% 1.2: 47% 1.3: 24% 1.4: 8% 1.5: 5% [image: Inline image 1] On Fri, Feb 2, 2018 at 3:40 PM, Andrew Purtell wrote: > Please take this anonym

Re: Anonymous survey: Apache HBase 1.x Usage

> > Mind share the number of votes boss? Please forgive my ignorance if it's > shown in the inline image since I cannot read it (picture failed to open) > > Best Regards, > Yu > > On 8 February 2018 at 09:07, Andrew Purtell wrote: > > > Response to the surv

[ANNOUNCE] Apache HBase 1.3.5 is now available for download

The HBase team is happy to announce the immediate availability of Apache HBase 1.3.5. Download from http://hbase.apache.org/downloads Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions

[ANNOUNCE] Apache HBase 1.4.10 is now available for download

The HBase team is happy to announce the immediate availability of Apache HBase 1.4.10. Download from http://hbase.apache.org/downloads Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with million

Re: [ANNOUNCE] New VP Apache Phoenix

Congratulations on the new role Ankit. On Thu, Apr 16, 2020 at 8:14 AM Josh Elser wrote: > I'm pleased to announce that the ASF board has just approved the > transition of VP Phoenix from myself to Ankit. As with all things, this > comes with the approval of the Phoenix PMC. > > The ASF defines

Re: [ANNOUNCE] New Phoenix committer Viraj Jasani

Congratulations, Viraj! > On Feb 9, 2021, at 2:07 PM, Geoffrey Jacoby wrote: > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Viraj > Jasani has accepted the PMC's invitation to become a committer on Apache > Phoenix. > > We appreciate all of the great contributions Viraj

Is anyone using OMID or Tephra in production?

At my employer we maintain a fork of Phoenix that we try to keep as close to open source as possible given our internal requirements. One issue we are facing in recent months is a tightening corporate policy on the presence of known software vulnerabilities in our dependencies. Of course, this mean

Re: [ANNOUNCE] Rushabh Shah as Phoenix Committer

Congratulations and welcome, Rushabh! > On Aug 15, 2023, at 1:46 PM, Viraj Jasani wrote: > > On behalf of the Apache Phoenix PMC, I'm pleased to announce that Rushabh > Shah has accepted the PMC's invitation to become a committer on Apache > Phoenix. > > We appreciate all of the great contrib