[GitHub] ignite pull request #868: IGNITE-2598 - Enum arguments in SQL queries are no...

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/868 IGNITE-2598 - Enum arguments in SQL queries are not considered with B… …inaryMarshaller. - Query arguments are converted to binary objects now if binary marshaller used. You can

Re: IGNITE-3055

Ok, then I would go for IgniteDataStreamerTimeoutException. — Denis > On Jul 13, 2016, at 6:08 AM, Dmitriy Setrakyan wrote: > > On Tue, Jul 12, 2016 at 2:40 PM, Denis Magda wrote: > >> Personally, I don’t get why we need to have specific timeout related >> exceptions. My preferences is to sto

Re: set ExpiryPolicy does not work in C# client code

WithExpiryPolicy() returns another instance of ICache with overridden expiry policy and you should use this new instance to do the Put. So the code should look like this: cache.WithExpiryPolicy(new ExpiryPolicy(TimeSpan.FromMilliseconds(100), TimeSpan.FromMilliseconds(100), TimeSpan.FromMillis

Re: IGNITE-3055

On Tue, Jul 12, 2016 at 2:40 PM, Denis Magda wrote: > Personally, I don’t get why we need to have specific timeout related > exceptions. My preferences is to stop this practice starting from > IgniteDataStreamer and create generic TimeoutException that can be used by > the new features later. >

set ExpiryPolicy does not work in C# client code

Guys, I test below code and found the key(key1) still exists after 100 milliseconds(even longer), seems cache.WithExpiryPolicy does not work? Can someone tell how to set ExpiryPolicy in config.xml? Thanks much! Code snippet: public static void WriteTestCache(IIgnite ignite)

Re: kick off a discussion

Hi Alex, I believe most of your comments have to do with disk-based functionality, especially in regard to backups, snapshots, etc. However, Ignite is currently an in-memory system, at least for the nearest future. Let me know if I misunderstood something. D. On Tue, Jul 12, 2016 at 9:44 PM, Ale

Re: kick off a discussion

On Tue, Jul 12, 2016 at 6:44 PM, Konstantin Boudnik wrote: > On Mon, Jul 11, 2016 at 08:15AM, Dmitriy Setrakyan wrote: > > > > I think you mean data center replication here. It is not an easy feature > to > > implement, and so far has been handled by commercial vendors of Ignite, > > e.g. GridGa

[GitHub] ignite pull request #867: Ignite 1849

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/867 Ignite 1849 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1849 Alternatively you can review and apply the

[jira] [Created] (IGNITE-3471) Do not send previous value to client node for invoke() when possible

Alexey Goncharuk created IGNITE-3471: Summary: Do not send previous value to client node for invoke() when possible Key: IGNITE-3471 URL: https://issues.apache.org/jira/browse/IGNITE-3471 Project:

[jira] [Created] (IGNITE-3470) Continuous queries should support EXPIRED events

Valentin Kulichenko created IGNITE-3470: --- Summary: Continuous queries should support EXPIRED events Key: IGNITE-3470 URL: https://issues.apache.org/jira/browse/IGNITE-3470 Project: Ignite

[jira] [Created] (IGNITE-3469) Get rid of deprecated APIs and entities

Alexey Goncharuk created IGNITE-3469: Summary: Get rid of deprecated APIs and entities Key: IGNITE-3469 URL: https://issues.apache.org/jira/browse/IGNITE-3469 Project: Ignite Issue Type:

Re: Apache Ignite - New Release

Yakov, Is it possible to include several probably easy-to-fix bugs and improvements; they are very annoying and they decrease the value of the product? We're working on Apache Ignite based BI solution accelerator, and these issues impact us. I've opened them and I fix one and working on others.

[jira] [Created] (IGNITE-3468) Missing Primary Key flag in getColumns()

Alexandre Boudnik created IGNITE-3468: - Summary: Missing Primary Key flag in getColumns() Key: IGNITE-3468 URL: https://issues.apache.org/jira/browse/IGNITE-3468 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-3467) jdbc getTables() returns catalog as null

Alexandre Boudnik created IGNITE-3467: - Summary: jdbc getTables() returns catalog as null Key: IGNITE-3467 URL: https://issues.apache.org/jira/browse/IGNITE-3467 Project: Ignite Issue Typ

[jira] [Created] (IGNITE-3466) select * causes NoClassDefFoundError with jdbc query tools

Alexandre Boudnik created IGNITE-3466: - Summary: select * causes NoClassDefFoundError with jdbc query tools Key: IGNITE-3466 URL: https://issues.apache.org/jira/browse/IGNITE-3466 Project: Ignite

Re: kick off a discussion

Dmitriy, thank you for your time and questions, which helped me to realize what I forget to mentioned! See my answers inline; later I'll combine everything together to help to the next readers :) I put together some implementation ideas in Apache Ignite JIRA, as promised: https://issues.apache.org

Re: Apache Ignite - New Release

Yup, looks like having a minor bump is totally warranted. On Mon, Jul 11, 2016 at 10:11PM, Sergi Vladykin wrote: > Yakov, > > Good idea. > > Alexey, > > Why not just bump it to 1.7 as we do usually? > > Sergi > > > > On Mon, Jul 11, 2016 at 9:21 PM, Alexey Goncharuk < > alexey.goncha...@gma

Re: kick off a discussion

On Mon, Jul 11, 2016 at 08:15AM, Dmitriy Setrakyan wrote: > My answers are inline… > > On Sat, Jul 9, 2016 at 3:04 AM, Dmitriy Setrakyan > wrote: > > > Thanks Sasha! > > > > Resending to the dev list. > > > > D. > > > > On Fri, Jul 8, 2016 at 2:02 PM, Alexandre Boudnik > > wrote: > > > >> Apach

[jira] [Created] (IGNITE-3465) Java crash: problematic frame org.apache.ignite.internal.binary.BinaryObjectImpl.hashCode()

Ksenia Rybakova created IGNITE-3465: --- Summary: Java crash: problematic frame org.apache.ignite.internal.binary.BinaryObjectImpl.hashCode() Key: IGNITE-3465 URL: https://issues.apache.org/jira/browse/IGNITE-3465

Re: IGNITE-3055

Personally, I don’t get why we need to have specific timeout related exceptions. My preferences is to stop this practice starting from IgniteDataStreamer and create generic TimeoutException that can be used by the new features later. — Denis > On Jul 12, 2016, at 2:35 PM, Dmitriy Setrakyan wr

Re: IGNITE-3055

If other Timeout Exceptions are specific, shouldn’t this one be specific to data streamer as well, for consistency reasons, e.g. IgniteDataStreamerTimeoutExcepiton? On Tue, Jul 12, 2016 at 2:20 PM, Vladislav Pyatkov wrote: > Dmitriy, > > I discussed that with Denis and we have decided create new

Re: IGNITE-3055

Dmitriy, I discussed that with Denis and we have decided create new Exception type by some reasons: 1) The exception need to be unchecked (the behavior means serious problem in grid) hence, TimeoutException will implement IgniteException (as RintimeException). 2) Other timeout exception, which fo

