[jira] [Created] (IGNITE-2706) GridHandleTable stores object at incorrect index

Denis Magda created IGNITE-2706: --- Summary: GridHandleTable stores object at incorrect index Key: IGNITE-2706 URL: https://issues.apache.org/jira/browse/IGNITE-2706 Project: Ignite Issue Type:

Re: OSGi Support?

Looks like the sun.nio.ch package is included in OpenJDK: http://hg.openjdk.java.net/jdk8/jdk8/jdk/file/tip/src/share/classes/sun/nio/ch/ServerSocketChannelImpl.java. But my bet is that Karaf doesn't export it by default because it is not part of the standard JRE spec. Raúl. On 20 Feb 2016

Re: Apache Arrow and Apache Ignite

Agree. Feel free to initiate a discussion on the Arrow list and cross-copy this list. I will also think about it some more and will propose something next week. On Sat, Feb 20, 2016 at 12:13 PM, Dood@ODDO wrote: > That's the million dollar question - I think we should

Re: Apache Arrow and Apache Ignite

That's the million dollar question - I think we should approach the Arrow people and get a conversation going. We want to be ahead of the curve, not behind it - Arrow seems to be making quite a stir, not to mention that it was fast-tracked to mature project status apparently solely based on

Re: OSGi Support?

Raul, To my knowledge Ignite can run under OpenJDK as well. Would this package be required in OpenJDK? D. On Sat, Feb 20, 2016 at 11:24 AM, Raul Kripalani wrote: > Hey John, > > Yeah, this is expected. Ignite uses some packages only available in the > Oracle JDK (proprietary

Re: OSGi Support?

Hey John, Yeah, this is expected. Ignite uses some packages only available in the Oracle JDK (proprietary Sun packages). Karaf doesn't export the sun.nio.ch package by default from bundle 0 (system bundle). You need to add it to the jre.properties file manually in the Karaf etc directory. Then

Re: Binary object inside Externalizable

Andrey, you are absolutely right. I was suggesting a quick fix, which in my view, would fix most of the issues. In the long term, we should fix the binary serialization to work the way you are describing. D. On Sat, Feb 20, 2016 at 9:26 AM, Andrey Kornev wrote: > Val,

Re: ODBC processor default behaviour

What's about to use the port range like TcpDiscoveryVmIpFinder? On Sat, Feb 20, 2016 at 6:22 PM, Yakov Zhdanov wrote: > How about outputting warning like and keep retrying in a background thread? > > warning - "Failed to bind ODBC processor TCP server to port (retrying

Re: ODBC processor default behaviour

How about outputting warning like and keep retrying in a background thread? warning - "Failed to bind ODBC processor TCP server to port (retrying every 2 sec) [port=ABC] --Yakov 2016-02-20 17:38 GMT+03:00 Igor Sapego : > Igniters, > > I'm currently working on the ODBC

Re: OSGi Support?

Raul, can you please help with the issue? --Yakov 2016-02-20 18:03 GMT+03:00 John D. Ament : > Hey guys > > I was looking at a Camel issue this morning. > > https://issues.apache.org/jira/browse/CAMEL-9458 > > It appears that camel-ignite doesn't install properly in

[GitHub] ignite pull request: IGNITE-2704: Disabled ODBC for core tests.

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/507 IGNITE-2704: Disabled ODBC for core tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/isapego/ignite ignite-2704 Alternatively you can

[GitHub] ignite pull request: IGNITE-2273

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

ODBC processor default behaviour

Igniters, I'm currently working on the ODBC driver. It connects by TCP to the OdbcProcessor on the node side. OdbcProcessor is enabled by default and it starts TCP server on the specific TCP port or throws exception if the port is busy. The problem is that such behavior breaks tests that start

Re: Binary mode for Data Structures

No replies, so I've created an issue: https://issues.apache.org/jira/browse/IGNITE-2701 On Thu, Feb 18, 2016 at 3:06 PM, Pavel Tupitsyn wrote: > Igniters, > > Currently we don't have binary mode (withKeepBinary) in Data Structures > (Queue, AtomicReference). > Are there

[jira] [Created] (IGNITE-2701) Binary mode in Data Structures

Pavel Tupitsyn created IGNITE-2701: -- Summary: Binary mode in Data Structures Key: IGNITE-2701 URL: https://issues.apache.org/jira/browse/IGNITE-2701 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-2700) GridClosureProcessor internal closures are [de]serialized by OptimizedMarshaller even if BinaryMarshaller is configured

Ilya Lantukh created IGNITE-2700: Summary: GridClosureProcessor internal closures are [de]serialized by OptimizedMarshaller even if BinaryMarshaller is configured Key: IGNITE-2700 URL:

[GitHub] ignite pull request: IGNITE-2621 .NET: Fix compute in mixed-platfo...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/505 IGNITE-2621 .NET: Fix compute in mixed-platform cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-2621

Re: NoopSwapSpaceSpi and dynamically started caches

Hello. Patch for https://issues.apache.org/jira/browse/IGNITE-2650 is available. Please review. On Thu, Feb 18, 2016 at 2:10 PM, Konstantin Margorin wrote: > Yakov, thank you. Sounds good. I'll do this way. > > On Thu, Feb 18, 2016 at 1:43 PM, Yakov Zhdanov

[GitHub] ignite pull request: IGNITE-2654

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/504 IGNITE-2654 Just for demonstration, do not merge. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-2654 Alternatively