[GitHub] ignite pull request #810: Ignite 3184

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/810 Ignite 3184 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-3184 Alternatively you can review and apply these

[GitHub] ignite pull request #809: IGNITE-3139 .NET: UTF-16 surrogate symbols are not...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/809 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-3330) CPP: Implement Cache::Invoke method.

Igor Sapego created IGNITE-3330: --- Summary: CPP: Implement Cache::Invoke method. Key: IGNITE-3330 URL: https://issues.apache.org/jira/browse/IGNITE-3330 Project: Ignite Issue Type: Sub-task

Re: IGNITE-3293 AWS bootstrap scripts patch for Ignite-Cassandra

I'm reviewed this issue. Comments added to ticket. On Mon, Jun 13, 2016 at 10:42 PM, Igor Rudyak wrote: > Could somebody please look at the pull request > https://github.com/apache/ignite/pull/794 related to > https://issues.apache.org/jira/browse/IGNITE-3293 ticket. > > It's

[GitHub] ignite pull request #809: IGNITE-3139 .NET: UTF-16 surrogate symbols are not...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/809 IGNITE-3139 .NET: UTF-16 surrogate symbols are not serialized properly You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite

[jira] [Created] (IGNITE-3329) .NET: TestDeployNodeSingleton fails sporadically

Pavel Tupitsyn created IGNITE-3329: -- Summary: .NET: TestDeployNodeSingleton fails sporadically Key: IGNITE-3329 URL: https://issues.apache.org/jira/browse/IGNITE-3329 Project: Ignite Issue

[GitHub] ignite pull request #803: IGNITE-3311 .NET: Include configuration schema in ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/803 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-3328) .NET: cacheConfiguration.AffinityFunction

Pavel Tupitsyn created IGNITE-3328: -- Summary: .NET: cacheConfiguration.AffinityFunction Key: IGNITE-3328 URL: https://issues.apache.org/jira/browse/IGNITE-3328 Project: Ignite Issue Type:

[GitHub] ignite pull request #748: IGNITE-3182 Compute jobs execute on client nodes

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/748 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #782: IGNITE-3105 .NET: Fix ContinuousQueryAbstractTest....

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/782 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (IGNITE-3327) .NET: Pass all logging through Java side

Pavel Tupitsyn created IGNITE-3327: -- Summary: .NET: Pass all logging through Java side Key: IGNITE-3327 URL: https://issues.apache.org/jira/browse/IGNITE-3327 Project: Ignite Issue Type:

Merged: When multiple addresses resolve to same name, TcpDiscoverySharedFsIpFinder fails on unregister

Kristian, Thanks again for improving Apache Ignite. I’ve just reviewed and merged your pull request. https://github.com/apache/ignite/pull/799/files Waiting for more contributions from your side! — Denis

[GitHub] ignite pull request #806: IGNITE-3317 .NET: Improve error message when jvm.d...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/806 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #804: Ignite gg 11237

Github user avinogradovgg closed the pull request at: https://github.com/apache/ignite/pull/804 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Maven conflicts within ignite-core from duplicated classes

We already have 2 dependencies at ignite-core: *javax.cache.cache-api* and *org.gridgain.ignite-shmem* (ASAIK we have an issue to redeploy org.gridgain.ignite-shmem as org.apache.ignite.ignite-shmem) On Thu, Jun 16, 2016 at 11:57 AM, Vladimir Ozerov wrote: > And why do we

Re: Change rest-http Java to JSON null transformation logic

Den, that was my main reason "consistency". Strings in java can be "null" and can be empty. But after serialization we lost this info. As for compatibility - I'm afraid it is impossible to fix. Only to change user code. On Thu, Jun 16, 2016 at 4:51 PM, Denis Magda wrote: >

Re: Change rest-http Java to JSON null transformation logic

Pavel, we cannot omit them. Because if JSON will be transformed back to Java and some java field has not null default value that will lead to not correct de-serialization in this case. On Thu, Jun 16, 2016 at 4:54 PM, Pavel Tupitsyn wrote: > Why do we even write null

[GitHub] ignite pull request #808: ignite-3239 Fix of java.io.IOException: Resource d...

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/808 ignite-3239 Fix of java.io.IOException: Resource deadlock avoided You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite

Re: Change rest-http Java to JSON null transformation logic

Pavel, in this case object will be serialized like : {"a": "null"} compare with {"a": null} On Thu, Jun 16, 2016 at 4:49 PM, Pavel Tupitsyn wrote: > Hi, > > What if there is an actual string with "null" value? > > Pavel. > > On Thu, Jun 16, 2016 at 12:44 PM, Vladislav

Re: Change rest-http Java to JSON null transformation logic

Vlad, Actually I implemented 2 custom serializers: one for null strings and another for null objects. But I think that it looks like a "workaround" for me. On Thu, Jun 16, 2016 at 4:44 PM, Vladislav Pyatkov wrote: > Hello, > > Why do you want this, if you can save full

Re: Change rest-http Java to JSON null transformation logic

Why do we even write null fields? Can we just omit them? This will be faster, more compact, and less ambiguous. Pavel. On Thu, Jun 16, 2016 at 12:51 PM, Denis Magda wrote: > This looks strange. Definitely for consistency reasons it makes sense that > all ‘null’ objects

Re: Change rest-http Java to JSON null transformation logic

This looks strange. Definitely for consistency reasons it makes sense that all ‘null’ objects including string are serialized as “null”. In regards to the compatibility stuff I think it can be resolved somehow. — Denis > On Jun 16, 2016, at 12:15 PM, Alexey Kuznetsov

Re: Change rest-http Java to JSON null transformation logic

Hi, What if there is an actual string with "null" value? Pavel. On Thu, Jun 16, 2016 at 12:44 PM, Vladislav Pyatkov wrote: > Hello, > > Why do you want this, if you can save full compatibility using custom > serializer for null value

[GitHub] ignite pull request #796: IGNITE-3151 I rework fixation, so that there was n...

Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/796 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] ignite pull request #807: Ignite 3233

Github user alexpaschenko closed the pull request at: https://github.com/apache/ignite/pull/807 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Change rest-http Java to JSON null transformation logic

Hello, Why do you want this, if you can save full compatibility using custom serializer for null value (ObjectMapper#setSerializerProvider)? On Thu, Jun 16, 2016 at 12:15 PM, Alexey Kuznetsov wrote: > Hi All! > > I'm working on migrating from outdated json-lib to

[jira] [Created] (IGNITE-3325) .NET: LINQ Take method does not work within CompiledQuery

Pavel Tupitsyn created IGNITE-3325: -- Summary: .NET: LINQ Take method does not work within CompiledQuery Key: IGNITE-3325 URL: https://issues.apache.org/jira/browse/IGNITE-3325 Project: Ignite

Change rest-http Java to JSON null transformation logic

Hi All! I'm working on migrating from outdated json-lib to Jackson issue IGNITE-3277 [1] and found that previous library serialize null strings as "" and null objects as "null", for example: {"a": "", "b": null} How about to serialize all values as "null" ? In this case we would definitely know

[jira] [Created] (IGNITE-3324) .NET: LINQPad Data Context Driver

Pavel Tupitsyn created IGNITE-3324: -- Summary: .NET: LINQPad Data Context Driver Key: IGNITE-3324 URL: https://issues.apache.org/jira/browse/IGNITE-3324 Project: Ignite Issue Type: New

Re: Maven conflicts within ignite-core from duplicated classes

And why do we afraid this dependency? It has "CLASS" retention so users do not need them in runtime, AFAIK. On Thu, Jun 16, 2016 at 11:19 AM, Vladislav Pyatkov wrote: > Why not just rename these classes? > > On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov

Re: Maven conflicts within ignite-core from duplicated classes

Why not just rename these classes? On Thu, Jun 16, 2016 at 11:16 AM, Semyon Boikov wrote: > As far as I know the only reason sources of Nullable are in Ignite - we > did not want to have any dependecy for 'core' module. > > On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda

Re: Maven conflicts within ignite-core from duplicated classes

As far as I know the only reason sources of Nullable are in Ignite - we did not want to have any dependecy for 'core' module. On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda wrote: > Hi Pete, > > CC-ing Ignite dev list to the thread as well. > > Igniters, up to today is there

Re: Maven conflicts within ignite-core from duplicated classes

Denis, I've created issue: https://issues.apache.org/jira/browse/IGNITE-3323 On Mon, Jun 13, 2016 at 10:04 AM, Denis Magda wrote: > Hi Pete, > > CC-ing Ignite dev list to the thread as well. > > Igniters, up to today is there any reason why we need to include sources > of

[jira] [Created] (IGNITE-3323) Get rid of copypasted JB annotations, use dependency instead.

Anton Vinogradov created IGNITE-3323: Summary: Get rid of copypasted JB annotations, use dependency instead. Key: IGNITE-3323 URL: https://issues.apache.org/jira/browse/IGNITE-3323 Project: