Re: Question on serializibility constraint for key-values in Ignite JCache

Hi Val, I somehow missed the response, my bad. I'll take a look at it & get back in case I have follow up questions. Thanks, Subru On Mon, Aug 8, 2016 at 5:10 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Subru, > > There is a response from me in the thread: http://apache

Re: Question on serializibility constraint for key-values in Ignite JCache

Hi Subru, There is a response from me in the thread: http://apache-ignite-users.70518.x6.nabble.com/Question-on-serializibility-constraint-for-key-values-in-Ignite-JCache-td6434.html Please respond there if you have follow up questions. -Val On Mon, Aug 8, 2016 at 4:11 PM, Subru Krishnan wrote

Fwd: Question on serializibility constraint for key-values in Ignite JCache

Trying dev group as didn't get any response from the user group. Any pointers will be helpful. Thanks, Subru -- Forwarded message -- From: Subru Krishnan Date: Wed, Jul 20, 2016 at 6:30 PM Subject: Question on serializibility constraint for key-values in Ignite JCache To: u...@

Re: IGNITE-3263 Affinity function must check for null keys

Hi Saikat, Thanks for keep contributing! I’ve reviewed your changes and left comments in JIRA. — Denis > On Aug 7, 2016, at 2:11 AM, Saikat Maitra wrote: > > Hi, > > I have raised PR[1] for the following jira ticket[2]. > > Please review and let me know if any changes required. > > I have

Re: Contribution

Hi Alisher, Welcome to the community of Apache Ignite developers! You should get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here: https://cwiki.apache.org/confluenc

[jira] [Created] (IGNITE-3656) JdbcConnection.setTransactionIsolation should not throw an exception

Valentin Kulichenko created IGNITE-3656: --- Summary: JdbcConnection.setTransactionIsolation should not throw an exception Key: IGNITE-3656 URL: https://issues.apache.org/jira/browse/IGNITE-3656 Pr

Re: IGNITE-1192 Implementation (Integration with Spring Data)

Eduard, It's up to you :) I'm just saying that we should split the big task into smaller ones. -Val On Mon, Aug 8, 2016 at 3:57 AM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Hi, Valentin. > I am going to close these ticket with some prototype and create new ones > (maybe, with u

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

In my view, we should still handle automatic hashcode generation for all known types, boxed or unboxed. Most of the time, especially in INSERT statements, the hashcode will be a primitive type or String or Date, etc. We should automatically handle these types without any additional configuration.

[GitHub] ignite pull request #931: IGNITE-1192

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/931 IGNITE-1192 You can merge this pull request into a Git repository by running: $ git pull https://github.com/EdShangGG/ignite IGNITE-1192 Alternatively you can review and apply these changes

[GitHub] ignite pull request #930: Ignite 3272

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

[jira] [Created] (IGNITE-3655) Expose BinaryObjectBuilder in the cpp API

Valerio Aimale created IGNITE-3655: -- Summary: Expose BinaryObjectBuilder in the cpp API Key: IGNITE-3655 URL: https://issues.apache.org/jira/browse/IGNITE-3655 Project: Ignite Issue Type: Wi

[GitHub] ignite pull request #929: IGNITE-2545 : Allocate ArrayList for futures only ...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/929 IGNITE-2545 : Allocate ArrayList for futures only after second future… … is added You can merge this pull request into a Git repository by running: $ git pull https://github.com/AMashenk

[GitHub] ignite pull request #919: IGNITE-2310 Lock cache partition for affinityRun/a...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/919 --- 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 featu

[jira] [Created] (IGNITE-3654) SpringCache should optionally treat put with null as remove.

Vladimir Ozerov created IGNITE-3654: --- Summary: SpringCache should optionally treat put with null as remove. Key: IGNITE-3654 URL: https://issues.apache.org/jira/browse/IGNITE-3654 Project: Ignite

[GitHub] ignite pull request #928: IGNITE-3633 GridCacheUtils - validate hash code pr...

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/928 IGNITE-3633 GridCacheUtils - validate hash code presence in binary objs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-i

[jira] [Created] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

Nikolay Tikhonov created IGNITE-3653: Summary: P2P doesn't work for remote filter and filter factory. Key: IGNITE-3653 URL: https://issues.apache.org/jira/browse/IGNITE-3653 Project: Ignite

[GitHub] ignite pull request #860: Gridgain 7.5.29 p1

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

[GitHub] ignite pull request #859: Ignite 3414 tests

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

[GitHub] ignite pull request #845: Ignite 3405

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

[GitHub] ignite pull request #834: Ignite 3185

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

[GitHub] ignite pull request #818: Ignite 3184

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

[GitHub] ignite pull request #793: Ignite 2938

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

[GitHub] ignite pull request #787: Ignite 3285 -- merge to Ignite

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

[GitHub] ignite pull request #545: Hunk perf 1119 plus lock relax

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

[GitHub] ignite pull request #540: Hunk perf 1119

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

[GitHub] ignite pull request #401: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp do n...

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

[GitHub] ignite pull request #373: Ignite igfs kerberos

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

[GitHub] ignite pull request #363: Ignite tmp

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

[GitHub] ignite pull request #361: ignite-2218: deleted HadoopNativeCodeLoader

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

[GitHub] ignite pull request #360: 2206

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

[GitHub] ignite pull request #350: IG-2195: trial.

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

[GitHub] ignite pull request #277: Ignite 1926

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

[GitHub] ignite pull request #240: ignite-1639

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

[GitHub] ignite pull request #225: ignite-183: IgfsImpl and IgfsMetaManager use the s...

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

[GitHub] ignite pull request #198: IGNITE-1850.

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

[GitHub] ignite pull request #168: Ignite 1740

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

[GitHub] ignite pull request #168: Ignite 1740

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

[GitHub] ignite pull request #168: Ignite 1740

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

[GitHub] ignite pull request #157: ignite-825: disabled test remastered and restored.

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

[GitHub] ignite pull request #156: IGNITE-1487: exceptions on normal execution path a...

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

[GitHub] ignite pull request #141: Ignite 1590

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

[GitHub] ignite pull request #115: IGNITE-1573: mkdirs concurrency fixed.

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

Re: IGNITE-1192 Implementation (Integration with Spring Data)

Hi, Valentin. I am going to close these ticket with some prototype and create new ones (maybe, with umbrella one). Will it work? On Sat, Aug 6, 2016 at 8:03 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Eduard, > > This is too much information :) > > I think you should cre

