Version: ignite 2.1.0
A custom IgniteLogger is passed in the configuration. The existing
java.util.logging configuration is still modified by ignite.
Cause:
IgniteJdbcDriver uses a static instance of a JavaLogger. The JavaLogger
modifies the java.util.logging configuration.
G. Simon
P.S.
Hi Mikhail,
Thanks for reply!
Sure, i will check it all on python 2.7.
Best Regards,
Valeriy
>
>
>Hi Valeriy,
>
>I'm not sure where is the bug, but it works fine with python 2.7.
>
>So for now I recommend to switch to python 2.7. It requires further debbuging
>to understand what is wrong with p
Hi team,
Congrats to all the contributor to ignite 2.1. The availability of Ignite
Persistent Store and hence a concept of Durable Memory on disk is a reality.
I quickly wanted to check one thing, that let us say one of my partitioned
nodes (the box itself) is restarted and it becomes part of th
Hi Nikolai,
As for now Ignite-Cassandra module always executes same CQL query on each
node while doing loadCache(...).
But you assumptions are right and there is a ticket for this:
https://issues.apache.org/jira/browse/IGNITE-3962
Igor
On Thu, Jul 27, 2017 at 10:28 AM, Nikolai Tikhonov
wrot
Hi,
I am trying to use BinaryObjects to create the cache at runtime. For
example, instead of writing a pojo class such as Employee and configuring
it as a cache value type, I need to be able to dynamically configure the
cache with the field names and field types for the particular cache.
I have p
Hi Alex,
Did you get an chance to look at this?
Now I am getting this error for both searchable and non-searchable caches.
Thanks,
Ankit Singhai
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-Illeg
