[jira] [Created] (IGNITE-3715) Incorrect Hibernate L2 cache statistics

Valentin Kulichenko created IGNITE-3715: --- Summary: Incorrect Hibernate L2 cache statistics Key: IGNITE-3715 URL: https://issues.apache.org/jira/browse/IGNITE-3715 Project: Ignite Issue

[GitHub] ignite pull request #974: IGNITE-3314 Implement Serializable in org.apache.i...

GitHub user irudyak opened a pull request: https://github.com/apache/ignite/pull/974 IGNITE-3314 Implement Serializable in org.apache.ignite.cache.store.cassandra.datasource.DataSource You can merge this pull request into a Git repository by running: $ git pull https://github

[GitHub] ignite pull request #973: IGNITE-3627: Tuned ODBC capabilities to match capa...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/973 IGNITE-3627: Tuned ODBC capabilities to match capabilities of the Ignite SQL. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-i

Re: copyOnRead performance issues

Yakov, I've checked the current master and found out what only 2 of 4 system caches were updated to have copyOnRead=false. I'm wondering why. The work was done for https://issues.apache.org/jira/browse/IGNITE-3569 issue. Regarding the hint I've filed the new issue: https://issues.apache.org/jira/

[jira] [Created] (IGNITE-3714) Introduce new performance hint for default store-by-value caches behavior.

Alexei Scherbakov created IGNITE-3714: - Summary: Introduce new performance hint for default store-by-value caches behavior. Key: IGNITE-3714 URL: https://issues.apache.org/jira/browse/IGNITE-3714

[GitHub] ignite pull request #972: IGNITE-3625 IGFS: Use common naming for IGFS meta ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/972 IGNITE-3625 IGFS: Use common naming for IGFS meta and data caches. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-igni

[jira] [Created] (IGNITE-3713) .NET: Possible NPE in PlatformConfigurationUtils due to null Enum values

Pavel Tupitsyn created IGNITE-3713: -- Summary: .NET: Possible NPE in PlatformConfigurationUtils due to null Enum values Key: IGNITE-3713 URL: https://issues.apache.org/jira/browse/IGNITE-3713 Project:

[GitHub] ignite pull request #923: IGNITE-3625 IGFS: Use common naming for IGFS meta ...

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

[GitHub] ignite pull request #854: ignite-2795

Github user ascherbakoff closed the pull request at: https://github.com/apache/ignite/pull/854 --- 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 #971: IGNITE-3711 .NET: PlatformRawMemory is not covered...

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

[GitHub] ignite pull request #971: IGNITE-3711 .NET: PlatformRawMemory is not covered...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/971 IGNITE-3711 .NET: PlatformRawMemory is not covered with tests * Remove unused code * Add asserts You can merge this pull request into a Git repository by running: $ git pull https://githu

[jira] [Created] (IGNITE-3712) test

Semen Boikov created IGNITE-3712: Summary: test Key: IGNITE-3712 URL: https://issues.apache.org/jira/browse/IGNITE-3712 Project: Ignite Issue Type: Bug Reporter: Denis Kholodov

[GitHub] ignite pull request #909: JB Annotatins required only at Ignite sources comp...

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

[jira] [Created] (IGNITE-3711) .NET: PlatformRawMemory is not covered with tests

Pavel Tupitsyn created IGNITE-3711: -- Summary: .NET: PlatformRawMemory is not covered with tests Key: IGNITE-3711 URL: https://issues.apache.org/jira/browse/IGNITE-3711 Project: Ignite Issue

Re: Ignite Maven project version number

I'm not a Maven expert and do not see all the consequences, but so far everything worked well. Why change it? Especially if we do not have a consensus in our community. I think we can't accept this change until everyone agrees. Sergi 2016-08-19 10:28 GMT+03:00 Anton Vinogradov : > Igor, > > > >

Re: Ignite Maven project version number

Igor, > Well, it's all about how to minimize copy-pasting parent version to > constantly growing amount of module POMs while switching to development of > new version. Don't worry about it, currently we use bash script to do that, it based on release:update-versions, and it will be relocated to