[jira] [Created] (IGNITE-3652) IGFS: Local secondary: Review work directory support.

Vladimir Ozerov created IGNITE-3652: --- Summary: IGFS: Local secondary: Review work directory support. Key: IGNITE-3652 URL: https://issues.apache.org/jira/browse/IGNITE-3652 Project: Ignite

[jira] [Created] (IGNITE-3650) IGFS: Local secondary: Implement "info()" operation.

Vladimir Ozerov created IGNITE-3650: --- Summary: IGFS: Local secondary: Implement "info()" operation. Key: IGNITE-3650 URL: https://issues.apache.org/jira/browse/IGNITE-3650 Project: Ignite I

[jira] [Created] (IGNITE-3651) IGFS: Local secondary: Implement "usedSpaceSize()" operation.

Vladimir Ozerov created IGNITE-3651: --- Summary: IGFS: Local secondary: Implement "usedSpaceSize()" operation. Key: IGNITE-3651 URL: https://issues.apache.org/jira/browse/IGNITE-3651 Project: Ignite

[jira] [Created] (IGNITE-3649) IGFS: Local secondary: "create" flag is not used for append() operation.

Vladimir Ozerov created IGNITE-3649: --- Summary: IGFS: Local secondary: "create" flag is not used for append() operation. Key: IGNITE-3649 URL: https://issues.apache.org/jira/browse/IGNITE-3649 Projec

[jira] [Created] (IGNITE-3647) IGFS: Local secondary: Implement listPaths() and listFiles() operations.

Vladimir Ozerov created IGNITE-3647: --- Summary: IGFS: Local secondary: Implement listPaths() and listFiles() operations. Key: IGNITE-3647 URL: https://issues.apache.org/jira/browse/IGNITE-3647 Projec

[jira] [Created] (IGNITE-3648) IGFS: Local secondary: "properties" is not used for create() operation.

Vladimir Ozerov created IGNITE-3648: --- Summary: IGFS: Local secondary: "properties" is not used for create() operation. Key: IGNITE-3648 URL: https://issues.apache.org/jira/browse/IGNITE-3648 Project

[GitHub] ignite pull request #105: Ignite 1515 b

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

[GitHub] ignite pull request #101: IGNITE-586: version for "master" branch

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

[jira] [Created] (IGNITE-3646) IGFS: Local secondary: support symlinks for mkdirs operation.

Vladimir Ozerov created IGNITE-3646: --- Summary: IGFS: Local secondary: support symlinks for mkdirs operation. Key: IGNITE-3646 URL: https://issues.apache.org/jira/browse/IGNITE-3646 Project: Ignite

[jira] [Created] (IGNITE-3645) IGFS: Local secondary: Implement update() operation.

Vladimir Ozerov created IGNITE-3645: --- Summary: IGFS: Local secondary: Implement update() operation. Key: IGNITE-3645 URL: https://issues.apache.org/jira/browse/IGNITE-3645 Project: Ignite I

[GitHub] ignite pull request #98: Ignite 586

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/98 --- 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-3644) IGFS: Local secondary: Implement exists() operation.

Vladimir Ozerov created IGNITE-3644: --- Summary: IGFS: Local secondary: Implement exists() operation. Key: IGNITE-3644 URL: https://issues.apache.org/jira/browse/IGNITE-3644 Project: Ignite I

[GitHub] ignite pull request #93: IG-1376: fixed.

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/93 --- 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 #92: ignite-1477: more detailed error messages.

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/92 --- 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-3643) IGFS: Local secondary: Define proper default buffer size.

Vladimir Ozerov created IGNITE-3643: --- Summary: IGFS: Local secondary: Define proper default buffer size. Key: IGNITE-3643 URL: https://issues.apache.org/jira/browse/IGNITE-3643 Project: Ignite

[GitHub] ignite pull request #880: Ignite 3513

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

[GitHub] ignite pull request #91: Ignite 1392

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/91 --- 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-3642) IGFS: Local secondary: support symlink deletion.

Vladimir Ozerov created IGNITE-3642: --- Summary: IGFS: Local secondary: support symlink deletion. Key: IGNITE-3642 URL: https://issues.apache.org/jira/browse/IGNITE-3642 Project: Ignite Issue

[GitHub] ignite pull request #89: ignite-1465: provided more detailed error massage i...

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/89 --- 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-3641) IGFS: Local secondary: Support properties for mkdirs.

Vladimir Ozerov created IGNITE-3641: --- Summary: IGFS: Local secondary: Support properties for mkdirs. Key: IGNITE-3641 URL: https://issues.apache.org/jira/browse/IGNITE-3641 Project: Ignite

[GitHub] ignite pull request #47: Ignite 1298 flush

Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/47 --- 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-3640) IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation.

Vladimir Ozerov created IGNITE-3640: --- Summary: IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation. Key: IGNITE-3640 URL: https://issues.apache.org/jira/browse/IGNITE-3640

[jira] [Created] (IGNITE-3639) IGFS: Local secondary: investigate whether we need BufferedOutputStream for create/append.

Vladimir Ozerov created IGNITE-3639: --- Summary: IGFS: Local secondary: investigate whether we need BufferedOutputStream for create/append. Key: IGNITE-3639 URL: https://issues.apache.org/jira/browse/IGNITE-3639

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

I like what Vladimir proposed. As for `encoded string` implementation, I guess it should be just an implementation with a list of fields which have to participate in hashCode and equals. I guess in 99% of cases everyone generates hashCode and equals with IDE, we will just implement the same logic

[jira] [Created] (IGNITE-3638) Implement rename at the LocalIgfsSecondaryFileSystem

Taras Ledkov created IGNITE-3638: Summary: Implement rename at the LocalIgfsSecondaryFileSystem Key: IGNITE-3638 URL: https://issues.apache.org/jira/browse/IGNITE-3638 Project: Ignite Issue T

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

I like the idea with string-based BinaryEqualsHashCodeResolver a lot. I think it should be as flexible as possible. Since EqualsHashCode resolver becomes a part of cache configuration, we get another part of configuration which must be deployed on server nodes and defeats benefits of BinaryMarshall

Contribution

Hi! My name is Alisher! I’m a java engineer and have experience of analytics, recommendation systems, distributed processing I would like to contribute to the project With best regards Alisher Alimov signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [RESULT] [VOTE] Apache Ignite 1.7.0 Release (RC1)

Hi The maven staging repository released. On Mon, Aug 8, 2016 at 4:33 AM, Andrey Novikov wrote: > Can’t find maven artifacts for 1.7.0 > > http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.ignite%22 > > > On Sat, Aug 6, 201

Re: All BinaryObjects created by BinaryObjectBuilder stored at the same partition by default

Dmitriy, >>> Every time an object is used as a key in a cache, we automatically generate hashcode for it. The first time we do it, we print out a warning in the log, that the hashcodes will be automatically generated, if not provided. We will receive billion questions like "why did I put object to