Thanks a lot.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Michael,
The issue is almost fixed. The fix will be available as a part of Apache
Ignite 2.4 release.
On Tue, Dec 19, 2017 at 1:48 PM, Michael Jay <841519...@qq.com> wrote:
> Hi,has it been solved or is it a bug? I just met with the same
> problem.When I
> set "streaming=false" ,it worked,
It is a bug. Just created https://issues.apache.org/jira/browse/IGNITE-7248.
Sorry I forgot to create it before.
Hi,has it been solved or is it a bug? I just met with the same problem.When I
set "streaming=false" ,it worked, data can be inserted via JdbcClientDriver.
However, when streaming=true, I got message that said "schema not found" .
Thanks.
--
Sent from:
Hi James,
Can you please set "streaming=false" and try again? If it worked, I will
open a bug about this "schema not found" issue in the streaming mode.
Thanks!
Here is my code:
Connection igniteJdbcConnection =
DriverManager.getConnection("jdbc:ignite:cfg://streaming=true:cache=am_jdbc@file:/E:/ignite-jdbc.xml");
PreparedStatement igniteInsertPrepareStatement =
igniteJdbcConnection.prepareStatement("insert into Sample_Superstore(Row_ID,
...");
Above
James,
Just to confirm - are you saying that Statement.executeUpdate("create table
Sample_Superstore ...") throws that exception but still creates the cache
as expected?
I found out that following code in IgniteH2Indexing.java throws one
exception.
stmt.executeUpdate("SET SCHEMA " + H2Utils.withQuotes(schema));
In Ignite implementation, schema is "PUBLIC" at beginning during runtime,
then changed to "".
But I cannot figure out why my code get this
I am running a local server with native persistence.
CacheConfiguration cacheConfiguration = new
CacheConfiguration<>();
cacheConfiguration.setSqlSchema("public");
cacheConfiguration.setName("am_jdbc");
