Re: Should we take care of Java 9 in Ignite 2.0 scope?

> For using internal classes that not exported by default, we will need to > add new args(--add-exports) when compiling (javac) *and* when running (java > ). > Is it ok? Anton, are you fine with this approach? — Denis > On Mar 21, 2017, at 11:05 AM, Evgenii Zhuravlev

Re: Should we take care of Java 9 in Ignite 2.0 scope?

IMO: 1) sun.misc.PerfCounter usages must be removed 2) sun.misc.Cleaner - either remove, try to switch to DirectByteBuffer or Unsafe.allocateMemory() if possible, or create a wrapper delegating to official Cleaner from Java9. 3) sun.misc.URLClassPath and sun.misc.SharedSecrets - used only in one

[GitHub] ignite pull request #1660: Ignite 4587 tmp

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

Re: Should we take care of Java 9 in Ignite 2.0 scope?

Denis, I've found that some internal classes like sun.misc.SharedSecrets, sun.misc.URLClassPath, sun.misc.PerfCounter, sun.misc.Cleaner changed their packages. I can create wrapper for this classes with 2 modules, that can be enabled by profiles for java9 and java7-8. For using internal classes

Re: CacheStore and Transaction

Even with transactional cache, it's correct that updates are propagated to CacheWriter methods. It's up to CacheStore implementation to maintain underlying transaction on persistence store and commit or rollback it depending on cache transaction status. Usually it's done with the help of session

[GitHub] ignite pull request #1659: Ignite 1.8.4-p1

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

[GitHub] ignite pull request #1658: 1.8.4 p1

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

[GitHub] ignite pull request #1653: IGNITE-4846 .NET: Support complex type dictionari...

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

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

[GitHub] ignite pull request #728: ignite-db-x

Github user sboikov closed the pull request at: https://github.com/apache/ignite/pull/728 --- 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 #1657: ignite-4844

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

[GitHub] ignite pull request #1656: IGNITE-4691: Implemented Time type for ODBC.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/1656 IGNITE-4691: Implemented Time type for ODBC. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4691 Alternatively

[GitHub] ignite pull request #1655: IGNITE-4302 BinaryMetadata exchange protocol refa...

GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/1655 IGNITE-4302 BinaryMetadata exchange protocol refactored... ... to use **CustomDiscoveryMessage**s instead of system cache You can merge this pull request into a Git repository by

[GitHub] ignite pull request #1654: IGNITE-4827 Remove deprecated code related to bac...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1654 IGNITE-4827 Remove deprecated code related to backward compatibility You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1653: IGNITE-4846 .NET: Support complex type dictionari...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1653 IGNITE-4846 .NET: Support complex type dictionaries in app.config configuration You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1652: IGNITE-3682

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1652 IGNITE-3682 PR after removing ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-3682 Alternatively you can

[GitHub] ignite pull request #1651: IGNITE-4211

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1651 IGNITE-4211 PR after removing ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4211 Alternatively you can

[GitHub] ignite pull request #1650: IGNITE-3592

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/1650 IGNITE-3592 PR after removing ignite-2.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-3592 Alternatively you can

[GitHub] ignite pull request #1649: Ignite 4558 Use BinaryArrayIdentityResolver by de...

GitHub user ezhuravl opened a pull request: https://github.com/apache/ignite/pull/1649 Ignite 4558 Use BinaryArrayIdentityResolver by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4558

[GitHub] ignite pull request #1621: 1.8.4

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1621 --- 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 #1648: IGNITE-4475 Simplify async API

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1648 IGNITE-4475 Simplify async API You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4475-async

[GitHub] ignite pull request #1647: Ignite 3018 fair

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1647 Ignite 3018 fair You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3018-fair Alternatively you can

[GitHub] ignite pull request #1603: IGNITE-4211

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1603 --- 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 #1622: IGNITE-3575: CPP: Implemented remote filters for ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1622 --- 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 #1436: IGNITE-4501: Improvement of connection in a clust...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1646 --- 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 #1598: IGNITE-4690: CPP: Added support for Time type

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1598 --- 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 #1638: IGNITE-3487: Made _key and _val columns hidden

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

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

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1614 --- 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 #1637: IGNITE-3586: CPP: Made QueryArgument internal

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1637 --- 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 #1467: IGNITE-4558 Use BinaryArrayIdentityResolver by de...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1467 --- 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 #1525: IGNITE-4617: Added field-access methods for Binar...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1525 --- 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 #1575: IGNITE-3018: RendezvousAffinityFunction performan...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1575 --- 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 #1534: IGNITE-4650: Scan and SPI queries must go through...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1600 --- 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 #1629: IGNITE-3429: org.hibernate.cache.spi.CacheKey not...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1629 --- 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 #1587: IGNITE-3939 Compact long zero values binary repre...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1588 --- 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 #1435: IGNITE-3207: Rename IgniteConfiguration.gridName

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1435 --- 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 #1518: IGNITE-2703 .NET: Dynamic type registration

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1518 --- 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 #1506: IGNITE-4302 binary metadata component refactored ...

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

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

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

[GitHub] ignite pull request #1579: Ignite 4755

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1579 --- 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 #1507: IGNITE-4663: skip class loading when deserialize ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1507 --- 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 #1512: IGNITE-4673 Object array element type is written ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1512 --- 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 #972: IGNITE-3625 IGFS: Use common naming for IGFS meta ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/972 --- 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 #1566: IGNITE-824 Remove GridRandomSelfTest

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1566 --- 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 #1513: IGNITE-4511: Set QueryIndexType.SORTED by default...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1513 --- 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 #1346: IGNITE-4399: remove IgfsSecondaryFileSystemV2, im...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1409 --- 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 #1626: IGNITE-4824 Remove: AffinityTask.affinityKey meth...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1626 --- 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 #1252: IGNITE-3961 IGFS: Support direct PROXY mode invoc...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1252 --- 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 #1474: IGNITE-1495 Uppercase index fields in metadata

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1474 --- 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 #1251: IGNITE-2356 IGFS client should be able to failove...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1251 --- 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 #1469: IGNITE-4105 Introduced separate thread pool for S...

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

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1470 --- 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 #1173: IGNITE-3875 Create separate thread pool for data ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1173 --- 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 #1362: IGNITE-4441 Define plugin API in .NET

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

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1645 Ignite 4828 Improve distribution of keys within partitions, for partition counts that are a power of 2. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1642: Ignite-4828

Github user endian675 closed the pull request at: https://github.com/apache/ignite/pull/1642 --- 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 #1644: IGNITE-4811

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

[jira] [Created] (IGNITE-4846) .NET: Support complex type dictionaries in app.config configuration

Pavel Tupitsyn created IGNITE-4846: -- Summary: .NET: Support complex type dictionaries in app.config configuration Key: IGNITE-4846 URL: https://issues.apache.org/jira/browse/IGNITE-4846 Project: