[GitHub] ignite pull request #932: Ignite 1.7.2

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

[jira] [Created] (IGNITE-3657) Add formatter for UUID fields

Pavel Konstantinov created IGNITE-3657: -- Summary: Add formatter for UUID fields Key: IGNITE-3657 URL: https://issues.apache.org/jira/browse/IGNITE-3657 Project: Ignite Issue Type: Sub-ta

[GitHub] ignite pull request #933: Ignite-2968-1

GitHub user agura opened a pull request: https://github.com/apache/ignite/pull/933 Ignite-2968-1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/agura/incubator-ignite ignite-2968-1 Alternatively you can review and apply these c

[GitHub] ignite pull request #913: IGNITE-3138 - IgniteDataStreamer: failures are not...

Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/913 --- 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-3658) Move all failing and flaky tests to separate test suite.

Vladimir Ozerov created IGNITE-3658: --- Summary: Move all failing and flaky tests to separate test suite. Key: IGNITE-3658 URL: https://issues.apache.org/jira/browse/IGNITE-3658 Project: Ignite

[GitHub] ignite pull request #934: IGNITE-3138 - IgniteDataStreamer: failures are not...

GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/934 IGNITE-3138 - IgniteDataStreamer: failures are not shown on the strea… …ming side You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatk

[GitHub] ignite pull request #935: IGNITE-3644 IGFS: Local secondary: Implement exist...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/935 IGNITE-3644 IGFS: Local secondary: Implement exists() operation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-3659) Implement tests suites with special handling of ignored tests.

Vladimir Ozerov created IGNITE-3659: --- Summary: Implement tests suites with special handling of ignored tests. Key: IGNITE-3659 URL: https://issues.apache.org/jira/browse/IGNITE-3659 Project: Ignite

[GitHub] ignite pull request #936: Ignite 1.6.5

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

[jira] [Created] (IGNITE-3660) Add "Ignored" suite to TC.

Vladimir Ozerov created IGNITE-3660: --- Summary: Add "Ignored" suite to TC. Key: IGNITE-3660 URL: https://issues.apache.org/jira/browse/IGNITE-3660 Project: Ignite Issue Type: Sub-task

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

Guys, I have made a pull request. https://github.com/apache/ignite/pull/931 New module spring-data was added. The example of repository: @RepositoryConfig(cacheName = "cache") public interface FirstRepository extends IgniteRepository { /*

[GitHub] ignite pull request #937: IGNITE-3647 IGFS: Local secondary: Implement listP...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/937 IGNITE-3647 IGFS: Local secondary: Implement listPaths() and listFiles() operations. …s() operations. You can merge this pull request into a Git repository by running: $ git pull ht

[jira] [Created] (IGNITE-3661) Process failing web sessions tests.

Vladimir Ozerov created IGNITE-3661: --- Summary: Process failing web sessions tests. Key: IGNITE-3661 URL: https://issues.apache.org/jira/browse/IGNITE-3661 Project: Ignite Issue Type: Sub-ta

[GitHub] ignite pull request #938: IGNITE-3649 IGFS: Local secondary: "create" flag i...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/938 IGNITE-3649 IGFS: Local secondary: "create" flag is not used for appe… …nd() operation. You can merge this pull request into a Git repository by running: $ git pull https://github.

[jira] [Created] (IGNITE-3662) Improving Integration with Spring Data

Eduard Shangareev created IGNITE-3662: - Summary: Improving Integration with Spring Data Key: IGNITE-3662 URL: https://issues.apache.org/jira/browse/IGNITE-3662 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-3663) Failed test: Sporadic failures to WebSessionSelfTest.testSessionRenewalDuringLogin()

Vladimir Ozerov created IGNITE-3663: --- Summary: Failed test: Sporadic failures to WebSessionSelfTest.testSessionRenewalDuringLogin() Key: IGNITE-3663 URL: https://issues.apache.org/jira/browse/IGNITE-3663

[jira] [Created] (IGNITE-3664) IGFS: Local secondary: Support blockSize attribute

Taras Ledkov created IGNITE-3664: Summary: IGFS: Local secondary: Support blockSize attribute Key: IGNITE-3664 URL: https://issues.apache.org/jira/browse/IGNITE-3664 Project: Ignite Issue Typ

[GitHub] ignite pull request #939: IGNITE-3650 IGFS: Local secondary: Implement "info...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/939 IGNITE-3650 IGFS: Local secondary: Implement "info()" operation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #940: Ignite 2079

GitHub user AndreyVel opened a pull request: https://github.com/apache/ignite/pull/940 Ignite 2079 Please, make review changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/AndreyVel/ignite ignite-2079 Alternatively you can rev

Release notes preparations...

Gents, this has triggered the recollection of the release notes conversation we had the other day. Looks like the ticket queue isn't getting pruned in time of the release, so the changes like that are happening postfactum. This is either leads to more load on the RM, or might be error-prone. I w

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

Thank you Denis. I will update the PR accordingly. Regards Saikat On Tue, Aug 9, 2016 at 3:39 AM, Denis Magda wrote: > 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: > >

Re: IGNITE-3407 HTTP REST: query commands without pageSize failed with NPE

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 Maitra wrote: > Hi, > > I have raised PR[1] for the following jira ticket[2]. > > Please review and let me know if any changes required. > > Regards, > Saikat

Interested in Apache Ignite Contributions

Hello list! I am Patrick Peralta, a developer at Workday. We are in the process of adopting Ignite and we are interested in joining the community and offering contributions to the project! We would like to start by expanding the test coverage to include test cases that (force) kill JVMs and as

Re: Interested in Apache Ignite Contributions

Hi Patrick, Thanks for showing interest in making Apache Ignite better! I do believe that the skills you have let you dive in and get to know Ignite much faster. I’ve added you to the contributors list in JIRA. So for now you can assign a ticket you want to take over on yourself. > We would li

[jira] [Created] (IGNITE-3665) Update KafkaStreamer dependencies

Roman Shtykh created IGNITE-3665: Summary: Update KafkaStreamer dependencies Key: IGNITE-3665 URL: https://issues.apache.org/jira/browse/IGNITE-3665 Project: Ignite Issue Type: Improvement

.Net's QueryExample mixes everything in a single cache

Pavel, I found out today that our .Net’s QueryExample mixes data for both Employee and Organization entities in a single cache. Is there any significant reasons for that? Basically I would prefer demonstrating how data can be logically divided among different caches and that cross-cache queri

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

Denis, good catch! I would also prefer to split Orgs and Employees into different caches, as putting them into the same cache is rather an anti-pattern. On Tue, Aug 9, 2016 at 6:28 PM, Denis Magda wrote: > Pavel, > > I found out today that our .Net’s QueryExample mixes data for both > Employee a

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

Crossposting to dev list. Igniters, Is there anyone who can create image for the recently released 1.7? -Val On Sat, Aug 6, 2016 at 2:18 PM, zshamrock wrote: > Why there is no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub > https://hub.docker.com/r/apacheignite/ignite/tags/? > >

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

Nick, As far as I remember you were preparing the image for the earlier release. Can you do the same for both 1.6.0 and 1.7.0? Do we have any documentation so that any from the community can perform this task at the end of release process? — Denis > On Aug 9, 2016, at 9:39 PM, Valentin Kuliche

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 Orgs and Employees into > d

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 Wed, Aug 10, 2016 at 7:3

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 > wrote: > > > Hi Denis, > > > > It has alway

[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

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.