Re: Add new event in putblic API

Dmitriy, In cases where ContinuousQuery Event unmarshalling failed we have to inform node's owner somehow. Failed CQ event means you'll just get no event, no exception, and you'll have no need to read logs. Currently, we have no possibility to inform user except writing error message to logs.

[jira] [Created] (IGNITE-4177) .NET: Remove PlatformAsyncTarget and remove future-related code from PlatformTargetProxy

Pavel Tupitsyn created IGNITE-4177: -- Summary: .NET: Remove PlatformAsyncTarget and remove future-related code from PlatformTargetProxy Key: IGNITE-4177 URL: https://issues.apache.org/jira/browse/IGNITE-4177

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

I will take a look on PR today. On Mon, Nov 7, 2016 at 11:35 AM, Roman Shtykh wrote: > Denis, > It is https://github.com/apache/ignite/pull/1212 > > Thank you, > Roman > > > On Saturday, November 5, 2016 4:56 AM, Denis Magda < > dma...@gridgain.com> wrote: > > >

Re: IGNITE-3999: Design discussion

Hi Amir, Having POJO class QueryField looks like a good idea to me. Because we will be able to encapsulate more field information into it over time. E.g. we can add "keyField" flag for DML there. I would even think about removing map from method signature in favor of simple list/array: void

Re: IGNITE-3066 Set of Redis commands that can be easily implemented via existing REST commands

Denis, It is https://github.com/apache/ignite/pull/1212 Thank you, Roman On Saturday, November 5, 2016 4:56 AM, Denis Magda wrote: Roman, Would you mind making a pull-request? It’s not clear and easy to review using the branch you provided

[GitHub] ignite pull request #1212: IGNITE-3066: Set of Redis commands that can be ea...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/1212 IGNITE-3066: Set of Redis commands that can be easily implemented via existing REST commands You can merge this pull request into a Git repository by running: $ git pull

IGNITE-3999: Design discussion

Hi Igniters, I was looking into ticket IGNITE-3999 and I have a concern on this, can you please advise what will be the correct way to solve it. As of today, SQL fields are defined as setFields(LinkedHashMap fields), with introduction of case insensitive property need to create a

PR review

Hi Igniters, I raised PR for IGNITE-4176. Can you please review it and let me know? https://issues.apache.org/jira/browse/IGNITE-4176 -- Sincerely Yours Amir Akhmedov

[GitHub] ignite pull request #1211: IGNITE-4176: IgniteQueue not functioning as expec...

GitHub user amirakhmedov opened a pull request: https://github.com/apache/ignite/pull/1211 IGNITE-4176: IgniteQueue not functioning as expected after remove() You can merge this pull request into a Git repository by running: $ git pull https://github.com/amirakhmedov/ignite