Yes, a blog post will be of great help especially considering its not clear
when Amazon will upgrade their default version to 3.x or 4.x
On Sep 8, 2014, at 9:07 PM, James Taylor jamestay...@apache.org wrote:
Thanks, Puneet. That's super helpful. Was (2) difficult to do? That might
make an
How big is the table? I think, its taking so long to create the table
because phoenix creates a new column _0 for each row with null
values. So, when it failed the upserts were only partially complete but
table is available for querying. Since, view doesnt perform this upsert,
its faster to create
Hi,
Does PQS support HBase's timeline consistency (HBASE-10070)?
Looking at the connection properties implementation within Avatica, I see
that following are defined: ["transactionIsolation", "schema", "readOnly",
"dirty", "autoCommit", "catalog"] but there's isn't a property defined for
setting
LT_CONSISTENCY_LEVEL));
On Thu, Jan 19, 2017 at 2:35 PM, Tulasi Paradarami <
tulasi.krishn...@gmail.com> wrote:
> Hi,
>
> Does PQS support HBase's timeline consistency (HBASE-10070)?
>
> Looking at the connection properties implementation within Avatica, I see
> that following a
gt; closeStatement call (either from multiple callers) or the automatic-closing
> logic inside of PQS itself (by default, PQS will close statements that
> haven't been used for 10mins, IIRC).
>
> Any more information on the context in which you see this would be very
> helpful.
>
> Tu
avatica.connectioncache.expiryunit
avatica.statementcache.concurrency
avatica.statementcache.initialcapacity
avatica.statementcache.maxcapacity
avatica.statementcache.expiryduration
avatica.statementcache.expiryunit
On Thu, Jan 5, 2017 at 10:04 AM, Tulasi Paradarami <
tulasi.krishn...@gmail.com>
t; you want to do).
>
> You can try setting org.apache.calcite.avatica.jdbc.JdbcMeta=DEBUG in the
> $PHOENIX_HOME/bin/log4j.properties file. That will print some messages
> when a statement or connection is automatically evicted from the respective
> cache.
>
> Finally, no st
tatement, both trying to close the ResultSet.
>
> This is sounding more and more like an Avatica bug to me. Any chance you
> can share more of the TRACE logging that you've turned on and maybe open up
> a JIRA issue under the CALCITE project (and ping me), please?
>
> I real
We noticed that PQS started raising ArrayIndexOutOfBoundsException in our
production cluster. This exception is raised sporadically and goes away
when PQS is restarted. Does anyone know what might be causing this
exception? Are there any configuration (PQS and/or Avatica) parameters that
we can
Hi,
I'm running few tests against Phoenix array and running into this bug where
array elements return null values when a join is involved. Is this a known
issue/limitation of arrays?
create table array_test_1 (id integer not null primary key, arr tinyint[5]);
upsert into array_test_1 values
e initialized in
KeyValyColumnExpression for ARRAY elements during tuple projection. That
is, when projecting array elements, it should perhaps be initialized with
"_v, ", instead of "default cf, actual column qualifier"?
It'll be helpful to hear from the Phoenix experts on thi
Tested on 4.7, 4.11 & 4.14.
https://issues.apache.org/jira/browse/PHOENIX-4791
On Tue, Jun 19, 2018 at 8:10 PM Jaanai Zhang wrote:
> what's your Phoenix's version?
>
>
>
>Yun Zhang
>Best regards!
>
>
> 2018-06-20 1
12 matches
Mail list logo
