[GitHub] ignite pull request #2440: IGNITE-5416: add Kafka-specific builder for Strea...

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/2440 IGNITE-5416: add Kafka-specific builder for StreamSingleTupleExtractor You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite

[GitHub] ignite pull request #1712: ignite-4847 : implemented

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1712 ignite-4847 : implemented You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-4 Alternatively you can review

[GitHub] ignite pull request #1696: IGNITE-4847 integrate log4j2 2.8.1

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

[GitHub] ignite pull request #1708: Ignite-4847 integrate log4j2 version 2.8.1

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

[GitHub] ignite pull request #1708: Ignite-4847 integrate log4j2 version 2.8.1

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1708 Ignite-4847 integrate log4j2 version 2.8.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-2 Alternatively you

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

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1707 Ignite-4828 Improve the distribution of keys within partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite IGNITE-4828

[GitHub] ignite pull request #1692: Ignite-4878

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1692 Ignite-4878 Replace conns collection with ConcurrentLinkedDeque to avoid possible concurrent modification exception You can merge this pull request into a Git repository by running: $ git

[GitHub] ignite pull request #1689: IGNITE-4847

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

[GitHub] ignite pull request #1689: IGNITE-4847

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1689 IGNITE-4847 ignite-4847 log4j2 2.8.1 upgrade You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-1 Alternatively

[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 https

[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

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

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1642 Ignite-4828 Improve the distribution of keys within partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite IGNITE-4828

[GitHub] ignite pull request: IGNITE-2169 Ignite-import-schema tool generat...

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/356 IGNITE-2169 Ignite-import-schema tool generates incorrect null schema for JDBC Ignite-import-schema tool generates incorrect null schema for JDBC You can merge this pull request into a Git

IGNITE-1903: CacheStore implementation is serialised to grid clients whether they require it or not

nging, but I am not confident that they can. If they cannot, I will have to abandon my clients joining the grid as clientMode=true and use some other method, probably laying my own transport layer over the top of Ignite, something that I had hoped to avoid. vkulichenko wrote > > endian675

[GitHub] ignite pull request: Ignite 1681

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

[GitHub] ignite pull request: Ignite 1681

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

[GitHub] ignite pull request: Ignite 1681

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

Re: HTTP-REST sql query ID problem

Alexey, No problem, here is a link that is relatively simple to understand : http://javarevisited.blogspot.co.uk/2011/02/fix-protocol-session-or-admin-messages.html However, a simplified approach of just adding a client ID seems sufficient - the sequence number reset functionality of FIX is

Java 7 client using Java 7 server, or vice versa

As mentioned on a post to the user list (http://apache-ignite-users.70518.x6.nabble.com/Mixing-Java-major-versions-on-client-server-td1380.html) it's not possible to connect a Java 7 client to a Java 8 server. Does anyone with intimate knowledge of the code know whether there are specific