Hi Ryan,
The Apache Phoenix community doesn't manage the EMR bootstrap actions,
those are handled by EMR themselves. Unless one of the EMR folks is lurking
here, you'll probably have better luck by raising the issue on the AWS EMR
forum.
We do however manage our own getting started docs, and
And in addition for CREATE VIEW ... AS SELECT ...
your example
create view v2(a VARCHAR PRIMARY KEY, f1.c INTEGER) as select * from t1;
it seems that AS SELECT part is very limited. It looks like I can not
specify columns or any where clause there what kind of very
limits purpose of the VIEW.
Hi Ryan,
I suspect its a mismatch between the commons-collections version, as
the HTrace metrics framework requires a fairly new version (3.2.1). We
ran into that with PHOENIX-1613 and had to disable tracing when the
metrics initialization would fail. Perhaps this is another flavor of
something
Hello,
I have Phoenix 4.3.0 running on my local machine. I am using Hadoop 2.4.1
in psuedo-distributed mode and HBase 0.98.10.1-hadoop2.
I am able to connect to HBase with Phoenix using sqlline.py.
I am building a Java application to demonstrate a Cascading application
that uses Phoenix on
Hello Phoenix users,
I noticed that the CLI command for EMR is outdated and, at least for me,
not working. The bootstrap action fails. I'm referencing this page,
http://phoenix.apache.org/phoenix_on_emr.html.
I'm also unable to view the file using the following command,
aws s3 cp
Update: I checked out 4.0.1 branch from git and local build is underway.
On Fri, Mar 6, 2015 at 12:50 PM, anil gupta anilgupt...@gmail.com wrote:
Hi James/Mujtaba,
I am giving a tech talk of HBase on Monday morning. I wanted to demo
Phoenix as part of that. Installation of 4.0.0 jars can
4.0.1 failed with a JUnit failure:
Failed tests: testSkipScan(org.apache.phoenix.end2end.VariableLengthPKIT)
Tests run: 1115, Failures: 1, Errors: 0, Skipped: 4
I disabled JUnit from the build and it ran successfully.
On Fri, Mar 6, 2015 at 1:49 PM, anil gupta anilgupt...@gmail.com wrote: