Re: Off-heap issue

Hi Peter, I don't see your code, so can hardly suggest anything else. According to your description, I'm pretty sure the logger instance is being serialized as a part of key or value object, but I have no idea why. I would start with running the app in debug and checking if my assumption is right

Re: Update performance

Hi Ionut, Yes, SQL updates are on the roadmap. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Update-performance-tp6214p6358.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: mybatis-ignite

Hi, First of all, please properly subscribe to the mailing list so that the community can receive email notifications for you messages. Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 As for the issue, looks like

Re: Off-heap issue

Hi Val, it's like: public class LoaderThread extends Thread { private static final Logger LOG = createProprietaryLogger(); private Ignite ignite; private IgniteCache cache; public LoaderThread(Ignite ignite) { this.ignite = ignite; this.cache =

Adding a binary object to two caches fails with FULL_SYNC write mode configured for the replicated cache

I am using ignite version 1.6. In my use case I have two caches with the below configuration CacheConfiguration cfg1 = new CacheConfiguration<>("Cache 1"); cfg1.setCacheMode(CacheMode.PARTITIONED);

Any plans to enhance support for subselects on partitioned caches?

Hello, I see that subselects on partitioned caches don't return the correct results in the current version (the subselect is ran only on the partition on the current node)[1]. Are there any plans to enhance this support in the near future? Thanks, Cristi [1]

Re: Removing or overwriting cache value, but still able to get it from the cache

Can you please attach a minimal code sample that reproduces the issue, including config file and cache store code? On Mon, Jul 18, 2016 at 10:32 AM, zshamrock wrote: > /Hi, you have readThrough enabled and a cache store defined, which is > causing > this behavior: >

Re: Store-by-reference

Hi Andi, Ignite doesn't support storing values by references without serializing them first because of it's distributed nature. So setting the property storeByValue has no effect. To avoid deserialization on every read you should use: CacheConfiguration.setCopyOnRead(false) 2016-07-18 11:20

Re: Removing or overwriting cache value, but still able to get it from the cache

Yes, Pavel, I will try to come with something reproducible. Not sure whether it is gonna be minimal or just a complete app setup (which is chunk of work, but will take a look into). Any ideas/theories, what I should take a look in the meanwhile? Thank you. -- View this message in context:

Re: Any plans to enhance support for subselects on partitioned caches?

Hi Cristi, There is a work in progress on supporting distributed joins without necessary data collocation, but it will work only for top level joins. What means you'll need to rewrite a query containing subselect to the identical query with join. 2016-07-18 17:01 GMT+03:00 Cristi C

Re: Adding a binary object to two caches fails with FULL_SYNC write mode configured for the replicated cache

Hi, Currently you have to make a copy of BinaryObject for each cache operation because it's not immutable and internally caches some information for performance reasons. Do you have a real case then you need to put a lot of binary object keys to multiple caches? BTW, if you are using

Re: Removing or overwriting cache value, but still able to get it from the cache

Can it be really because of the near cache? Near cache section of the Ignite documentation doesn't say much or explain the correct usage/caveats of the near cache https://apacheignite.readme.io/docs/near-caches. Is there more I can read somewhere? If I remove the values from the near-cache are

Re: Any plans to enhance support for subselects on partitioned caches?

Subquery in FROM clause should work with distributed joins enabled. Subquery expressions (in SELECT, WHERE, etc...) must always be collocated. Sergi On Mon, Jul 18, 2016 at 7:09 PM, Cristi C wrote: > Thanks for your reply, Alexei. > > So, considering users will be able

Re: Any plans to enhance support for subselects on partitioned caches?

On Mon, Jul 18, 2016 at 10:44 PM, Sergi Vladykin wrote: > Subquery in FROM clause should work with distributed joins enabled. > Subquery expressions (in SELECT, WHERE, etc...) must always be collocated. > Thanks, Sergi! This definitely helps. Is it going to be possible

