Re: Apache Ignite - New Release

On Fri, Jul 22, 2016 at 7:10 AM, Semyon Boikov wrote: > Hi, > > Today I merged into master 'distributed join' implementation - > https://issues.apache.org/jira/browse/IGNITE-1232 (thanks to Sergi, he > implemented this feature). I think this together with recent bugfixes

[jira] [Created] (IGNITE-3559) CPP: Review Ignite C++ API and provide list of breaking improvements that can be included in Ignite 2.0

Igor Sapego created IGNITE-3559: --- Summary: CPP: Review Ignite C++ API and provide list of breaking improvements that can be included in Ignite 2.0 Key: IGNITE-3559 URL:

[GitHub] ignite pull request #885: ignite-3476

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

Re: Apache Ignite - New Release

Hi, Today I merged into master 'distributed join' implementation - https://issues.apache.org/jira/browse/IGNITE-1232 (thanks to Sergi, he implemented this feature). I think this together with recent bugfixes worth 1.7 release. Do you think we can cut off 1.7 release branch from master? Thanks

[GitHub] ignite pull request #879: IGNITE-3512 .NET: IBinaryObject.ToBuilder loses ty...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/879 --- 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: Breaking improvements for the Ignite C++.

Dmitriy, I've checked Java implementation of the BinaryType and it seems to be something a bit different than in C++. Current role of the BinaryType in C++ is to provide Ignite with the information about its template type, to be used during serialization and deserialization. Unlike Java version,

Breaking improvements for the Ignite C++.

Hello Igniters and Ignite users, As there is going to be Ignite 2.0 release soon, It is a good opportunity for us to improve Ignite C++ API without the need to maintain backward compatibility. Let's collect and discuss all the proposal for the changes in API here. If you've had any proposal on

Re: Breaking improvements for the Ignite C++.

I am not a C++ expert, but can you please explain why you would like to change all methods on the BinaryType to static? Is it the same way in Java? On Fri, Jul 22, 2016 at 9:00 AM, Igor Sapego wrote: > Hello Igniters and Ignite users, > > As there is going to be Ignite 2.0

Enums and SQL queries

Folks, I noticed that we currently have a very weird limitation for enum fields when running SQL queries. Basically, you can't use enum value names as many users would expect. Technically this happens because binary format stores only ordinal and the only way to run such query is to do something

[GitHub] ignite pull request #886: Ignite 2294 SQL DML

GitHub user alexpaschenko opened a pull request: https://github.com/apache/ignite/pull/886 Ignite 2294 SQL DML You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2294 Alternatively you can review and

Re: Enums and SQL queries

I'm not sure what exactly you are going to patch in SQL engine. We could and some SQL function like enum('MY_ENUM_NAME') but probably it will not work if we will not pass enum type there as well, so it have look like enum('com.mycompany.MyEnum', 'MY_ENUM_NAME') which is ugly. Sergi On 23 июля

[GitHub] ignite pull request #887: IGNITE-2344 WebSessionFilter doesn't support sessi...

GitHub user samaitra opened a pull request: https://github.com/apache/ignite/pull/887 IGNITE-2344 WebSessionFilter doesn't support session ID renewal You can merge this pull request into a Git repository by running: $ git pull https://github.com/samaitra/ignite IGNITE-2344

[jira] [Created] (IGNITE-3537) Add tests checking that data structures work inside user transactions

Semen Boikov created IGNITE-3537: Summary: Add tests checking that data structures work inside user transactions Key: IGNITE-3537 URL: https://issues.apache.org/jira/browse/IGNITE-3537 Project:

[jira] [Created] (IGNITE-3540) .NET: Review access modifiers

Pavel Tupitsyn created IGNITE-3540: -- Summary: .NET: Review access modifiers Key: IGNITE-3540 URL: https://issues.apache.org/jira/browse/IGNITE-3540 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #882: Ignite 7.6.3

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

[jira] [Created] (IGNITE-3538) Implement remove failover for cache collections

Semen Boikov created IGNITE-3538: Summary: Implement remove failover for cache collections Key: IGNITE-3538 URL: https://issues.apache.org/jira/browse/IGNITE-3538 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-3539) .NET: Remove deprecated code

Pavel Tupitsyn created IGNITE-3539: -- Summary: .NET: Remove deprecated code Key: IGNITE-3539 URL: https://issues.apache.org/jira/browse/IGNITE-3539 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-3548) .NET: Rename ILifecycleBean

Pavel Tupitsyn created IGNITE-3548: -- Summary: .NET: Rename ILifecycleBean Key: IGNITE-3548 URL: https://issues.apache.org/jira/browse/IGNITE-3548 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-3549) IGFS: Switch his

Vladimir Ozerov created IGNITE-3549: --- Summary: IGFS: Switch his Key: IGNITE-3549 URL: https://issues.apache.org/jira/browse/IGNITE-3549 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #875: IGNITE-3515

