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

[VladimirErshov]

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 check, that those classes don't suffer also from this 
issue:
* GridPortableContext
* GridKernalContextImpl
* ClusterGroupAdapter
* ClusterNodeLocalMapImpl
* PortableContext

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/VladimirErshov/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/246.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #246


commit 89781a9f5b63da38069191576a5647194d90e58e
Author: vershov 
Date:   2015-11-18T17:26:13Z

IGNITE-10 Fix ignite components [de]serialization

commit 7dee5b2d0f62578b139fcaf0aefcc44d823e4f70
Author: vershov 
Date:   2015-11-18T17:31:49Z

IGNITE-10 Fix ignite components [de]serialization




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite-1.5 Release

[Alexey Goncharuk]

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 changes tomorrow.

2015-11-18 17:58 GMT+03:00 Semyon Boikov :

> 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 tx-put-get. Need to verify TC and hopefully will
> merge these changes tomorrow.
>
> ​
>

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

[Alexey Goncharuk (JIRA)]

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
  Issue Type: Sub-task
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Pavel Tupitsyn (JIRA)]

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: Sub-task
  Components: interop
Affects Versions: 1.1.4
Reporter: Pavel  Tupitsyn
 Fix For: 1.6


Configure basic IgniteConfiguration properties in C# code:
* clientMode
* timeouts
* log frequency
* etc




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Branch deletion prohibited

[Raul Kripalani]

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 https://git-wip-us.apache.org/repos/asf/ignite
 ! [remote rejected] ignite-1790 (deletion prohibited)
error: failed to push some refs to '
https://git-wip-us.apache.org/repos/asf/ignite'

Regards,

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

Re: Branch deletion prohibited

[Dmitriy Setrakyan]

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  wrote:

> 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 https://git-wip-us.apache.org/repos/asf/ignite
>  ! [remote rejected] ignite-1790 (deletion prohibited)
> error: failed to push some refs to '
> https://git-wip-us.apache.org/repos/asf/ignite'
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>

Re: Ignite-1.5 Release

[Vladimir Ozerov]

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 ready, I
just need to perform some cleanup and refactoring.

On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> 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 changes tomorrow.
>
> 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
>
> > 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 tx-put-get. Need to verify TC and hopefully will
> > merge these changes tomorrow.
> >
> > ​
> >
>

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

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1834 .Net: Remove MetadataEnabled prop...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[Vladimir Ozerov (JIRA)]

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
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


There are TODOs suggesting removal of these methods.

I think we should keep these methods because they are convenient shortcuts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vladimir Ozerov (JIRA)]

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
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


Currently we have to perform at least 3 hash map lookups from BinaryReader to 
PortableContext:
- ID mapper
- Schema registry
- Class descriptor.

We must refactor PortableContext to allow for only single lookup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Vasilisa Sidorova (JIRA)]

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
  Issue Type: Bug
  Components: general
Affects Versions: 1.5
Reporter: Vasilisa  Sidorova
Assignee: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5


At this moment there is error in the ignite-1282 sources: in the 
/examples/config/ config example-default.xml is renamed into 
example-ignite.xml. And conversely: example-ignite.xml is renamed into 
example-default.xml. Please, fix it before merge. Оtherwise many of examples 
will be failed with "new" example-ignite.xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: Ignite-1900

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite-1.5 Release

[Denis Magda]

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, initialized in constructor, has sync setter, but is accessed
several times in code outside of sync. Can you please refactor this?
3. Yes, Denis is looking into this. And I think your issue will be fixed in
the scope of Denis one.
I'm afraid that my changes won't fix the issue in Vladislav's 
implementation.
However, when my changes are merged we will be able to rework these 
semaphore failover tests and fix any issue in the semaphore impl related 
to failover. I can take care of this.


--
Denis



Vlad, can you please refactor [2] and I will pick it up and merge tomorrow.

Thank you for your interest and contribution!

--Yakov

2015-11-17 21:30 GMT+04:00 Vladisav Jelisavcic :


Hi Yakov,
1. Yes

2. if you mean that nodeMap is accessed in onNodeRemoved(UUID nodeID)
method of the GridCacheSemaphoreImpl class,
it shouldn't be a problem, but it can be changed easily not to do so;

3.

org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantTopologyChangeFailoverSafe()

org.apache.ignite.internal.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest#testSemaphoreConstantMultipleTopologyChangeFailoverSafe()

I think the problem is with the atomicity of the simulated grid failure;
once stopGrid() is called for a node, other threads on this same node start
throwing interrupted exceptions,
which are in turn not handled properly in the
GridCacheAbstractDataStructuresFailoverSelfTest;
Those exceptions shouldn't be dealt with inside the GridCacheSemaphoreImpl
itself.
In a realworld node failure scenario, all those threads would fail at the
same time
(none of them would influence the rest of the grid anymore);

I think fixing the issue Denis is working on can fix this (IGNITE-801 and
IGNITE-803)
Am i right? Does it makes sense?


Best regards,
Vladisav

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

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1664 .Net: Review generic type argumen...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1289 Platforms .Net: Move portable mar...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1662 .Net: Improve docs for IEvents an...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1572 .Net: Check if we can get rid of ...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1682 .Net: Remove RemoteListen from Ev...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1435 Platform .Net: Make it possible t...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1340 Platforms .Net: Fix PlatformCache...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1367 Platforms .Net: Move grid executa...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1492 Platform .Net: Set up FxCop proje...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1645 .Net: Throw exception on null fla...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1845 .Net: Adopt portable API changes.

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1696 .Net: Ignite does not start with ...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1480 Platform .Net: IClusterNode.IsCli...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1934 .Net: Store tests broken after ke...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1912 .Net: Continuous query does not w...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1845 .Net: Adopt portable API changes.

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1589 Platform .Net: CacheAbstractTest....

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1509 .Net: User must operate on IEnume...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1416 .Net: Implement AtomicLong data s...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1562 .Net: Remove "Generic" word from ...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1565 Platform .Net: Fix examples

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1677 .Net: Sign assemblies and store S...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1652 .Net: Rework async APIs (remove W...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1644 .Net: DateTime.Kind is lost durin...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-1665 .Net: Cache field IDs when deseri...

[ptupitsyn]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite-1.5 Release

[Semyon Boikov]

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 tx-put-get. Need to verify TC and hopefully will
merge these changes tomorrow.

​

Re: Ignite-1.5 Release

[Dmitriy Setrakyan]

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 new osgi module and
> many POM changes mainly to generate the manifests.
>

Raul, did you create a patch or a PR? I can’t find it anywhere.


>
> Should be a quick task.
>
> Regards,
> Raúl.
> On 18 Nov 2015 20:38, "Vladimir Ozerov"  wrote:
>
> > 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 ready,
> I
> > just need to perform some cleanup and refactoring.
> >
> > On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > 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 changes tomorrow.
> > >
> > > 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
> > >
> > > > 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 tx-put-get. Need to verify TC and hopefully
> > will
> > > > merge these changes tomorrow.
> > > >
> > > > ​
> > > >
> > >
> >
>

Re: Ignite-1.5 Release

[Raul Kripalani]

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 quick task.

Regards,
Raúl.
On 18 Nov 2015 20:38, "Vladimir Ozerov"  wrote:

> 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 ready, I
> just need to perform some cleanup and refactoring.
>
> On Wed, Nov 18, 2015 at 7:22 PM, Alexey Goncharuk <
> alexey.goncha...@gmail.com> wrote:
>
> > 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 changes tomorrow.
> >
> > 2015-11-18 17:58 GMT+03:00 Semyon Boikov :
> >
> > > 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 tx-put-get. Need to verify TC and hopefully
> will
> > > merge these changes tomorrow.
> > >
> > > ​
> > >
> >
>

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

[Alexey Kuznetsov (JIRA)]

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
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.5
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.5


Schema Import Utility Should generate XML and Java code for new Queries and 
Pojo store API



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Pavel Konstantinov (JIRA)]

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: Sub-task
Reporter: Pavel Konstantinov


The current message is:
{code}
Error: Failed to find query with ID: 2
{code}

It looks like a bug, but the actual reason is that query was timed out.
I suggest to add a possible reasons to the message such as:
1) Time out
2) Node restart




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Denis Magda (JIRA)]

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
  Issue Type: Bug
  Components: general
Reporter: Denis Magda
 Fix For: 1.6


It was noted that {{ClusterTopologyCheckedException}} ready future can be null.

Go though all the places where this kind of exception is being initialized and 
check why the ready future is not set in some cases.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)