[GitHub] ignite pull request: IGNITE-2050 - Remove duplicates from the conf...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/291 --- 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-2102) .NET: Simplify query examples

Vladimir Ozerov created IGNITE-2102: --- Summary: .NET: Simplify query examples Key: IGNITE-2102 URL: https://issues.apache.org/jira/browse/IGNITE-2102 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-2103) CPP: Simplify query examples.

Vladimir Ozerov created IGNITE-2103: --- Summary: CPP: Simplify query examples. Key: IGNITE-2103 URL: https://issues.apache.org/jira/browse/IGNITE-2103 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-2101) NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded.

Vladimir Ozerov created IGNITE-2101: --- Summary: NPE when trying to submit Hadoop job to a node where Hadoop module is not loaded. Key: IGNITE-2101 URL: https://issues.apache.org/jira/browse/IGNITE-2101

[GitHub] ignite pull request: IGNITE-2098 - Added test for java proxy.

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/301 IGNITE-2098 - Added test for java proxy. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agoncharuk/ignite ignite-2098 Alternatively you

[jira] [Created] (IGNITE-2107) Splitting TX example and adding new

Yakov Zhdanov created IGNITE-2107: - Summary: Splitting TX example and adding new Key: IGNITE-2107 URL: https://issues.apache.org/jira/browse/IGNITE-2107 Project: Ignite Issue Type: Task

[GitHub] ignite pull request: IGNITE-1692 test suite

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/300 --- 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-2108) CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node

Denis Magda created IGNITE-2108: --- Summary: CacheJdbcPojoStoreFactory is not fully initialized when deserialized on a remote node Key: IGNITE-2108 URL: https://issues.apache.org/jira/browse/IGNITE-2108

Re: NearCacheConfiguration extends MutableConfiguration

These properties do not make sense for near cache. I doubt if this has been done on purpose. What if we extend Configuration? Will it break anything? --Yakov 2015-12-08 6:06 GMT+03:00 Valentin Kulichenko : > Folks, > > I just noticed that NearCacheConfiguration

[jira] [Created] (IGNITE-2104) Marshalling fails with Binary marshaller if class hierarchy contains duplicate field names

Alexey Goncharuk created IGNITE-2104: Summary: Marshalling fails with Binary marshaller if class hierarchy contains duplicate field names Key: IGNITE-2104 URL:

[jira] [Created] (IGNITE-2106) BinaryMarshaller: near cache mustn't keep a copy on put() operation

Anton Vinogradov created IGNITE-2106: Summary: BinaryMarshaller: near cache mustn't keep a copy on put() operation Key: IGNITE-2106 URL: https://issues.apache.org/jira/browse/IGNITE-2106 Project:

Re: Binary marshaller issues

Vova, We still have the logic that allows us to use reflection to get values in indexing, so basically the change is an additional check during the query processor start. My concern regarding (2) is that a server node must have model classes in the classpath in order to check that we should

Re: More query examples

I think the same is valid for TXs - https://issues.apache.org/jira/browse/IGNITE-2107 Thanks! -- Yakov Zhdanov, Director R *GridGain Systems* www.gridgain.com 2015-12-08 9:07 GMT+03:00 Sergey Kozlov : > I filed https://issues.apache.org/jira/browse/IGNITE-2097 > > On Tue,

[GitHub] ignite pull request: Ignite 2064 2

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

[GitHub] ignite pull request: 2064 Test hotfix

Github user avinogradovgg closed the pull request at: https://github.com/apache/ignite/pull/297 --- 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: EA versioning

Cos, I think you are right, probably we have to release 1.5.0-b1 then stable bug-fix versions will be 1.5.1, 1.5.2... And then next release from master should be 1.6.0. Yes, this should work and then we will not need *final *qualifier. Sergi 2015-12-07 7:23 GMT+03:00 Konstantin Boudnik

[jira] [Created] (IGNITE-2111) .Net: Create a build script

Pavel Tupitsyn created IGNITE-2111: -- Summary: .Net: Create a build script Key: IGNITE-2111 URL: https://issues.apache.org/jira/browse/IGNITE-2111 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-2112) Provide a way to serialize/deserialize an IgniteConfiguration object using JSON

Juan Velez created IGNITE-2112: -- Summary: Provide a way to serialize/deserialize an IgniteConfiguration object using JSON Key: IGNITE-2112 URL: https://issues.apache.org/jira/browse/IGNITE-2112 Project:

Re: Handling collections in BinaryMarshaller

I like the idea, however it has obvious downsides. First, if a user class contains a collection, we force user to implement additional interface, even if the collection is a simple ArrayList. Second, I do not see how this plain collection can be the value for the cache - user will always need to

[jira] [Created] (IGNITE-2113) Yardstick scripts don't work under Solaris (SunOS)

Andrey Gura created IGNITE-2113: --- Summary: Yardstick scripts don't work under Solaris (SunOS) Key: IGNITE-2113 URL: https://issues.apache.org/jira/browse/IGNITE-2113 Project: Ignite Issue

Re: What is jdbc:ignite:cfg ??

Done. I hope that is more clear now. On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan wrote: > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura wrote: > > > Cos, > > > > sepcifies configuration file for Ignite client node that > will > > be started

Re: Handling collections in BinaryMarshaller

Vladimir, I believe the default collections in Java and .NET should be supported out of the box. Moreover, if we know the collection type, e.g. HashMap, we can always provide a more efficient way of serializing it ourselves, in the Binary marshaller. Is this something you had in mind, or were

Re: Binary marshaller issues

My preference would be to deserialize and grab the fields using reflection, assuming the class is available on the server. If the class is not available, then a corresponding field-access operation should produce an exception with a proper error message, instructing user how to address it. There

Re: What is jdbc:ignite:cfg ??

Thanks Andrey! In my view, we should also provide a sample XML configuration file, especially given that we refer to it in the sample URL. D. On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura wrote: > Done. I hope that is more clear now. > > On Tue, Dec 8, 2015 at 1:14 AM,

Re: NearCacheConfiguration extends MutableConfiguration

Are there any other properties from MutableConfiguration that NearCacheConfiguration requires? On Tue, Dec 8, 2015 at 3:47 AM, Yakov Zhdanov wrote: > These properties do not make sense for near cache. I doubt if this has been > done on purpose. > What if we extend

Re: Is there any plan to build an ignite web console ?

There are a couple more of 3rd party management consoles. ApacheIgniteExtensions - provides basic management functionality and ability to manually use Ignite REST API from a UI console: https://github.com/sumeet70/aiex GridGain Visor - a UI management tool with comprehensive management and

Idiomatic way of configuring caches on client

I'm working on Ignite Web Console. And this utility is generating XML and java code with cluster configuration. For server-side I generate XML and java code that describe caches. But should I do the same when generating client node configuration? I think that I should only generate

[jira] [Created] (IGNITE-2114) implemented ability to download configuration as independent logic

Dmitriyff created IGNITE-2114: - Summary: implemented ability to download configuration as independent logic Key: IGNITE-2114 URL: https://issues.apache.org/jira/browse/IGNITE-2114 Project: Ignite