[jira] [Created] (IGNITE-3322) collect transaction log

2016-06-15 Thread Alexandre Boudnik (JIRA)
Alexandre Boudnik created IGNITE-3322:
-

 Summary: collect transaction log
 Key: IGNITE-3322
 URL: https://issues.apache.org/jira/browse/IGNITE-3322
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
 Environment: any
Reporter: Alexandre Boudnik
Assignee: Alexandre Boudnik


It should collect transaction log from all cluster nodes; record both successes 
and failures.



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


Re: IGNITE-2344 merged

2016-06-15 Thread Saikat Maitra
Thank you so much Valentin

Regards,
Saikat


> On 15-Jun-2016, at 4:13 PM, Valentin Kulichenko 
>  wrote:
> 
> Hi Saikat,
> 
> I reviewed and merged changes you made in scope of [1] (Web Session renewal 
> after login).
> 
> Thanks for you contribution!
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-2344 
> 
> 
> -Val



[jira] [Created] (IGNITE-3321) Address possible data corruption in Persistent Store implementations

2016-06-15 Thread Alexandre Boudnik (JIRA)
Alexandre Boudnik created IGNITE-3321:
-

 Summary: Address possible data corruption in Persistent Store 
implementations
 Key: IGNITE-3321
 URL: https://issues.apache.org/jira/browse/IGNITE-3321
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 1.6
 Environment: any
Reporter: Alexandre Boudnik
Assignee: Alexandre Boudnik


When records from partitions on different nodes are committed, each node uses 
its own SQL connection. It is possible that one of DML statements will fail on 
one of the connections, while others have committed successfully.

And we need to make a very hard decision:
- If we ignore fail then we will lose some changes.
- If we throw an exception we will make inconsistent changes.



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


[GitHub] ignite pull request #788: Ignite 3272

2016-06-15 Thread ntikhonov
Github user ntikhonov closed the pull request at:

https://github.com/apache/ignite/pull/788


---
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 #807: Ignite 3233

2016-06-15 Thread alexpaschenko
GitHub user alexpaschenko opened a pull request:

https://github.com/apache/ignite/pull/807

Ignite 3233



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

$ git pull https://github.com/alexpaschenko/ignite ignite-3233

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

https://github.com/apache/ignite/pull/807.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 #807


commit b0575aeb89f807b101101163b577f1658067c146
Author: Alexander Paschenko 
Date:   2016-06-15T15:20:30Z

IGNITE-3233 SpringResource - added resourceClass parameter

commit 4848c24a5d61562778ff8e96b2342f6034663e7a
Author: Alexander Paschenko 
Date:   2016-06-15T15:42:25Z

Removed unused import and added @SuppressWarnings to a test (trivial)

commit 649c314d2d3e480ac637d2c5c76762bffa37dc2a
Author: Alexander Paschenko 
Date:   2016-06-15T15:45:25Z

Changed package-wide import back to per class one (trivial)




---
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-3320) .NET: Configure AffinityFunction without Spring

2016-06-15 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3320:
--

 Summary: .NET: Configure AffinityFunction without Spring
 Key: IGNITE-3320
 URL: https://issues.apache.org/jira/browse/IGNITE-3320
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7






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


[GitHub] ignite pull request #805: Ignite-2767

2016-06-15 Thread vldpyatkov
Github user vldpyatkov closed the pull request at:

https://github.com/apache/ignite/pull/805


---
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 #801: ignite-3209 Waiting for affinity topology in case ...

2016-06-15 Thread agura
Github user agura closed the pull request at:

https://github.com/apache/ignite/pull/801


---
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 #806: IGNITE-3317 .NET: Improve error message when jvm.d...

2016-06-15 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/806

IGNITE-3317 .NET: Improve error message when jvm.dll could not be loaded



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

$ git pull https://github.com/ptupitsyn/ignite ignite-3317

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

https://github.com/apache/ignite/pull/806.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 #806


commit 24a10f028965a198f28c3f87529f40909e782f11
Author: Pavel Tupitsyn 
Date:   2016-06-15T12:44:29Z

IGNITE-3317 .NET: Improve error message when jvm.dll could not be loaded

commit 4a7fab88c283ea905841091e3c6e7f659d037d4b
Author: Pavel Tupitsyn 
Date:   2016-06-15T12:53:05Z

Update error message




---
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 #805: Ignite-2767

2016-06-15 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request:

https://github.com/apache/ignite/pull/805

Ignite-2767



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

$ git pull https://github.com/vldpyatkov/ignite ignite-2767

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

https://github.com/apache/ignite/pull/805.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 #805


commit 9ca308aba2ac9ce5e592dbc223ad6c4bb533a421
Author: vdpyatkov 
Date:   2016-06-14T16:24:27Z

IGNITE-2767
Cont. query remote filter requires to be in client nodes class path

commit b375faea30a91c59b5ca9b2a54d9793a13e19f81
Author: vdpyatkov 
Date:   2016-06-15T10:25:11Z

IGNITE-2767
Cont. query remote filter requires to be in client nodes class path

commit cdde535d65bd3521e8493814b8e6a4ebc937dd53
Author: vdpyatkov 
Date:   2016-06-15T13:51:48Z

IGNITE-2767
Cont. query remote filter requires to be in client nodes class path




---
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: New contributor: Alexander Paschenko

2016-06-15 Thread Denis Magda
Hi Alexander,


Welcome onboard! Just take a look at the ticket and provide your thoughts 
regarding a possible fix. If you need to discuss the fix keep using the dev 
list.

—
Denis
> On Jun 15, 2016, at 12:09 PM, Alexander Paschenko 
>  wrote:
> 
> Hi Ignite Community!
> 
> My name is Alex. I want to contribute to Apache Ignite and am starting
> with the following issue: IGNITE-3233. Any suggestions are welcome.
> 
> Thanks!



Re: New contributor: Andrey Velichko

2016-06-15 Thread Denis Magda
Hi Andrey,

Welcome onboard! Just take a look at the ticket and provide your thoughts 
regarding a possible fix. If you need to discuss the fix keep using the dev 
list.

—
Denis

> On Jun 15, 2016, at 2:59 PM, Andrey Velichko  wrote:
> 
> Hi Ignite Community!
> 
> My name is Andrey. I want to contribute to Apache Ignite and am starting
> with the following issue:IGNITE-2852 
> . Any suggestions are 
> welcome.
> 
> Thanks!
> 



New contributor: Andrey Velichko

2016-06-15 Thread Andrey Velichko

Hi Ignite Community!

My name is Andrey. I want to contribute to Apache Ignite and am starting
with the following issue:IGNITE-2852 
. Any suggestions are 
welcome.

Thanks!



[GitHub] ignite pull request #804: Ignite gg 11237

2016-06-15 Thread avinogradovgg
GitHub user avinogradovgg opened a pull request:

https://github.com/apache/ignite/pull/804

Ignite gg 11237



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-11237

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

https://github.com/apache/ignite/pull/804.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 #804


commit 4de124c41a30e8b4ee825c355686e16228a4390d
Author: nikolay_tikhonov 
Date:   2016-02-16T15:28:51Z

Fixed "IGNITE-2515 Make 'updateCntr' available through 
CacheContinuousQueryEvent public API"

commit 6291c64efab4a2e3d5d9986479bc7a4372fdb553
Author: sboikov 
Date:   2016-02-10T11:07:40Z

ignite-2587 Fixed continuous query notifications in offheap mode and 
BinaryObjectOffheapImpl usage.

commit 72500026cf69429a81dcdcf5ffc81c1db3ee7642
Author: nikolay_tikhonov 
Date:   2016-02-17T08:04:08Z

Fixed "IGNITE-2466 OutOfMemory when ONHEAP_TIERED mode is used".

commit e0eefa50588efcf3b836f93a4b1ca32f92d8973d
Author: sboikov 
Date:   2016-02-17T12:57:27Z

ignite-2669 Changed BinaryUtils.isBinaryType to always convert enums to 
BinaryObject
(cherry picked from commit 8be62f0)

commit 528d6aea65e5d0053649442e704476ee964ca218
Author: sboikov 
Date:   2016-02-17T12:04:30Z

ignite-2669 Changed BinaryUtils.isBinaryType to always convert enums to 
BinaryObject
(cherry picked from commit 8be62f0)

commit 1d3e8cf16eba8d34ee1f7021df6f9ec3bcf5b409
Author: Valentin Kulichenko 
Date:   2016-02-18T02:21:54Z

IGNITE-2249 - Do not deserialize services on client node

commit cffde1b58c56f05fcd4071c56862003afbbc8067
Author: Denis Magda 
Date:   2016-02-18T06:28:10Z

IGNITE-2647: Cache is undeployed even when BinaryMarshaller is used. Fixed.

commit 1a4db916d4b7ba202e22c12ca689337a3c3d1da2
Author: sboikov 
Date:   2016-02-18T06:06:32Z

ignite-2669 Register BinaryEnumObjectImpl as predefined type.
(cherry picked from commit 21f22d3)

commit 9d0f45372c7161bf7f67243cfab0451c293e8ba9
Author: dkarachentsev 
Date:   2016-02-12T13:02:32Z

IGNITE-2430: Fixed binary builder serialization logic for non-standard 
collections.

commit d24ecb1e4409b6dae005394d73f21bdb116a9376
Author: dkarachentsev 
Date:   2016-02-17T13:47:44Z

IGNITE-2641: Now "SELECT [alias].*" is possible. This closes #486.

commit 51efdfaa1d18214af6eb95676968698cce2fdd35
Author: Alexey Goncharuk 
Date:   2016-02-18T15:19:53Z

IGNITE-2610 - Fixed TTL issues with offheap cache memory mode - Fixes #488.

Signed-off-by: Alexey Goncharuk 

commit 2622793b726d05694025fb092dc96b6bbdf3a7e8
Author: Denis Magda 
Date:   2016-02-19T07:19:06Z

IGNITE-2648: DataStreamer doesn't stream BinaryObjects created with 
BinaryBuilder

commit 0bdd56f9764a18b3b9988e7e7681ade122055f6f
Author: Denis Magda 
Date:   2016-02-19T07:22:35Z

Merge branch 'ignite-1.5.7' of 
https://git-wip-us.apache.org/repos/asf/ignite into ignite-1.5.7

commit 66bc778da0a23d0fe5fd5630efb203109c4a40b1
Author: Ilya Lantukh 
Date:   2016-02-19T13:22:23Z

Minor changes to GridCacheDrManager interface to better propagate topology 
version.

commit 03e5d9c6efa4ab5506c51d02c1d5ec88147bd315
Author: Anton Vinogradov 
Date:   2016-02-19T16:05:33Z

IGNITE-2683
(cherry picked from commit 2146631)

commit 80dd057a03374cc10280d0e9707ecbf6b609e880
Author: Anton Vinogradov 
Date:   2016-02-20T11:30:29Z

IGNITE-2648

commit 3172b4d7f022a1bb6f54f2daa9e62fbb432e7647
Author: sboikov 
Date:   2016-02-20T11:33:45Z

IGNITE-2683 In indexing kernal context can be null in tests.

commit b8beea91eede6bb89b005aa7e945112d4db993c6
Author: sboikov 
Date:   2016-02-20T11:34:12Z

Merge remote-tracking branch 'origin/ignite-1.5.7' into ignite-1.5.7

commit 409f52571254e5abbb7714f50eb4ce809736d3b2
Author: Anton Vinogradov 
Date:   2016-02-20T11:37:35Z

IGNITE-2683 fixes

commit feab7130bc2b166527c80e8e55f20575047e4fef
Author: Anton Vinogradov 
Date:   2016-02-20T11:37:50Z

Merge remote-tracking branch 'origin/ignite-1.5.7' into ignite-1.5.7

commit 390cd639eafe975a1191aac00d3c9c96bd98274f
Author: Anton Vinogradov 
Date:   2016-02-20T12:12:11Z

IGNITE-2683 fixes

commit 473cff0aed4aac37fd905aed05e0cc9be3ebf93e
Author: Anton Vinogradov 
Date:   2016-02-20T13:20:18Z

IGNITE-2683 fixes

commit 

IGNITE-2344 merged

2016-06-15 Thread Valentin Kulichenko
Hi Saikat,

I reviewed and merged changes you made in scope of [1] (Web Session renewal
after login).

Thanks for you contribution!

[1] https://issues.apache.org/jira/browse/IGNITE-2344

-Val


[GitHub] ignite pull request #803: IGNITE-3311 .NET: Include configuration schema in ...

2016-06-15 Thread ptupitsyn
GitHub user ptupitsyn opened a pull request:

https://github.com/apache/ignite/pull/803

IGNITE-3311 .NET: Include configuration schema in NuGet package



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

$ git pull https://github.com/ptupitsyn/ignite ignite-3311

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

https://github.com/apache/ignite/pull/803.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 #803


commit 08ad3db9ee72c84f16927552d5e1aa5d2102e0e5
Author: Pavel Tupitsyn 
Date:   2016-06-15T09:44:45Z

IGNITE-3311 .NET: Include configuration schema in NuGet package

commit 0276daafe0ac3de303c112e0a10cb097b0d2e76d
Author: Pavel Tupitsyn 
Date:   2016-06-15T09:50:07Z

wip

commit a210ea10422e87bb5345e3e8a5a9264493913d7d
Author: Pavel Tupitsyn 
Date:   2016-06-15T09:54:43Z

wip tests

commit a2f53e7a979142dd585a440eea247838c83432f3
Author: Pavel Tupitsyn 
Date:   2016-06-15T09:57:08Z

wip tests




---
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 #780: Ignite 2344 WebSessionFilter doesn't support sessi...

2016-06-15 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/780


---
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-3319) Web Console: speed up bundle rebuild and watch

2016-06-15 Thread Maxim Afanasiev (JIRA)
Maxim Afanasiev created IGNITE-3319:
---

 Summary: Web Console: speed up bundle rebuild and watch
 Key: IGNITE-3319
 URL: https://issues.apache.org/jira/browse/IGNITE-3319
 Project: Ignite
  Issue Type: Bug
  Components: UI
Reporter: Maxim Afanasiev
Assignee: Maxim Afanasiev


Try to use WebPack instead of JSPM.



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


Re: IgniteRDD.keepBinary()

2016-06-15 Thread Alexey Goncharuk
​Val,

Looks good to me, can't wait to see it in master :)


[jira] [Created] (IGNITE-3317) .NET: Improve error message when jvm.dll could not be loaded

2016-06-15 Thread Pavel Tupitsyn (JIRA)
Pavel Tupitsyn created IGNITE-3317:
--

 Summary: .NET: Improve error message when jvm.dll could not be 
loaded
 Key: IGNITE-3317
 URL: https://issues.apache.org/jira/browse/IGNITE-3317
 Project: Ignite
  Issue Type: Improvement
  Components: community, platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.7


User got an unhelpful error message:
{code}
Failed to load jvm.dll:
[option=JAVA_HOME, path=C:\Program 
Files\Java\jdk1.8.0_92\jre\bin\server\jvm.dll, errorCode=193]
[option=JAVA_HOME, path=C:\Program 
Files\Java\jdk1.8.0_92\jre\bin\default\jvm.dll, errorCode=126]
{code}

Which turned out to be x64/x86 issue. 
Provide more details in such case: what happened and how to fix this.



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