[jira] [Created] (IGNITE-1884) .Net: JNI local ref can't be accessed from another thread

Pavel Tupitsyn created IGNITE-1884: --- Summary: .Net: JNI local ref can't be accessed from another thread Key: IGNITE-1884 URL: https://issues.apache.org/jira/browse/IGNITE-1884 Project: Ignite

Re: Ignite-1.5 Release

Sorry I haven't made an appearance in this thread yet. > 6. MQTT streamer > https://issues.apache.org/jira/browse/IGNITE-535 Yes, it was merged to master before the ignite-1.5 was created. I'd like to add: Camel Streamer => https://issues.apache.org/jira/browse/IGNITE-1790 -- I'll merge this

Re: Ignite-1.5 Release

Guys, A quick update on the release status. I have spotted several potential slowdowns that I would like to add to 1.5 release. I am currently working in a separate branch and preliminary testing showed that we can get about 4-5% performance improvement in tx-put benchmark. There are other

[GitHub] ignite pull request: IGNITE-1566: fix + new test.

GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/216 IGNITE-1566: fix + new test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1566 Alternatively you can review

RE: OSGi migration may require a special marshaller

Raul, Could you please be a bit more specific about the nature of your disagreement? Is the proposed SPI not generic enough? Or, is it just the naming? As per Romain's suggestion, could you please just make sure the SPI is hooked into the new marshalling implementation and a no-op codec

Re: OSGi migration may require a special marshaller

Hi Romain, The implementation I have in mind won't be costly. I'm working on it this week. I still don't agree with a ClassLoaderCodec SPI as-is. If we create an SPI it should be for more generic hinting applicable in other circumstances during serialisation with other frameworks and what not.

[jira] [Created] (IGNITE-1885) Ignite ZooKeeper: Upgrade Curator to 2.9.1

Raúl Kripalani created IGNITE-1885: -- Summary: Ignite ZooKeeper: Upgrade Curator to 2.9.1 Key: IGNITE-1885 URL: https://issues.apache.org/jira/browse/IGNITE-1885 Project: Ignite Issue Type:

Ignite interpreter for Zeppelin

Guys, we are working to have Zeppelin as a part of upcoming Bigtop 1.1 stack. Does anyone here has/can share with us the interpreter.json content for Ignite, so we don't need to re-invent the wheel? Thanks in advance! -- Take care, Cos 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622

[jira] [Created] (IGNITE-1886) NPE in H2 when running query with subselects

Valentin Kulichenko created IGNITE-1886: --- Summary: NPE in H2 when running query with subselects Key: IGNITE-1886 URL: https://issues.apache.org/jira/browse/IGNITE-1886 Project: Ignite

Re: GIT branch audit

Branch deletion moratorium is a temp. thing. Should be lifted once they figure out a couple of things... Shouldn't be set in the first place, IMO On Mon, Nov 09, 2015 at 01:59PM, Artem Shutak wrote: > Igniters, > > Since no one can delete any branch Apache Git repo I've been created >

Re: IGNITE-1681: loadAll threshold is not configurable for CacheStoreBalancingWrapper

Hi Denis I'm looking at it now Regards Mike On Tue, Nov 10, 2015 at 11:19 AM, Denis Magda wrote: > Michael, > > Would you mind finishing that task? You should add a couple of tests to > validate that everything works is expected. I've put all the info into the > ticket. >

OSGi Manifest headers and feature repository pushed (IGNITE-1527)

Hi all, Just to inform you that I've pushed the POM changes to generate the OSGi Manifest for all Java modules except: gce, cloud, hadoop, log4j2, spark, yarn, mesos, as the prove a bit more difficult for different reasons each. Some modules are bundles (e.g. mqtt, zookeeper, kafka, etc.) while

Fwd: LOCAL CACHE MODE Configuration settings

Igniters, While investigating this issue reported by user, I noticed that LOCAL cache is fully destroyed when close() is called, which is inconsistent with other cache modes. Is there any reason for this? -Val -- Forwarded message -- From: vkulichenko

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

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

[jira] [Created] (IGNITE-1878) Implement support to package manager for vendor libs

Dmitriyff created IGNITE-1878: - Summary: Implement support to package manager for vendor libs Key: IGNITE-1878 URL: https://issues.apache.org/jira/browse/IGNITE-1878 Project: Ignite Issue Type:

[GitHub] ignite pull request: ignite-1817 Deprecate RandomEvictionPolicy an...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/191 --- 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: About the newbie bug #IGNITE-881

Hi Ken! My idea was to quit using distributed atomic long, but switch to invokes that change values atomically. In most cases this can work over atomic cache and provide faster performance. Does anyone in community have comments? --Yakov 2015-11-10 10:49 GMT+03:00 Ken Cheng

Re: 127.0.0.1 in VmIpFinder

Val, I've tried to run the nodes using the configuration discussed below on OS X Yosemity. Works perfectly fine, both nodes joined the topology and see each other. Will try to check on OS X El Captain a bit later. BTW, the problem may be in IPv6. I googled for post [1]. The issue discussed

IGNITE-1681: loadAll threshold is not configurable for CacheStoreBalancingWrapper

Michael, Would you mind finishing that task? You should add a couple of tests to validate that everything works is expected. I've put all the info into the ticket. Regards, Denis

[jira] [Created] (IGNITE-1880) .Net: Intermittent "Invalid global JNI handle passed to DeleteGlobalRef"

Pavel Tupitsyn created IGNITE-1880: --- Summary: .Net: Intermittent "Invalid global JNI handle passed to DeleteGlobalRef" Key: IGNITE-1880 URL: https://issues.apache.org/jira/browse/IGNITE-1880

[jira] [Created] (IGNITE-1881) .Net: Rename "portable" to "binary/binarizable"

Pavel Tupitsyn created IGNITE-1881: --- Summary: .Net: Rename "portable" to "binary/binarizable" Key: IGNITE-1881 URL: https://issues.apache.org/jira/browse/IGNITE-1881 Project: Ignite Issue

Re: OSGi migration may require a special marshaller

Gentlemen, I have several comments below… On Tue, Nov 10, 2015 at 11:52 AM, Raul Kripalani wrote: > Andrey, I already specified some points of my disagreement in the Wiki. In > my previous email I also said: "If we create an SPI it should be for more > generic hinting

[GitHub] ignite pull request: IGNITE-1880 .Net: Intermittent "Invalid globa...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/213 IGNITE-1880 .Net: Intermittent "Invalid global JNI handle passed to DeleteGlobalRef" You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request: IGNITE-1881 .Net: Rename "portable" to "binar...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/214 IGNITE-1881 .Net: Rename "portable" to "binary/binarizable" You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-1881

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

Re: OSGi migration may require a special marshaller

Hi, I have put my comments. Hope they will make the things progress :) Should I start to implement this ticket or should I wait and see if Raoul want to take it? Romain Le mar. 10 nov. 2015 à 02:58, Dmitriy Setrakyan a écrit : > Thanks Raul, great points! I have created

[jira] [Created] (IGNITE-1882) Rename BinaryTypeIdMapper to BinaryIdMapper

Vladimir Ozerov created IGNITE-1882: --- Summary: Rename BinaryTypeIdMapper to BinaryIdMapper Key: IGNITE-1882 URL: https://issues.apache.org/jira/browse/IGNITE-1882 Project: Ignite Issue

[jira] [Created] (IGNITE-1883) Test path to swap files of a cache during cache creating

Sergey Kozlov created IGNITE-1883: - Summary: Test path to swap files of a cache during cache creating Key: IGNITE-1883 URL: https://issues.apache.org/jira/browse/IGNITE-1883 Project: Ignite