Re: Removing or overwriting cache value, but still able to get it from the cache

Hi, Near cache is always consistent with the server cache. I.e., if you update the near cache, the update is propagated to the server nodes. Also, server nodes know about all near caches. So even if there are two clients with near caches, update on one of them will trigger the update on the

Re: How about adding kryo or protostuff as an optional marshaller?

Hi Lin, Do you have a GitHub project that I can run and compare these two marshallers? From these snippets it's not very clear what is actually serialized. Generally, Ignite does provide minimal overhead in the binary format, mainly to allow field lookups without deserialization, which is

Re: Update performance

BTW, here is the ticket for DML that you can follow: https://issues.apache.org/jira/browse/IGNITE-2294 -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Update-performance-tp6214p6359.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re: argument type mismatch of oracle TIMESTAMP field when call loadCache

Hello Bob We fix import of Oracle TIMESTAMP in issue: https://issues.apache.org/jira/browse/IGNITE-3394 It is available in master branch. It will be available in next nightly build. You can take it here: https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/

Re: How about adding kryo or protostuff as an optional marshaller?

Hi Val, I post the codes in GitHub https://github.com/jackeylu/marshaller-cmp, you can run and compare it. I am so glad that you can help me to choose the right serializes. I am not sure my cases is fair or not. And from my tests, I found that, 1. in most of the case of primitive types or

Re: Is there a way to get keyset except SQL query(select _key from ...)?

Hi, Right now there is no other way except iterating through entries and getting keys from them, but in this case you will fetch values as well. Later we will add an optional transformer to SCAN query [1] which will allow this functionality. What is the reason for not using SQL query? [1]

Is there a way to get keyset except SQL query(select _key from ...)?

I want to scan keys from ignite cache(except values) like this to reduce traffic and improve performance: /Iterator it = cache.keySetIterator(); while (it.hasNext()) { .. }/ *but I do not want to use SQL query(select _key from ...) for some reason, how can I achieve this by minimal

Re: Adding a binary object to two caches fails with FULL_SYNC write mode configured for the replicated cache

Please see my comments below > Currently you have to make a copy of BinaryObject for each cache operation > because it's not immutable and internally caches some information for > performance reasons. Isn't the BinaryObject not bound

Re: Update performance

Val, Thank you for your input. I don't understand what would be the significant overhead compared with what "invoke" method is already doing but I'm looking forward to see how "update" operation will be implemented in Ignite. I saw that there is such an item in the roadmap. Thanks, Ionut --

Re: Removing or overwriting cache value, but still able to get it from the cache

So, we have a REST endpoint which we can call with session id to stop a session. Which in result clear the cache. Which shows in Visor it works (cache is empty now). So, regards cache store (and read through) my expectations were: - because the cache is empty now - the next call to get() will

Re: Removing or overwriting cache value, but still able to get it from the cache

Hi, you have readThrough enabled and a cache store defined, which is causing this behavior: when readThrough is enabled, each cache.get() causes cacheStore.load call. Pavel. On Sun, Jul 17, 2016 at 6:03 PM, zshamrock wrote: > I have an interesting problem. > > I

Re: Removing or overwriting cache value, but still able to get it from the cache

Thank you, Pavel. This is fine. But the problem is that in the database I have the latest values, the one I see in Visor, but cache still returns the old value (which is not longer in the database). How it can be? -- View this message in context:

Re: Removing or overwriting cache value, but still able to get it from the cache

Another question is how I can configure the logger from the cache store used? I use Logback, so /private static final Logger logger = LoggerFactory.getLogger(SensorsToSessionsCacheStore.class);/, and do debug call: @Override public final V load(final K key) throws CacheLoaderException {

Store-by-reference

Hi, is there any way in Ignite, to store values by reference instead of always serializing cached values directly on insertion? When setting CacheConfiguration.storeByValue(false) and creating a new cache, nothing happens. I looked a bit through the JCache documentation and it does not say what