Re: Wen-Console 2.3 (table for found)

Never mind,  I did not have the checkbox "Use selected cache as default schema name" selected. Shame on me Sorry, Carsten Am 18.11.2017 um 00:51 schrieb Carsten: Hello guys, since version 2.3 I can't execute any statements through the web console any more. Frontend, backend, and agent

Wen-Console 2.3 (table for found)

Hello guys, since version 2.3 I can't execute any statements through the web console any more. Frontend, backend, and agent (with credentials) are running and I can see the caches but every query fails with: [IgniteSQLException] Failed to parse query: select item from MyCache

Re: Question about SQL -> Cache

Hello, Yes, you can use both SQL and key-value APIs for the caches created with DDL. There is a GitHub project that shows how to achieve this with JDBC and Java: https://github.com/dmagda/ignite_world_demo The same can be done for ODBC and .NET.

Re: Out of memory in client node freezes complete cluster

Hello Amit, There are the plans to make the cluster to heal itself by kicking off unstable nodes or unblocking pending transactions if an abnormal situation happens: https://cwiki.apache.org/confluence/display/IGNITE/IEP-5+Cluster+reaction+if+node+detects+an+extraordinary+situations Created a

Re: Adding more ignite-clients slows down the first client

Tobias, I would also recommend to turn off Cassandra for now and confirm that the bottleneck is not in Ignite. — Denis > On Nov 13, 2017, at 7:48 AM, Mikhail wrote: > > Hi Tobias, > > if you need to do an initial loading of a big amount of data, please read >

Re: Trouble with v 2.3.0 on AIX

Thanks Vladimir, Here is a ticket: https://issues.apache.org/jira/browse/IGNITE-6952 — Denis > On Nov 13, 2017, at 7:43 AM, Vladimir wrote: > > Logs uploaded. Node1 started first. Node2 couldn't join the cluster. Search

Re: [Ignite 2.0.0] Stopping the node in order to prevent cluster wide instability.

Looking at the source code of the master I couldn’t get how this NPE can happen. Please upgrade to 2.3.0 and let us know if you still observe the bug. — Denis > On Nov 12, 2017, at 4:27 AM, dark wrote: > > Another Ignite node logs here. > > Nodes are currently under

Re: Can client node use IgniteQueue?

Hi, What kind of issue did you hit? Do we have any ticket opened for it? — Denis > On Nov 10, 2017, at 7:50 AM, arunkjn wrote: > > I have also tried version 2.3 with the same issue. > Hi, > > I am still experiencing this issue with ignite version 2.2.0 > > Can you please

Re: Ignite Affinity Latency

Please share the source of the test you running. Preferably over GitHub. — Denis > On Nov 9, 2017, at 3:28 PM, rajivgandhi wrote: > > Not much - it is basically a filtering operation. > > The throughput is no more that 200-300 TPS tops > > > > -- > Sent from:

Question about SQL -> Cache

(Context - working in C#) Vanilla single node cluster, no persistence (yet). I executed a DDL statement via ODBC (CREATE TABLE BLAH (RecID varchar PRIMARY KEY, Value1 varchar)) I see a cache was created via the web console (SQL_PUBLIC_BLAH). I executed an Insert via ODBC (INSERT INTO BLAH

Re: Deserialization error with Ignite 2.3.0

Andrey, This ticket seems to be about the same issue: https://issues.apache.org/jira/browse/IGNITE-6944 Can you please take a look and provide your thoughts? -Val On Tue, Nov 7, 2017 at 4:02 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > *cross-posting to dev* > > Hi Chris,

Re: Initial query resent the data when client got reconnect

Hi, Ignite presently does not support auto-incremental keys. You can start discussing this feature on the Ignite Dev list and open an enhancement request if the Community agrees it worths implementation. Right you can use Ignite's AtomicSequence

Re: IgniteInterruptedException: Node is stopping

Hi Hyma, looks like your job takes too much time, you hit some timeout and spark killed your jobs. I don't see any other errors or warnings from your logs, it's very likely that you need to increase some time out in spark. thanks, Mike. -- Sent from:

Re: "select ... from (select ... from) where" doesn't work

Hi Matija, Nested select is supported by Ignite, could you please share a small pom based reproducer for the problem, it could be a configuration problem, but there's not enough information to help you. Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: binary object affinity collocation

Hi, You have a mistake in configuration: "uid" must be a part of a key, a custom affinity can't be done for entry filed, only for key field. So you need to make a complex key for IdMatching, the one part of it must be "uid". Thanks, Mike. -- Sent from:

IgniteInterruptedException: Node is stopping

Hi, When loading ignite cache, we saw the spark job went into hung state at this step. We see one of the executor task has been running for hours and below are the logs from this executor that had the failure. Stdout log Launch class org.apache.spark.executor.CoarseGrainedExecutorBackend by

Re: Initial query resent the data when client got reconnect

Hello, When node disconnected from cluster, server's nodes close query listener and lose information about updates which were already sent to client. You should query again for avoiding this situation. Server nodes don't keep the information when node goes out from clustre because it can lead to

Re: Failed to connect to address issue

Hi, could you please share the full logs from all your nodes? Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Scan query failed if set deploymentMode to Private

Hi, it sounds like a bug, I'll try to reproduce it and if it's so, I'll create a ticket for this. Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite ODBC Driver v/s Ignite C++ driver

That's right. You can watch it for update notifications. Best Regards, Igor On Fri, Nov 17, 2017 at 2:37 PM, kotamrajuyashasvi < kotamrajuyasha...@gmail.com> wrote: > Hi > > Yes.. around 100-150 C++ processes or may be threads will be running on a > machine, but each process/thread requires to

Re: Ignite ODBC Driver v/s Ignite C++ driver

Hi Yes.. around 100-150 C++ processes or may be threads will be running on a machine, but each process/thread requires to use a separate transaction. I found out that along with sql transactions feature ticket, a separate ticket is present to implement transactions support for ODBC. Hope it will

Re: QueryEntity Based Configuration

Thank you,it's so clear. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: QueryEntity Based Configuration

You could introduce an additional Model data cache that will store *data* for each Model as it is usually done in a regular ORM systems (http://docs.jboss.org/hibernate/orm/5.2/userguide/html_single/Hibernate_User_Guide.html#collections-map) The key for the Model data cache should include the key

binary object affinity collocation

Hi, I am trying to retrieve collocate data with join two different caches. In the caches, there are 10 rows for each. If I set DistributedJoins to false than It retrieves 5 records, If I set DistributedJoins to true, It retrieves 10 records(correct one). But with affinity collocation it should

Failed to connect to address issue

Hi there, My cluster always has the exception like below at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.processDiscoveryMessage(ClientImpl.java:1874) [ignite-core-2.3.0.jar!/:2.3.0] at