Re: Issues with sub query IN clause

Thanks Dmitriy, The EXPLAIN PLAN [[SELECT STORE__Z1.ENTRYID AS __C0_0, STORE__Z1.ATTRNAME AS __C0_1, STORE__Z1.ATTRVALUE AS __C0_2, STORE__Z1.ATTRSTYPE AS __C0_3 FROM "dn".IGNITE_DN DN__Z0 /* "dn".IGNITE_DN.__SCAN_ */ /* WHERE ((DN__Z0.PARENTDN LIKE 'dc=ignite,%')

Re: Issues with sub query IN clause

Rajesh, can you please show your query here together with execution plan? D. On Thu, Feb 1, 2018 at 8:36 AM, Rajesh Kishore wrote: > Hi Andrey > Thanks for your response. > I am using native ignite persistence, saving data locally and as of now I > don't have

Re: Upcoming Apache Ignite events this month

Great to see such a busy schedule! Ignite community is unstoppable :) D. On Thu, Feb 1, 2018 at 3:19 PM, Tom Diederich wrote: > Igniters, > > The following is a list of upcoming events in February. To view this list > from the Ignite events page, click here >

Upcoming Apache Ignite events this month

Igniters, The following is a list of upcoming events in February. To view this list from the Ignite events page, click here . Tokyo February 1: Meetup: Meet Apache Ignite In-Memory Computing Platform Join Roman Shtykh at the Tech it Easy- Tokyo

Re: NPE in attempt to load checkpoint

Hi Val. Sorry i forgot to specify version. It is ver. 2.3.0#20171028-sha1:8add7fd5 As for the reproducer, i'll try to make it tomorrow -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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

Hello, Valentin. I try to take a look at this bug. В Чт, 01/02/2018 в 12:35 -0700, vkulichenko пишет: > Well, then you need IGNITE-3653 to be fixed I believe. Unfortunately, it's > not assigned to anyone currently, so apparently no one is working on it. Are > you willing to pick it up and

Re: Discovery node port range

By standalone cluster I just mean a regular Ignite cluster running independently from Spark. The easiest way is to start a node is using ignite.sh script providing proper configuration file. Once you switch IgniteContext to standalone mode, all nodes started within Spark processes will run in

Re: how to create instance of CacheManager of ignite

ak47, What exactly doesn't work? Can you describe the issue you're having? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC Thin Client with Transactions

If client node based driver [1] is used, then you can also add transactionsAllowed=true parameter to URL to overcome this error. This will NOT enable transactional support, but will force the driver to go through transaction related methods without exceptions. So for example, if there are several

Re: ignite.sh spring xml file secret.properties file not found error

Ganesh, If you provide full path, you don't need classpath: prefix. If you choose to have this file on classpath, then you should use the prefix and then provide the path relative to one of classpath roots. Also note that it has to be on classpath of your application, I don't know if $CLASSPATH

Re: Discovery node port range

Ranjit, Generally, removing and adding nodes in unpredictable way (which happens in embedded mode because we basically rely on Spark here) is a very bad anti pattern when working with distributed data. It can have serous performance implications as well as data loss. Data nodes are supposed to

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

I tried that, and it does work with it disabled but i needed the peerClassLoading enabled. we have a microservice setup and so lots of different things are interacting with our ignite cluster to get data. we have stuff making continuous queries and regular sql queries. so multiple different apps

Re: Issues with sub query IN clause

Hi Andrey Thanks for your response. I am using native ignite persistence, saving data locally and as of now I don't have distributed cache, having only one node. By looking at the doc, it does not look like affinity key is applicable here. Pls suggest. Thanks Rajesh On 1 Feb 2018 6:27 p.m.,

NPE in attempt to load checkpoint

Hi, I got exception*[1]* after 2nd execution (on 1-node grid) of my IgniteRunnable implementation which looks like this: *@ComputeTaskSessionFullSupport* public class ProcessStream implements IgniteRunnable { private static final long serialVersionUID = 6894222808783502630L; private

The wrong sockAddrs are registered, and the cluster is broken when it tries to connect it occasionally.

Cluster was broken some time ago. In my opinion, it seems to use Docker IP, not normal IP, in communication. Is it possible to register only the IP of the normal host to the IP? I want to remove 127.0.0.1 and 172.17.0.1 as shown in the log below. How to only register 10.xxx.xxx.x to Ignite

Re: Issues with sub query IN clause

Hi Rajesh, Possibly, you data is not collocated and subquery return less retults as it executes locally. Try to rewrite IN into JOIN and check if query with query#setDistributedJoins(true) will return expected result. It is recommended 1. replace IN with JOIN due to performance issues [1]. 2.

Issues with sub query IN clause

Hi All, As of now, we have less than 1 M records , and attribute split into few(3) tables with index created. We are using combination of join & IN clause(sub query) in the SQL query , for some reason this query does not return any response. But, the moment we remove the IN clause and use just

Re: CacheStore example for partitioned cache backed with a postgres database

Pim, Why you set WAL disabled? Do you use native ignite persistence together with CacheStore? If so, it is not supported, either native persistence or CacheStore should be used, but not both. On Sat, Jan 20, 2018 at 7:34 PM, Pim D wrote: > Hi, > > I can't seem to find a

Re: Option meta schema in cache level?

Hi, To get metadata prior to iterating over cursor, you can try to cast cursor to internal class QueryCursorImpl and call #fieldsMetadata(). On Sun, Jan 21, 2018 at 11:27 PM, mamaco wrote: > I'm trying to use Binary Marshaller to replace old OptimizedMarshaller > which > is

Re: Question about 'table' created by JDBC

Hi, 1. No, it is not supported. It is possible to store entries of different types in same cache, so such metadata is not available from cache level. Types look strange as they are autogenerated names. Seems, you didn't specify key\value types in create table clause [1] and no QueryEntity [2]

Re: Apache Ignite & unixODBC and truncating text

I'm currently working on the fix. Sorry guys, I was not able to fit it in 2.4. I can share a separate patch when it will be ready though if you like. Best Regards, Igor On Tue, Jan 30, 2018 at 5:45 AM, Rick Alexander wrote: > Hey Igor or anyone who knows, > > Looking to

Re: Rebalancing mode set to None

But currently you start the same Ignite nodes which you will start in standalone mode, but you run them embedded. If you have 3 backups in the cluster and one of your nodes fails, then part of your data will have 2 backups. Also, after the returning to the cluster, without manual rebalancing,

Re: Memory usage by ignite nodes

Thanks Dmitrty. On Wed, Jan 24, 2018 at 8:27 PM, dkarachentsev wrote: > Hi Ranjit, > > That metrics should be correct, you also may check [1], because Ignite > anyway keeps data in offheap. But if enabled on-heap, it caches entries in > java heap. > > [1]

Re: Persistent Store Not enabled in Ignite Yarn Deployment

Hello! Unfortunately it's hard to tell why the node would stop without looking at client & server logs. Can you share these somewhere? Maybe you should also set memory policy for these nodes, to the values that your Yarn configuration expect them to have:

Re: Integration with Hibernate 5.2.X for L2 Cache?

Hi, Here is a ticket for Hibernate 5.2+ support [1]. Hope, it will be fixed in ignite-2.5 release. [1] https://issues.apache.org/jira/browse/IGNITE-5848 On Thu, Jan 18, 2018 at 5:25 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi, > > Hibernate 5.2.x requires java 8, while

Re: a2cf190a-6a44-4b94-baea-c9b88a16922e, class org.apache.ignite.IgniteCheckedException:Failed to execute SQL query

Hello Rahul! Unfortunately both nodes' loggers aren't properly configured, not all messages are there and it's hard to follow up relative times on both nodes. Moreover, according to logs, they are both client nodes (even one in igniteServer.log), and I am not sure if they are on the same

Re: Rebalancing mode set to None

yes i am using it in embeded mode. Standalone mode we can go for, but additional hardware needed for that which will stay idle when we don't use it. That was the reason to try this embedded stuff. We build the cache on fly , which gets shut down with spark. My question basically was, when i set

Re: Rebalancing mode set to None

> When due to some reason a task fails, the ignite node stops and when the task re-starts, Looks like you run in embedded mode. Do avoid too frequently node stopping events, you need to run Ignite in standalone mode, in this case, the node will run even if your task fails. Please let me know if I

Re: Re: Cannot connect the ignite server after running one or two days

OK. I’ll try it when the problem appears next time. Thanks. 发件人: Evgenii Zhuravlev [mailto:e.zhuravlev...@gmail.com] 发送时间: 2018年2月1日 16:13 收件人: user@ignite.apache.org 主题: Re: 答复: Re: Cannot connect the ignite server after running one or two days " Failed to deserialize object " is

Re: Rebalancing mode set to None

I read the data which is in avro format using spark sql and load it to cache from spark program. I build the Ignite key-store inside spark executors. When due to some reason a task fails, the ignite node stops and when the task re-starts, the new node joins back.I see slowness from here onwards. I

Re: Rebalancing mode set to None

Ranjit, How do you load data to the cache? Evgenii 2018-02-01 11:18 GMT+03:00 Ranjit Sahu : > Hi Val, > > Not always but out of 10, we see at least once the issue. Whats happening > is when one node crashes\stops the new node joins . The loading process > restarts but

Re: Rebalancing mode set to None

Hi Val, Not always but out of 10, we see at least once the issue. Whats happening is when one node crashes\stops the new node joins . The loading process restarts but what ever was happening in few minutes (3-5) goes to 2-3 hours. Thanks, Ranjit On Wed, Jan 31, 2018 at 3:12 AM, vkulichenko

RE: Key Value Store - control TTL refresh

Hi, Whenever an entry is touched, the expiry policy of the view that was used for that will be consulted to get a new TTL. It means that each time you touch an entry through a view with `EternalExpiryPolicy` its TTL will be reset to ETERNAL. You could say that the `bypassCache` from your example

Re: 答复: Re: Cannot connect the ignite server after running one or two days

" Failed to deserialize object " is just a consequence of the cause exception, as you see from stacktrace - Caused by: java.net.SocketException: Socket closed. Could you run netstat -apnt on server when you face this problem and share results here? 2018-02-01 11:04 GMT+03:00 xiang jie

答复: Re: Cannot connect the ignite server after running one or two days

But from server ping client is OK. And from log file, It seems communication is OK before " Failed to deserialize object " error. It really confuses me. [2018-01-30 07:40:41,646][DEBUG][exchange-worker-#42%igniteCosco%][GridDhtPartitionDeman der] Adding partition assignments: