Re: POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null

Cross-sending to user@ as well. On Tue, Sep 5, 2017 at 10:44 PM, kotamrajuyashasvi < kotamrajuyasha...@gmail.com> wrote: > Hi > > I'm using ignite with cassandra as persistent store. I have a POJO class > mapped to cassandra table. I have used > ignite-cassandra-store/KeyValuePersistenceSettings

POJO field having wrapper type, mapped to cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null

Hi I'm using ignite with cassandra as persistent store. I have a POJO class mapped to cassandra table. I have used ignite-cassandra-store/KeyValuePersistenceSettings xml bean to map POJO to cassandra table. In the POJO one of the fields is Integer (wrapper class) mapped to int column in

Re: How to configure ignite-jcl and Ignite-slf4j logger

Just sending it for your reference - Copied ignite-log* library in ignite lib folder Renamed ignite-log4j to log4j.xml for log4j configuration Renamed ignite-log4j2 to log4j2.xml for log4j configuration Copied respective log file config in config location so that it can be picked up during start

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Vova, I agree. Let's stay loyal to our binary serialization protocol. Do you know if we will be loosing any functionality available in Externalizable, but not present in our binary protocol? D. On Mon, Sep 4, 2017 at 11:38 PM, Vladimir Ozerov wrote: > Folks, > > Let's

Re: IGNITE-5655: Mixing binary string encodings in Ignite cluster

Can we just detect the encoding at cache, or at least column level? This way if the encoding does not match, we throw an exception immediately. Will it work? D. On Tue, Sep 5, 2017 at 9:16 AM, Andrey Kuznetsov wrote: > Hi Igniters! > > I met a couple of issues related to

Re: How to configure ignite-jcl and Ignite-slf4j logger

Prachi, Parameter of Log4JLogger constructor is not the path to XML file, it's just a name of root logger. Ignite logger configuration should look like this: ignite-log4j.xml file should be renamed to log4j.xml and moved

[GitHub] ignite pull request #2596: IGNITE-6179: fixed tests with client reconnect

GitHub user vk23 opened a pull request: https://github.com/apache/ignite/pull/2596 IGNITE-6179: fixed tests with client reconnect Affects: DynamicIndexPartitionedAtomicConcurrentSelfTest.testClientReconnectWithCacheRestart()

RE: Specifying location of persistent storage location

Hi Yakov, Yes, Dmitriy walked me through how setting the LocalHost results in the folder name for the persistent data to be fixed. I also fixed the port number as this is also an aspect of the folder name. Is there a known issue with IPv6 interfaces on a server hosting Ignite? Thanks,

RE: Specifying location of persistent storage location

Hi Pavel, Thanks for the pointer on how to have both the XML and .Net client configuration supplied to Ignite. Raymond. *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Tuesday, September 5, 2017 8:56 PM *To:* dev@ignite.apache.org *Cc:* u...@ignite.apache.org; Dmitriy

[GitHub] ignite pull request #2595: IGNITE-1.8.11 release

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2595 IGNITE-1.8.11 release Created for testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.11

IGNITE-5655: Mixing binary string encodings in Ignite cluster

Hi Igniters! I met a couple of issues related to different binary string encoding settings on different cluster nodes. Let cluster has two nodes. Node0 uses win-1251 to marshal strings with BinaryMarshaller and Node1 uses default utf-8 encoding. Let's create replicated cache and add some entry

[GitHub] ignite pull request #2455: IGNITE-5879 .NET: Move TestPlatformPlugin to a se...

Github user daradurvs closed the pull request at: https://github.com/apache/ignite/pull/2455 ---

[GitHub] ignite pull request #2594: IGNITE-5145 Support multiple service deployment i...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/2594 IGNITE-5145 Support multiple service deployment in API Created for testing You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2450: IGNITE-5145 add batch service deployment methods

Github user dmekhanikov closed the pull request at: https://github.com/apache/ignite/pull/2450 ---

[GitHub] ignite pull request #2561: ignite-6214 resolve problem with concurrent metad...

Github user dmekhanikov closed the pull request at: https://github.com/apache/ignite/pull/2561 ---

[GitHub] ignite pull request #2571: IGNITE-6214 resolve problem with concurrent metad...

GitHub user dmekhanikov reopened a pull request: https://github.com/apache/ignite/pull/2571 IGNITE-6214 resolve problem with concurrent metadata updates Created for testing You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #2571: IGNITE-6214 resolve problem with concurrent metad...

Github user dmekhanikov closed the pull request at: https://github.com/apache/ignite/pull/2571 ---

[GitHub] ignite pull request #2131: IGNITE-5344 JDBC thin driver: support Statement.c...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2131 ---

[jira] [Created] (IGNITE-6274) Cluster activation may hang because of OutOfMemoryError.

Vyacheslav Koptilin created IGNITE-6274: --- Summary: Cluster activation may hang because of OutOfMemoryError. Key: IGNITE-6274 URL: https://issues.apache.org/jira/browse/IGNITE-6274 Project:

[jira] [Created] (IGNITE-6273) Move ServiceDeploymentException to org.apache.ignite.services package

Denis Mekhanikov created IGNITE-6273: Summary: Move ServiceDeploymentException to org.apache.ignite.services package Key: IGNITE-6273 URL: https://issues.apache.org/jira/browse/IGNITE-6273

Re: [DISCUSSION] Urgent Ignite bug fix release

Igor, That's an important fix. Please merge it to ignite-2.2. Don't forget to change fix version. On Tue, Sep 5, 2017 at 3:42 PM, Igor Sapego wrote: > Igniters, > > There is one more fix I would propose to include into 2.2: [1]. It has > been fixed a while ago and it is

[jira] [Created] (IGNITE-6271) Fix ServicesTest in .NET part

Denis Mekhanikov created IGNITE-6271: Summary: Fix ServicesTest in .NET part Key: IGNITE-6271 URL: https://issues.apache.org/jira/browse/IGNITE-6271 Project: Ignite Issue Type: Test

Re: ContinuousQueryWithTransformer implementation questions - 2

Hello, Nikolay. I think we can't use this method: We need to set: * transformer * *local listener* - differs from regular ContinuousQuery listener * other continuous query params. So at least we have to add local listener param. If we use ContinuousQuery instance as first param to get all

[GitHub] ignite pull request #2593: Ignite-gg-12699

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/2593 Ignite-gg-12699 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12699 Alternatively you

Re: [DISCUSSION] Urgent Ignite bug fix release

Igniters, There is one more fix I would propose to include into 2.2: [1]. It has been fixed a while ago and it is critical for C++ users that would like to make use of persistence store, as currently they need to have separate Java node just to activate cluster. What do you think? [1] -

[jira] [Created] (IGNITE-6270) Rename user facing CREATE TABLE param names to split words properly

Alexander Paschenko created IGNITE-6270: --- Summary: Rename user facing CREATE TABLE param names to split words properly Key: IGNITE-6270 URL: https://issues.apache.org/jira/browse/IGNITE-6270

[jira] [Created] (IGNITE-6269) Document CREATE TABLE param for cache write sync mode on readme.io

Alexander Paschenko created IGNITE-6269: --- Summary: Document CREATE TABLE param for cache write sync mode on readme.io Key: IGNITE-6269 URL: https://issues.apache.org/jira/browse/IGNITE-6269

[jira] [Created] (IGNITE-6268) Add documentation for SQL CRUD operations with nested BinaryObject fields

Alexandr Fedotov created IGNITE-6268: Summary: Add documentation for SQL CRUD operations with nested BinaryObject fields Key: IGNITE-6268 URL: https://issues.apache.org/jira/browse/IGNITE-6268

[jira] [Created] (IGNITE-6267) .NET: Get rid of Doxygen-specific files

Pavel Tupitsyn created IGNITE-6267: -- Summary: .NET: Get rid of Doxygen-specific files Key: IGNITE-6267 URL: https://issues.apache.org/jira/browse/IGNITE-6267 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-6266) Nested BinaryObject fields cannot be inserted via SQL

Alexandr Fedotov created IGNITE-6266: Summary: Nested BinaryObject fields cannot be inserted via SQL Key: IGNITE-6266 URL: https://issues.apache.org/jira/browse/IGNITE-6266 Project: Ignite

Re: Thin client and binary metadata

Ok, I think we all agree on that. Client implementors can decide whether they call metadata API or not. Now onto the API itself: I've outlined the proposal in JIRA [1]. Let me know your thoughts. [1] https://issues.apache.org/jira/browse/IGNITE-6258 On Mon, Sep 4, 2017 at 5:06 PM, Dmitriy

Re: DataStreamer usability

Here is another little example of non-obvious DataStreamer-related API: https://stackoverflow.com/questions/46045987/unknown-pair-exception-when-using-streamtransformer-for-binaryobject/46051447?noredirect=1#comment79063618_46051447 I think, passing new value as the first element of Object array

[jira] [Created] (IGNITE-6265) BinaryObject fields nested deeper than one level cannot be updated via SQL

Alexandr Fedotov created IGNITE-6265: Summary: BinaryObject fields nested deeper than one level cannot be updated via SQL Key: IGNITE-6265 URL: https://issues.apache.org/jira/browse/IGNITE-6265

Re: Specifying location of persistent storage location

Raymond, I think most of Ignite users run on ipv4. So, issues with v6 in this case are hardly possible =) --Yakov

[jira] [Created] (IGNITE-6264) .NET: Verify Java API parity with a unit test

Pavel Tupitsyn created IGNITE-6264: -- Summary: .NET: Verify Java API parity with a unit test Key: IGNITE-6264 URL: https://issues.apache.org/jira/browse/IGNITE-6264 Project: Ignite Issue

[jira] [Created] (IGNITE-6263) .NET: Verify Java config parity with a unit test

Pavel Tupitsyn created IGNITE-6263: -- Summary: .NET: Verify Java config parity with a unit test Key: IGNITE-6263 URL: https://issues.apache.org/jira/browse/IGNITE-6263 Project: Ignite Issue

Re: New API docs look for Ignite.NET

Great news, thanks a lot! On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn wrote: > DocFX takes around 30 seconds on my machine. > > > if you already tried that > Yes, everything is done on my side, see JIRA ticket [4] and preview [5] > above. > > On Tue, Sep 5, 2017 at

Re: Specifying location of persistent storage location

Ignite.NET does not have IgniteConfiguration.ConsistentId, here is the ticket: https://issues.apache.org/jira/browse/IGNITE-6249 Workaround is to use Spring XML for that particular property (keep everything else in .NET, configs will be merged):

Re: Specifying location of persistent storage location

+ dev Pavel Tupitsin, can you please check that org.apache.ignite.configuration.IgniteConfiguration#setConsistentId has it platform counterpart? I could not find it. Raymond, you can explicitly set a bind address for Ignite with public string Localhost { get; set; }. This will make consistent ID

Re: New API docs look for Ignite.NET

DocFX takes around 30 seconds on my machine. > if you already tried that Yes, everything is done on my side, see JIRA ticket [4] and preview [5] above. On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov wrote: > Pavel, thanks! > It is the great news! > Looks like DocFX will

Re: New API docs look for Ignite.NET

Pavel, thanks! It is the great news! Looks like DocFX will save 30-40 min. 2017-09-05 11:16 GMT+03:00 Pavel Tupitsyn : > Igniters and users, > > Historically we've been using Doxygen [1] to generate .NET API > documentation [2]. > > Recently it became very slow on our code

Re: New API docs look for Ignite.NET

Pavel I like the idea to change Doxygen. It really becomes uncomfortable to regenerate often. Do you know how much DocFX faster than Doxygen (if you already tried that)? On Tue, Sep 5, 2017 at 11:16 AM, Pavel Tupitsyn wrote: > Igniters and users, > > Historically we've

New API docs look for Ignite.NET

Igniters and users, Historically we've been using Doxygen [1] to generate .NET API documentation [2]. Recently it became very slow on our code base (more than 30 minutes to generate), and I could not find any solution or tweak to fix that. Other issues include outdated looks and limited

[GitHub] ignite pull request #2589: IGNITE-6255 .NET: Fix TestAffinityCall to take la...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2589 ---

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

Folks, Let's discuss how this should be handled properly. I proposed to use the same format as regular binary object, with all data being written in "raw" form. This would give us one critical advantage - we will be able to work with such objects without deserialization on the server. Hence, no

Re: How to configure ignite-jcl and Ignite-slf4j logger

Valentin, Nikolai, I have published my example on github - https://github.com/pgarg/myIgniteExamples On Mon, Sep 4, 2017 at 7:57 PM, Rishi Yagnik wrote: > I have configured log4j, log4j-2 in our environment, can share additional > details here if you need it. > > On Mon,