[GitHub] ignite pull request: IGNITE-10 Fix ignite components [de]serializa...

GitHub user VladimirErshov opened a pull request: https://github.com/apache/ignite/pull/246 IGNITE-10 Fix ignite components [de]serialization IgniteSpiThread holds now gridName. It's obtained through IgnitionEx.gridName() for IgniteKernal readResolve. It could be useful to

Re: Ignite-1.5 Release

Hi folks, I merged performance optimizations for tx mode which gave up to 5% improvement for tx-put benchmark to ignite-1.5. I also pushed finalizaing changes to Binary configuration in ignite-1945 branch and currently waiting for TC. If all is ok, will cooperate with Vladimir Ozerov and merge

[jira] [Created] (IGNITE-1945) Get rid of keepDeserialized flag in configuration

Alexey Goncharuk created IGNITE-1945: Summary: Get rid of keepDeserialized flag in configuration Key: IGNITE-1945 URL: https://issues.apache.org/jira/browse/IGNITE-1945 Project: Ignite

[jira] [Created] (IGNITE-1944) .Net: IgniteConfiguration properties

Pavel Tupitsyn created IGNITE-1944: --- Summary: .Net: IgniteConfiguration properties Key: IGNITE-1944 URL: https://issues.apache.org/jira/browse/IGNITE-1944 Project: Ignite Issue Type:

Branch deletion prohibited

Fellows, I'm trying to push a branch deletion and the ASF Git tells me that branch deletion is prohibited. Has someone changed something? [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790 remote: error: denying ref deletion for refs/heads/ignite-1790 To

Re: Branch deletion prohibited

Raul, ASF is currently prohibiting deletion of GIT branches until further notice. Please add your branch to this Wiki page, so we don’t loose track: https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete Thanks, D. On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani

Re: Ignite-1.5 Release

Hi Alex, Today I marged several big things into 1282 - reworked metadat and compacted footers optimization. I have on big ticket left - IGNITE-1917 - with marshalling microoptimizations. They should not conflict with anything and I expect them to be finalized tomorrow. All optimizations are

[GitHub] ignite pull request: IGNITE-1768 .Net: Review portable configurati...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/187 --- 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: IGNITE-1834 .Net: Remove MetadataEnabled prop...

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

[jira] [Created] (IGNITE-1941) BinaryObject: review field() and hasField() methods.

Vladimir Ozerov created IGNITE-1941: --- Summary: BinaryObject: review field() and hasField() methods. Key: IGNITE-1941 URL: https://issues.apache.org/jira/browse/IGNITE-1941 Project: Ignite

[jira] [Created] (IGNITE-1942) Binary format: minimize map lookups during read.

Vladimir Ozerov created IGNITE-1942: --- Summary: Binary format: minimize map lookups during read. Key: IGNITE-1942 URL: https://issues.apache.org/jira/browse/IGNITE-1942 Project: Ignite

[jira] [Created] (IGNITE-1940) Wrong file names in the ignite-1282 branch

Vasilisa Sidorova created IGNITE-1940: -- Summary: Wrong file names in the ignite-1282 branch Key: IGNITE-1940 URL: https://issues.apache.org/jira/browse/IGNITE-1940 Project: Ignite

[GitHub] ignite pull request: Ignite-1900

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

On 11/17/2015 9:37 PM, Yakov Zhdanov wrote: 1. Understood 2. Well, I understand that object gets deserialized on get from cache and this most probably should not cause any issue. However, code does not look healthy and someone may think that there is an issue - field is not volatile,

[GitHub] ignite pull request: IGNITE-1910 .Net: Possible handle leak in Sca...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/232 --- 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: IGNITE-1664 .Net: Review generic type argumen...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/154 --- 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: IGNITE-1289 Platforms .Net: Move portable mar...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/46 --- 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: IGNITE-1662 .Net: Improve docs for IEvents an...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/148 --- 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: IGNITE-1572 .Net: Check if we can get rid of ...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/122 --- 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: IGNITE-1682 .Net: Remove RemoteListen from Ev...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/158 --- 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: IGNITE-1435 Platform .Net: Make it possible t...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/84 --- 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: IGNITE-1340 Platforms .Net: Fix PlatformCache...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/54 --- 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: IGNITE-1367 Platforms .Net: Move grid executa...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/70 --- 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: IGNITE-1492 Platform .Net: Set up FxCop proje...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/95 --- 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: IGNITE-1645 .Net: Throw exception on null fla...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/146 --- 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: IGNITE-1845 .Net: Adopt portable API changes.

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/212 --- 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: IGNITE-1696 .Net: Ignite does not start with ...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/161 --- 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: IGNITE-1480 Platform .Net: IClusterNode.IsCli...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/90 --- 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: IGNITE-1934 .Net: Store tests broken after ke...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/243 --- 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: IGNITE-1912 .Net: Continuous query does not w...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/233 --- 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: IGNITE-1845 .Net: Adopt portable API changes.

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/207 --- 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: IGNITE-1589 Platform .Net: CacheAbstractTest....

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/119 --- 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: IGNITE-1509 .Net: User must operate on IEnume...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/140 --- 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: IGNITE-1416 .Net: Implement AtomicLong data s...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/111 --- 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: IGNITE-1562 .Net: Remove "Generic" word from ...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/125 --- 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: IGNITE-1565 Platform .Net: Fix examples

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/112 --- 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: IGNITE-1677 .Net: Sign assemblies and store S...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/159 --- 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: IGNITE-1652 .Net: Rework async APIs (remove W...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/175 --- 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: IGNITE-1644 .Net: DateTime.Kind is lost durin...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/173 --- 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: IGNITE-1665 .Net: Cache field IDs when deseri...

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

Hi, Yesterday I merged optimizations for tx update operations working single key, got ~7% improvement in tx-put benchmark. And today I finished to implement optimization for cache 'get' operation with single key. Got another benchmark results improvements: ~10% with atomic-put-get, ~5% with

Re: Ignite-1.5 Release

On Wed, Nov 18, 2015 at 2:17 PM, Raul Kripalani wrote: > I merged the Camel Streamer today and I hope to finish the first phase of > OSGi tomorrow. > > I'll need someone to review the latter quickly if we want it merged for > 1.5... No code changes in existing codebase. Just a

Re: Ignite-1.5 Release

I merged the Camel Streamer today and I hope to finish the first phase of OSGi tomorrow. I'll need someone to review the latter quickly if we want it merged for 1.5... No code changes in existing codebase. Just a new osgi module and many POM changes mainly to generate the manifests. Should be a

[jira] [Created] (IGNITE-1946) Rework Schema Import Utility to generate code with new API

Alexey Kuznetsov created IGNITE-1946: Summary: Rework Schema Import Utility to generate code with new API Key: IGNITE-1946 URL: https://issues.apache.org/jira/browse/IGNITE-1946 Project: Ignite

[jira] [Created] (IGNITE-1947) Make more detailed error message

Pavel Konstantinov created IGNITE-1947: -- Summary: Make more detailed error message Key: IGNITE-1947 URL: https://issues.apache.org/jira/browse/IGNITE-1947 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

Denis Magda created IGNITE-1948: --- Summary: ClusterTopologyCheckedException can return null for retryReadyFuture() Key: IGNITE-1948 URL: https://issues.apache.org/jira/browse/IGNITE-1948 Project: Ignite