Re: IGNITE-3055

Thanks Vlad. At a high level, the changes look OK. However, I am not sure about TimeoutException. Don’t we already have other timeout exceptions in Ignite? Can we reuse them? D. On Tue, Jul 12, 2016 at 1:51 PM, Vladislav Pyatkov wrote: > Dmitriy, > > I have added the description of changes in

Re: IGNITE-3055

Dmitriy, I have added the description of changes in the JIRA ticket. On Tue, Jul 12, 2016 at 1:28 PM, Dmitriy Setrakyan wrote: > Hi Vlad, > > Can you please list the API changes in the ticket, so others can review > without digging in code? > > Thanks, > D. > > On Mon, Jul 11, 2016 at 1:14 PM,

Re: IGNITE-3055

Hi Vlad, Can you please list the API changes in the ticket, so others can review without digging in code? Thanks, D. On Mon, Jul 11, 2016 at 1:14 PM, Vladislav Pyatkov wrote: > Igniters, > > I have implemented timeout in DataStreamer by issue IGNITE-3055 >

Re: Cache unhandled exception

I would add new event like UnhandledExceptioEvent. Presently it will be used for your scenario however in the future it can be reused for other cases. Other thoughts? — Denis > On Jul 11, 2016, at 7:26 PM, AndreyVel wrote: > > I have question about https://issues.apache.org/jira/browse/IGNITE

Re: Cache performance for LOCAL mode + setIndexedTypes

Andrey, the values clearly don’t make sense, which means that the test was conducted incorrectly. I would rerun it. On Tue, Jul 12, 2016 at 10:38 AM, Andrey Velichko wrote: > Agree, indexes consume CPU, but as shown in the table, > performance for index and CacheMode=LOCAL more then 2x. > > Ca

Re: Cache performance for LOCAL mode + setIndexedTypes

Agree, indexes consume CPU, but as shown in the table, performance for index and CacheMode=LOCAL more then 2x. CacheMode.CacheMode + TRANSACTIONAL = 45 K op./sec CacheMode.CacheMode + TRANSACTIONAL + setIndexedTypes = 107 K op./sec CacheMode.CacheMode + ATOMIC= 340 K op./sec CacheMode.C