Thank you Ilya, it worked!
Em segunda-feira, 4 de junho de 2018 15:44:35 GMT-3, ilya.kasnacheev
escreveu:
Hello!
Yes, you should be able to do that by specifying WITH "VALUE_TYPE=..."
Look it up on readme.io:
https://apacheignite-sql.readme.io/docs/create-table
Regards,
--
Sent f
Hello!
Yes, you should be able to do that by specifying WITH "VALUE_TYPE=..."
Look it up on readme.io:
https://apacheignite-sql.readme.io/docs/create-table
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thank you Ilya.
Instead of configuring individual store dir on kubernetes pvc, I pointed the
workDirectory to the pvd and there is no more NPE, but after restarting the
whole cluster a new SQL class has been generated to represent the SQL cache.
visor> cache -scan -c=@c0
Entries in cache: SQL_PU
Hello!
I think this errors stems from the fact that you preserve persistence dir
between runs, but not Ignit work dir, and specifically not work/marshaller.
It is crucial to preserve contents of this directory between node restarts.
It is recommended to set workDirectory to some persistent locati
I have a similar issue.
If I run local, two nodes connected via TcpDiscoveryMulticastIpFinder it
works fine. But when I run o Kubernetes where the same two nodes are
connected by TcpDiscoveryKubernetesIpFinder Ignite throws those errors.
I have a test SQL table created:
CREATE TABLE TEST (KEY I
Mikhail,
I believe this NPE is already fixed as part of [1] and will be released in
2.4 version soon.
I'm going to close IGNITE-7458 as duplicate with corresponding JIRA link.
[1] https://issues.apache.org/jira/browse/IGNITE-6668
On Thu, Jan 18, 2018 at 3:03 AM, Mikhail
wrote:
> Hi Aaron,
>
>
Hi Aaron,
Can you always reproduce the issue?
Might be you have a reproducer for this issue?
I created a ticket:
https://issues.apache.org/jira/browse/IGNITE-7458
but I don't think that it will be fixed without a reproducer, so it will be
great if you'll provide one, I'll attach it to the tick