Github user kromulan closed the pull request at: https://github.com/apache/ignite/pull/875 --- 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-3551) Hadoop: Improve usability for Apache Ignite 2.0

Vladimir Ozerov created IGNITE-3551: --- Summary: Hadoop: Improve usability for Apache Ignite 2.0 Key: IGNITE-3551 URL: https://issues.apache.org/jira/browse/IGNITE-3551 Project: Ignite Issue

[jira] [Created] (IGNITE-3552) IGFS: Performance improvements.

Vladimir Ozerov created IGNITE-3552: --- Summary: IGFS: Performance improvements. Key: IGNITE-3552 URL: https://issues.apache.org/jira/browse/IGNITE-3552 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3553) Implement internal light-weight closure execution.

Vladimir Ozerov created IGNITE-3553: --- Summary: Implement internal light-weight closure execution. Key: IGNITE-3553 URL: https://issues.apache.org/jira/browse/IGNITE-3553 Project: Ignite

[jira] [Created] (IGNITE-3554) IGFS: Support cross-mode operations.

Vladimir Ozerov created IGNITE-3554: --- Summary: IGFS: Support cross-mode operations. Key: IGNITE-3554 URL: https://issues.apache.org/jira/browse/IGNITE-3554 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3541) Visrocmd returns emty list of caches

Sergey Kozlov created IGNITE-3541: - Summary: Visrocmd returns emty list of caches Key: IGNITE-3541 URL: https://issues.apache.org/jira/browse/IGNITE-3541 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-3544) IGFS: Review info() semantics - should it return null or throw exception if file doesn't exist?

Vladimir Ozerov created IGNITE-3544: --- Summary: IGFS: Review info() semantics - should it return null or throw exception if file doesn't exist? Key: IGNITE-3544 URL:

[jira] [Created] (IGNITE-3546) IGFS: Review events subsystem.

Vladimir Ozerov created IGNITE-3546: --- Summary: IGFS: Review events subsystem. Key: IGNITE-3546 URL: https://issues.apache.org/jira/browse/IGNITE-3546 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3542) IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try.

Vladimir Ozerov created IGNITE-3542: --- Summary: IGFS: Ensure IgfsPathIds.verifyIntegrity() always lead to re-try. Key: IGNITE-3542 URL: https://issues.apache.org/jira/browse/IGNITE-3542 Project:

[jira] [Created] (IGNITE-3545) IGFS: Review exceptions in secondary file system interface.

Vladimir Ozerov created IGNITE-3545: --- Summary: IGFS: Review exceptions in secondary file system interface. Key: IGNITE-3545 URL: https://issues.apache.org/jira/browse/IGNITE-3545 Project: Ignite

[jira] [Created] (IGNITE-3543) IGFS: Merge isRetryForSecondary() and verifyIntegrity() methods.

Vladimir Ozerov created IGNITE-3543: --- Summary: IGFS: Merge isRetryForSecondary() and verifyIntegrity() methods. Key: IGNITE-3543 URL: https://issues.apache.org/jira/browse/IGNITE-3543 Project:

[GitHub] ignite pull request #883: Ignite 1.6.3

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

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

[GitHub] ignite pull request #882: Ignite 7.6.3

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/882 --- 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-3547) Invalid message send retry with GridTcpNioCommunicationClient

Semen Boikov created IGNITE-3547: Summary: Invalid message send retry with GridTcpNioCommunicationClient Key: IGNITE-3547 URL: https://issues.apache.org/jira/browse/IGNITE-3547 Project: Ignite

[jira] [Created] (IGNITE-3555) IGFS: Expose IGFS as POSIX file system to OS.

Vladimir Ozerov created IGNITE-3555: --- Summary: IGFS: Expose IGFS as POSIX file system to OS. Key: IGNITE-3555 URL: https://issues.apache.org/jira/browse/IGNITE-3555 Project: Ignite Issue

[jira] [Created] (IGNITE-3557) Hadoop: integrate with Ambary management console.

Vladimir Ozerov created IGNITE-3557: --- Summary: Hadoop: integrate with Ambary management console. Key: IGNITE-3557 URL: https://issues.apache.org/jira/browse/IGNITE-3557 Project: Ignite

[jira] [Created] (IGNITE-3556) IGFS: Support external changes to the secondary file system.

Vladimir Ozerov created IGNITE-3556: --- Summary: IGFS: Support external changes to the secondary file system. Key: IGNITE-3556 URL: https://issues.apache.org/jira/browse/IGNITE-3556 Project: Ignite

[GitHub] ignite pull request #884: Ignite 3476

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

[GitHub] ignite pull request #884: Ignite 3476

Github user EdShangGG closed the pull request at: https://github.com/apache/ignite/pull/884 --- 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-3558) Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts

Taras Ledkov created IGNITE-3558: Summary: Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts Key: IGNITE-3558 URL: