Re: What is jdbc:ignite:cfg ??

Andrey, I agree on both points. However, I still think that we should provide sample step-by-step guide with a sample configuration. This configuration should include a couple of data types, like Person and Organization, define indexes for them, etc. This guide should include: 1. Start Ignite

[jira] [Created] (IGNITE-2126) .Net binaries aren't included into binary fabric package

Sergey Kozlov created IGNITE-2126: - Summary: .Net binaries aren't included into binary fabric package Key: IGNITE-2126 URL: https://issues.apache.org/jira/browse/IGNITE-2126 Project: Ignite

Introduction letter.

Dear Igniters! My name is Vladimir Ershov, I am a software engineer from Saint-Peresburg, Russia. I have joined the community recently and I hope to find here a lot of possibilities to create and design new solutions, to apply and develop my skills, and to be helpful by taking part in the most

Changes for ignite-jms11 and ignite-mtqq modules for fabric binary package

Hi I built Apache Ignite fabric from branch ignite-1.5 and just found that one got some changes in optional modules: libs/optional/ignite-jms11/ jms-api-1.1-rev-1.jar replaced by geronimo-jms_1.1_spec-1.1.1.jar libs/optional/ignite-mqtt/ added guava-18.0.jar Could someone confirm that such

[GitHub] ignite pull request: Ignite 2064 3

Github user avinogradovgg closed the pull request at: https://github.com/apache/ignite/pull/308 --- 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: Idiomatic way of configuring caches on client

On Wed, Dec 9, 2015 at 6:07 AM, Alexey Kuznetsov wrote: > Alex, > > Thanks for your suggestions. We will generate server cache configs + client > near cache configs. > Sounds good. Let’s make sure we name them properly, so users will clearly understand which one is for

[GitHub] ignite pull request: IGNITE-2105 - Fixed nested collections in dir...

GitHub user vkulichenko opened a pull request: https://github.com/apache/ignite/pull/318 IGNITE-2105 - Fixed nested collections in direct marshalling You can merge this pull request into a Git repository by running: $ git pull https://github.com/vkulichenko/incubator-ignite

Re: Changes for ignite-jms11 and ignite-mtqq modules for fabric binary package

On Thu, Dec 10, 2015 at 9:54 AM, Sergey Kozlov wrote: > libs/optional/ignite-jms11/ > jms-api-1.1-rev-1.jar replaced by geronimo-jms_1.1_spec-1.1.1.jar > Correct. The same API but the latter is OSGi friendly. > libs/optional/ignite-mqtt/ > added guava-18.0.jar > In

Re: Accidental deserialization of BinaryObject key on a remote node

Yup. I got to the bottom of the issue, will push the fix soon.

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

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/301 --- 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

Re: Accidental deserialization of BinaryObject key on a remote node

Alex, can you please assign ticket to yourself? --Yakov 2015-12-10 1:48 GMT+03:00 Alexey Goncharuk : > Denis, > > I will take a look at this tomorrow. >

[GitHub] ignite pull request: Ignite 2064 4

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

Re: ignite-osgi-karaf on maven repository

It's a very valid question, indeed. A Karaf feature is simply a shortcut to install modules in the OSGi container, so I don't see a problem with the ignite-hibernate feature itself. We do not distribute Hibernate. However, where I do see a possible risk is with the ignite-all feature, which

Re: Introduction letter.

Welcome to the community, Vladimir! *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Thu, Dec 10, 2015 at 9:08 AM,

[GitHub] ignite pull request: IGNITE-2124 - Do not notify DS manager for us...

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/313 IGNITE-2124 - Do not notify DS manager for user caches, use correct simple names for queries You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-2065 portable -> binary renaming

Github user ashutakGG closed the pull request at: https://github.com/apache/ignite/pull/299 --- 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-2130) CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.

Igor Sapego created IGNITE-2130: --- Summary: CPP: Implement basic support of SQLForeignKeys API call for ODBC driver. Key: IGNITE-2130 URL: https://issues.apache.org/jira/browse/IGNITE-2130 Project:

Re: keepBinaryInStore

On Thu, Dec 10, 2015 at 6:26 PM, Alexey Kuznetsov wrote: > How about always pass value in binary format to store in case of > BinaryMarshaller? Why do we need deserialized object in store? This would not be backward compatible. Essentially, everyone switching to the

Re: keepBinaryInStore

How about always pass value in binary format to store in case of BinaryMarshaller? Why do we need deserialized object in store? -- Alexey Kuznetsov GridGain Systems www.gridgain.com

[GitHub] ignite pull request: IGNITE-2122 .NET: Add generic Read/WriteColle...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/316 IGNITE-2122 .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods. You can merge this pull request into a Git repository by running: $ git pull

Re: keepBinaryInStore

Alex, What should happen if user do this? Cache c1 = ...; c1.put(...); Cache c2 = c1.withKeepBinary(); c2.put(...); 10 дек. 2015 г. 17:02 пользователь "Alexey Goncharuk" < alexey.goncha...@gmail.com> написал: > Igniters, > > We introduced a cache configuration property keepBinaryInStore which

[GitHub] ignite pull request: Ignite-996 TestSuite

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

Re: keepBinaryInStore

If we do not want withKeepBinary() flag to affect the way objects are passed to a cache store, then I think current approach with a cache configuration flag is better than having a separate interface for store. With separate interfaces it is impossible to implement a 'universal' store which will

Re: keepBinaryInStore

On Thu, Dec 10, 2015 at 11:44 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > If we do not want withKeepBinary() flag to affect the way objects are > passed to a cache store, then I think current approach with a cache > configuration flag is better than having a separate interface for

Re: What is jdbc:ignite:cfg ??

I didn't think that we should force client mode at moment of implementation. But I can't provide any reason not to do it. So we need two small improvements to JDBC driver: 1. Always force client mode. 2. Use default configuration in cases when user did't specify any URL. This configuration

[GitHub] ignite pull request: IGNITE-2100 - Fixes for Externalizable classe...

Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/311 --- 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

Re: keepBinaryInStore

On Thu, Dec 10, 2015 at 10:24 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > > > > > > This would not be backward compatible. Essentially, everyone switching to > > the new version of Ignite would be required to rewrite their store > > implementation. I still think that introducing

Re: keepBinaryInStore

Huge +1 for Alexey's offer. When you did not know about this property, you will get an obscure exception on put operation [1] for the following code: IgniteCache cache = ignite.cache(null).withKeepBinary(); BinaryObject o =

Re: keepBinaryInStore

Alex, How user should put objects in cache in this case: 1) One node started with user classes in classpath. 2) Second node started WITHOUT user classes in classpath. 3) Cache configured with store. On first node user put objects in cache. Should user do puts via c1.withKeepBinary() ? in order

[jira] [Created] (IGNITE-2128) Incorrect output in CacheClientBinaryQueryExample

#20151210-sha1:d2008c53 [17:41:30] 2015 Copyright(C) Apache Software Foundation [17:41:30] [17:41:30] Ignite documentation: http://ignite.apache.org [17:41:30] [17:41:30] Quiet mode. [17:41:30] ^-- Logging to file '/Users/gridgain/Downloads/apache-ignite-fabric-1.5-2.0-b2-bin/work/log/ignite

[jira] [Created] (IGNITE-2129) .Net examples need to update xmldoc

Vasilisa Sidorova created IGNITE-2129: -- Summary: .Net examples need to update xmldoc Key: IGNITE-2129 URL: https://issues.apache.org/jira/browse/IGNITE-2129 Project: Ignite Issue Type: