You can try a few things:
- salt your table by tacking on a SALT_BUCKETS=n where n is related to
the size of your cluster. Perhaps start with 16.
- lead your primary key constraint with core desc if this is your
primary means of accessing this table.
- add a secondary index over core desc if this
Hey Dan,
There were some changes in the test framework to make them run faster.
Our entire test suite can run in about 10-15mins instead of 60mins
now. One of the new requirements is adding the annotation that Samarth
indicated. Once JUnit releases 4.12, this will no longer be necessary,
as the
I'm having trouble connecting to Phoenix 2.2.2 from scala. What am I doing
wrong?
[hivedata@hivedev1 phoenix-debug]$ scala -classpath lib/phoenix-2.2.2.jar
Welcome to Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java
1.7.0_51).
Type in expressions to have them evaluated.
Type :help
Hi there,
I have a problem of HelloWorld example. http://phoenix.apache.org/faq.html
[stsuid@ana-poc-01:~/HDP]$java -cp
./HDP/phoenix/hadoop-2/phoenix-4.0.0-incubating-client.jar:. HelloWorld
Exception in thread main java.sql.SQLException: No suitable driver found for
jdbc:phoenix:ana-poc-01
Hi Russell,
I am not a Scala guy, but do you know if calling
classOf[com.salesforce.phoenix.jdbc.PhoenixDriver]
ends up loading the java class and hence executing the static block? If it
doesn't you might want to try DriverManager.registerDriver(
com.salesforce.phoenix.jdbc.PhoenixDriver) and
If I disable the metrics stuff on every query everything works fine btw.
Therefore, I don't think it's anything related to tests.
On Fri, Aug 29, 2014 at 3:03 PM, Samarth Jain samarth.j...@gmail.com
wrote:
+ Jesse
I think Jesse probably envisioned early use of annotations to be around
