[GitHub] ignite pull request #916: Ignite 3332

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

Distributed Joins Documentation

Igniters, As most of you know recently we have released Ignite 1.7.0 that has the distributed joins functionality. I’ve added the documentation and blogged about this feature https://apacheignite.readme.io/docs/sql-queries#distributed-joins

Re: Multi-cache transactions & persistent store

By the way Yakov. How should we handle multi-cache transactions for "write-behind" caches? For different caches (participated in transaction) we can receive several separate sessionEnd calls. Igor On Mon, Aug 1, 2016 at 1:32 AM, Yakov Zhdanov wrote: > Igor, you factory

[GitHub] ignite pull request #944: IGNITE-3668 IGFS: Local secondary: Review all "thr...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/944 IGNITE-3668 IGFS: Local secondary: Review all "throw new IOException"… … places. You can merge this pull request into a Git repository by running: $ git pull

Re: Release notes preparations...

Great! Thanks for updating the page! I've noticed that we are still using unsecure md5 and sha1, but i guess this is a topic for a different time ;) Cheers, Cos On Wed, Aug 10, 2016 at 12:26PM, Pavel Tupitsyn wrote: > Cos, you are right. > > More than 300 (!) tickets has been moved to 1.8

[GitHub] ignite pull request #930: Ignite 3272

Github user ntikhonov closed the pull request at: https://github.com/apache/ignite/pull/930 --- 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: IGNITE-3407 HTTP REST: query commands without pageSize failed with NPE

Thank you Andrey!!! I will update the PR accordingly. Regards Saikat On Wed, Aug 10, 2016 at 12:42 AM, Andrey Gura wrote: > Hi, > > I’ve reviewed your changes. Please, see my comments in JIRA. > > Thank you for contribution! > > > > On Sun, Aug 7, 2016 at 12:06 PM, Saikat

[jira] [Created] (IGNITE-3671) Ignite profiling interface

Alexey Goncharuk created IGNITE-3671: Summary: Ignite profiling interface Key: IGNITE-3671 URL: https://issues.apache.org/jira/browse/IGNITE-3671 Project: Ignite Issue Type: Wish

[GitHub] ignite pull request #942: Ignite 1.6.6

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

[jira] [Created] (IGNITE-3670) IGFS: Local secondary: Add test for listPath() method called for symlink to directory

Taras Ledkov created IGNITE-3670: Summary: IGFS: Local secondary: Add test for listPath() method called for symlink to directory Key: IGNITE-3670 URL: https://issues.apache.org/jira/browse/IGNITE-3670

[jira] [Created] (IGNITE-3669) Web console: Implement tests for validation feedback fields

Dmitriyff created IGNITE-3669: - Summary: Web console: Implement tests for validation feedback fields Key: IGNITE-3669 URL: https://issues.apache.org/jira/browse/IGNITE-3669 Project: Ignite

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/929 --- 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 #941: IGNITE-3618 - Client can not load data after serve...

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/941 IGNITE-3618 - Client can not load data after server restarts You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3618

Re: Release notes preparations...

Cos, you are right. More than 300 (!) tickets has been moved to 1.8 yesterday when I released 1.7 version in JIRA. For what it's worth, I've added a step to vote verification: https://cwiki.apache.org/confluence/display/IGNITE/Release+Process Pavel On Tue, Aug 9, 2016 at 9:37 PM, Konstantin

[jira] [Created] (IGNITE-3668) IGFS: Local secondary: Review all "throw new IOException" places.

Vladimir Ozerov created IGNITE-3668: --- Summary: IGFS: Local secondary: Review all "throw new IOException" places. Key: IGNITE-3668 URL: https://issues.apache.org/jira/browse/IGNITE-3668 Project:

[jira] [Created] (IGNITE-3667) IGFS: Local secondary: Ensure that user context is propagated properly to underlying FS operation.

Vladimir Ozerov created IGNITE-3667: --- Summary: IGFS: Local secondary: Ensure that user context is propagated properly to underlying FS operation. Key: IGNITE-3667 URL:

IGNITE-3138 IgniteDataStreamer: failures are not shown on the streaming side

IGNITE-3138 Patch available Please review and let me know if any changes required.

[jira] [Created] (IGNITE-3666) Print out an information message if LGPL module is in classpath

Sergey Kozlov created IGNITE-3666: - Summary: Print out an information message if LGPL module is in classpath Key: IGNITE-3666 URL: https://issues.apache.org/jira/browse/IGNITE-3666 Project: Ignite

Re: .Net's QueryExample mixes everything in a single cache

Yes, it is a good idea, because I think in 2.0 we will disallow having more than a single type in a cache. Sergi 2016-08-10 9:35 GMT+03:00 Vladimir Ozerov : > I do not know the reason. Let's split. > > On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn

Re: .Net's QueryExample mixes everything in a single cache

I do not know the reason. Let's split. On Wed, Aug 10, 2016 at 9:05 AM, Pavel Tupitsyn wrote: > Hi Denis, > > It has always been this way, not sure why. Vladimir can probably clarify. > I agree that this is an anti-pattern, feel free to create a ticket. > > Pavel. > > On

Re: .Net's QueryExample mixes everything in a single cache

Hi Denis, It has always been this way, not sure why. Vladimir can probably clarify. I agree that this is an anti-pattern, feel free to create a ticket. Pavel. On Wed, Aug 10, 2016 at 7:34 AM, Dmitriy Setrakyan wrote: > Denis, good catch! I would also prefer to split