client.ScannerCallable: Ignore, probably already closed, Name: 3085, already closed?

Hi, I am running a query that takes a long time, via sqlline.py, but I am repeatedly getting 15/09/29 08:54:27 WARN client.ScannerCallable: Ignore, probably already closed org.apache.hadoop.hbase.UnknownScannerException: org.apache.hadoop.hbase.UnknownScannerException: Name: 3085, already

Phoenix vs. Kudu performance

interesting comparison of Impala/Kudu vs. Hbase/Phoenix (section 6.3): http://getkudu.io/kudu.pdf

Re: Error with union all and a hint

By default if there is an index defined for a table, the index will be used if the plan with the index is better. Please file a Jira for the NPE. Thanks, Alicia From: Gašper Metelko > Reply-To:

RE: Error with union all and a hint

I have created the jira PHOENIX-2295. Running the query without the hint, executes the statment with a full table scan: 0: jdbc:phoenix:localhost> explain SELECT col1, col2 FROM table1 WHERE col1='123';

Re: integration Phoenix and Spark

Hi, Just to add that, at least for hadoop-2.7.1 and phoenix 4.5.2-HBase-1.1, hadoop guava lib has to be patched to 14.0.1 (under hadoop/share/hadoop/common/lib) otherwise spark tasks might fail due to missing guava methods. Cheers On 29/09/15 10:17, Hardika Catur Sapta wrote:

integration Phoenix and Spark

Spark setup 1. Ensure that all requisite Phoenix / HBase platform dependencies are available on the classpath for the Spark executors and drivers 2. One method is to add the phoenix-4.4.0-client.jar to ‘SPARK_CLASSPATH’ in spark-env.sh, or setting both ‘spark.executor. 3.

a good hbase config to work with phoenix and very large tables

Hi, anyone wants to share a good config that will work for not-so-fast clusters (7200rpm disks) and very large tables? I got a cluster of 3x region servers on lxc-virtual boxes on a 16-core machine with 3x7200rpm disks. Each region server runs on a virtual box using one of the disks and with

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

Welcome, Jan. Great to have you onboard as a committer! James On Tuesday, September 29, 2015, Andrew Purtell wrote: > Congratulations Jan, and welcome! > > > On Tue, Sep 29, 2015 at 11:23 AM, Eli Levine > wrote: > > > On behalf of the

[ANNOUNCE] New Apache Phoenix committer - Jan Fernando

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 contributions are: 1) Worked deeply in the sequence code including implementing Bulk Sequence Allocation:

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

Congrats Jan! 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

Re: integration Phoenix and Spark

Make sure to double check your imports. Note the following from https://phoenix.apache.org/phoenix_spark.html import org.apache.spark.SparkContext import org.apache.spark.sql.SQLContext import org.apache.phoenix.spark._ There's also a sample repository here: