Re: Handling collections in BinaryMarshaller

[Vladimir Ozerov]

Dmitriy,
Correct. This is what I meant.

On Tue, Dec 8, 2015 at 10:26 PM, Dmitriy Setrakyan 
wrote:

> Vladimir,
>
> I believe the default collections in Java and .NET should be supported out
> of the box. Moreover, if we know the collection type, e.g. HashMap, we can
> always provide a more efficient way of serializing it ourselves, in the
> Binary marshaller.
>
> Is this something you had in mind, or were you proposing something
> different.
>
> D.
>
> On Tue, Dec 8, 2015 at 6:29 AM, Vladimir Ozerov 
> wrote:
>
> > Alex,
> >
> > What interface do you mean? If user has collection field in class and
> > explicitly call BinaryWriter.writeCollection(), we can leave current
> > interoperability support - it is not a problem.
> > As per your second point - user could pass collections e.g. as argument
> to
> > Java task started from .NET. This is where we will loose interoperabiltiy
> > and will force user to create some wrappers. But these are very specific
> > use cases.
> >
> > BTW, proposed solution is almost exactly how we work with collections in
> > .NET.
> >
> > On Tue, Dec 8, 2015 at 4:57 PM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com
> > > wrote:
> >
> > > I like the idea, however it has obvious downsides. First, if a user
> class
> > > contains a collection, we force user to implement additional interface,
> > > even if the collection is a simple ArrayList. Second, I do not see how
> > this
> > > plain collection can be the value for the cache - user will always need
> > to
> > > write a wrapper/containing class around it.
> > >
> > > I think we should provide minimum support for basic types - HashMap,
> > > LinkedHashMap, ArrayList and treat other classes the way Vladimir
> > > described.
> > >
> >
>

[GitHub] ignite pull request: Ignite 2064 2

[avinogradovgg]

Github user avinogradovgg closed the pull request at:

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


---
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-1864 Custom TX manager configuration

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
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: Idiomatic way of configuring caches on client

[Yakov Zhdanov]

I think it is very good idea to generate client node config as well and it
seems that console should provide ability to configure near cache (e.g.
start size and eviction policy) or turn it off completely.

--Yakov

2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov :

> I'm working on Ignite Web Console.
> And this utility is generating XML and java code with cluster
> configuration.
>
> For server-side I generate XML and java code that describe caches.
>
> But should I do the same when generating client node configuration?
>
> I think that I should only generate NearCacheConfiguration in case
> of client node
> and do not generate CacheConfiguration in XML and java.
>
> Also, it is a good idea to generate NearCacheConfiguration for each cache
> by default?
> Or better to give a choice of caches?
>
>
> Thoughts?
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[jira] [Created] (IGNITE-2118) CacheBinaryAutoStore Example output depend on number of runs

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2118:
-

 Summary: CacheBinaryAutoStore Example output depend on number of 
runs
 Key: IGNITE-2118
 URL: https://issues.apache.org/jira/browse/IGNITE-2118
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
 Fix For: 1.5


1. Start H2 server
2. Start ignite node
3. Start CacheBinaryAutoStore a few times. Each time "Loaded cache entries" 
incremented by one.

{noformat}
>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5980051555829975513, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5980051555829975513, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 7
{noformat}

{noformat}

>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5677607654468819582, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5677607654468819582, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 8
{noformat}

{noformat}
>>> Cache auto store example started.
Read value: null
Overwrote old value: null
Read value: Person [firstName=Isaac, lastName=Newton, id=5702655301354862064, 
orgId=null, resume=null, salary=0.0]
Read value after commit: Person [firstName=Isaac, lastName=Newton, 
id=5702655301354862064, orgId=null, resume=null, salary=0.0]
>>> --
>>> Load data to cache from DB with custom SQL...
Loaded cache entries: 3
>>> Load ALL data to cache from DB...
Loaded cache entries: 9
{noformat}





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

[jira] [Created] (IGNITE-2115) Improve "peerClassLoadingEnabled=true" handling in Hadoop module.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2115:
---

 Summary: Improve "peerClassLoadingEnabled=true" handling in Hadoop 
module.
 Key: IGNITE-2115
 URL: https://issues.apache.org/jira/browse/IGNITE-2115
 Project: Ignite
  Issue Type: Task
  Components: hadoop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
 Fix For: 1.6


We have very subtle logic for Hadoop module loading. Even if it is in 
classpath, if "peerClassloadingEnabledFlag" is set, module is not loaded. No 
warning or errors appear. 

We should:
1) Print warning if this flag prevents loading of Hadoop module;
2) Remove "peerClassLoadingEnabled=true" from IGFS example.



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

[GitHub] ignite pull request: IGNITE-2111 .Net: Create a build script

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2111 .Net: Create a build script



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

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

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

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


commit 163cdac9d035e5fe73d23b3b2eb52f102b8d881b
Author: Pavel Tupitsyn 
Date:   2015-12-08T15:43:28Z

Include XML documentation

commit a5b8cd8f9e7ffd13d68c8d168b869100fca2c9bd
Author: Pavel Tupitsyn 
Date:   2015-12-08T16:30:48Z

Update examples HintPaths

commit 665dd80b0ab15c30c38d5018870d321b0846af6d
Author: Pavel Tupitsyn 
Date:   2015-12-08T16:41:24Z

Fix HintPath conditions

commit c2e40f737da8b80b3c8d13424c0e96f23bf9966b
Author: Pavel Tupitsyn 
Date:   2015-12-09T09:19:26Z

Fix HintPath typo

commit f12c7cab4a2915351c6f1bd595f35ed91cdff665
Author: Pavel Tupitsyn 
Date:   2015-12-09T09:54:54Z

wip dxg

commit 90ff07f8db21f84b07c14aeab7ef5285ddd34da3
Author: Pavel Tupitsyn 
Date:   2015-12-09T10:01:06Z

wip dxg

commit 8abf95aa50d1daf2c3738043224c4defca93affc
Author: Pavel Tupitsyn 
Date:   2015-12-09T10:26:56Z

wip dxg

commit 4767eb210e35cb8e0f0c818ff7598d580667ab73
Author: Pavel Tupitsyn 
Date:   2015-12-09T11:51:52Z

wip dxg

commit 57159066bd10714222e0647ec4e670da2d1ff40e
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:08:35Z

wip dxg

commit 2f6136127bd0d3faf1fd9bd86770a448b23e44dc
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:12:14Z

Update release fabric

commit c7922f6014362513f531299620321a4c785a5103
Author: Pavel Tupitsyn 
Date:   2015-12-09T12:14:59Z

cleanup




---
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-2116) ignite-osgi-karaf has only readme and license files

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-2116:
-

 Summary: ignite-osgi-karaf has only readme and license files
 Key: IGNITE-2116
 URL: https://issues.apache.org/jira/browse/IGNITE-2116
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.5
Reporter: Sergey Kozlov
Assignee: Yakov Zhdanov
Priority: Critical
 Fix For: 1.5


{noformat}
C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
...
08.12.2015  12:34  .
08.12.2015  12:34  ..
08.12.2015  12:34  licenses
08.12.2015  12:34   735 README.txt
...
C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir 
licenses
...
08.12.2015  12:34  .
08.12.2015  12:34  ..
08.12.2015  12:3411 358 apache-2.0.txt
08.12.2015  12:34   289 ignite-osgi-karaf-licenses.txt
...
{noformat}



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

Re: Idiomatic way of configuring caches on client

[Alexey Goncharuk]

I see nothing wrong with generating a server config for a client node. This
may be used in a case when server nodes are started with plain empty config
and clients are deploying caches to the grid.

[jira] [Created] (IGNITE-2122) .NET: Add generic Read/WriteCollection and Read/WriteDictionary methods.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2122:
---

 Summary: .NET: Add generic Read/WriteCollection and 
Read/WriteDictionary methods.
 Key: IGNITE-2122
 URL: https://issues.apache.org/jira/browse/IGNITE-2122
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






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

[jira] [Created] (IGNITE-2121) .NET: Port correct collections handling logic.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2121:
---

 Summary: .NET: Port correct collections handling logic.
 Key: IGNITE-2121
 URL: https://issues.apache.org/jira/browse/IGNITE-2121
 Project: Ignite
  Issue Type: Sub-task
  Components: interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






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

[GitHub] ignite pull request: Ignite 2064 3

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

Ignite 2064 3



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

$ git pull https://github.com/avinogradovgg/ignite ignite-2064-3

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

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


commit d5791837890a70e1777b86aab281245701afe1eb
Author: sboikov 
Date:   2015-12-08T09:42:25Z

ignite-1.5 Fixed hang on client reconnect (should not do blocking calls 
from reconnect callback)

commit 5cd0039a535b4c2ea7434d4b085c9e18f28c930d
Author: sboikov 
Date:   2015-12-08T10:12:24Z

ignite-1692 Changed test initialization logic to remove race confition that 
caused ClusterTopologyServerNotFoundException

commit 322a85a359e0fc2c56f5c3aa38fc48a92e553289
Author: S.Vladykin 
Date:   2015-12-08T10:17:36Z

ignite-1.5 - MessageCollection + marshalling issue test

commit c292748013acfcbf6b3752183a34bb26de16c1f4
Author: S.Vladykin 
Date:   2015-12-08T10:18:30Z

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

commit 67ebd02c9a58ef2d835e55e4aa6efdcec6d53b8c
Author: Alexey Goncharuk 
Date:   2015-12-08T12:09:10Z

Ignite-1.5 - Added missing serialVersionUID to fix the build.

commit 8ca163bd0f06cc832df126733dbbe50cea35c2ac
Author: Anton Vinogradov 
Date:   2015-12-08T12:46:10Z

IGNITE-2064 More test fixes

commit efe632b18e760f699bedee906050f66eabadb077
Author: Pavel Tupitsyn 
Date:   2015-12-08T12:59:23Z

IGNITE-2026: .NET: Fixed stack overflow caused by incorrect unboxing of 
value types.

commit 3a340034056f5da0ca00ed88e128b59cc28381d2
Author: ashutak 
Date:   2015-12-08T13:02:36Z

Fixed race in IgniteTransactionalWriteInvokeBenchmark test.

commit 568f910f11472e6ab533c3f1cef6f197456e006f
Author: Pavel Tupitsyn 
Date:   2015-12-08T13:35:51Z

IGNITE-1694 : .NET: Use DllImport instead of delegates in P/Invoke.

commit 0e81a3973cccfe6d912e073cd9f44db5a5c46d79
Author: vozerov-gridgain 
Date:   2015-12-08T13:36:12Z

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

commit c30def8f049bddb4ec272528326f84bf90a1399b
Author: Anton Vinogradov 
Date:   2015-12-08T13:48:58Z

2064 Issue url fix

commit 3baf4d163c6edafa7367ece7901ad1efe695a8d4
Author: sboikov 
Date:   2015-12-08T14:30:14Z

ignite-1.5 Cache map refactoring. This closes #279.

commit bdbe4068b3851f7a412935acb3e36860cd08efa9
Author: Raul Kripalani 
Date:   2015-12-08T20:04:36Z

Fix OSGi test.

(@ProbeBuilder applies to all test classes when run from a suite).

commit 69047243bb1de980647711a59573bf44e69761eb
Author: sboikov 
Date:   2015-12-09T06:27:23Z

ignite-2030  Fixed issue with JAVA_HOME containing parenthesis

commit 0adee3ae09a86334375b521871539b086215ba92
Author: sboikov 
Date:   2015-12-09T06:56:53Z

ignite-10 Fix ignite instance [de]serialization

commit 5ea19a4549eb9df619bad9e8a86b844a5db2ca1f
Author: ashutak 
Date:   2015-12-09T09:02:57Z

IGNITE-1864: Transaction manager factory instead of Transaction manager 
Lookup

commit d0786551aef92f77cbb23097de18745399d00d69
Author: Anton Vinogradov 
Date:   2015-12-08T13:39:36Z

IGNITE-2064 Fixed Usage of Optimize classloader

commit afbb0dc0c1323b1b24d1a6f4f46fc78d255c98a4
Author: Anton Vinogradov 
Date:   2015-12-09T09:59:51Z

IGNITE-2064 Fixed Usage of Optimize classloader test coverage

commit 6e7292613c9d8926532f3b9fe6b89b6dd3bf0fb9
Author: Anton Vinogradov 
Date:   2015-12-09T14:33:59Z

IGNITE-2064 Fixed deserialize. Added more 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.
---

Re: Idiomatic way of configuring caches on client

[Alexey Kuznetsov]

Yakov, Ignite console has UI (on Summary page) for near cache configuration
with optional eviction policy.

On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov  wrote:

> I think it is very good idea to generate client node config as well and it
> seems that console should provide ability to configure near cache (e.g.
> start size and eviction policy) or turn it off completely.
>
> --Yakov
>
> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov :
>
> > I'm working on Ignite Web Console.
> > And this utility is generating XML and java code with cluster
> > configuration.
> >
> > For server-side I generate XML and java code that describe caches.
> >
> > But should I do the same when generating client node configuration?
> >
> > I think that I should only generate NearCacheConfiguration in case
> > of client node
> > and do not generate CacheConfiguration in XML and java.
> >
> > Also, it is a good idea to generate NearCacheConfiguration for each cache
> > by default?
> > Or better to give a choice of caches?
> >
> >
> > Thoughts?
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Idiomatic way of configuring caches on client

[Alexey Kuznetsov]

Alex,

Thanks for your suggestions. We will generate server cache configs + client
near cache configs.

On Wed, Dec 9, 2015 at 9:06 PM, Alexey Kuznetsov 
wrote:

> Yakov, Ignite console has UI (on Summary page) for near cache
> configuration with optional eviction policy.
>
> On Wed, Dec 9, 2015 at 7:34 PM, Yakov Zhdanov  wrote:
>
>> I think it is very good idea to generate client node config as well and it
>> seems that console should provide ability to configure near cache (e.g.
>> start size and eviction policy) or turn it off completely.
>>
>> --Yakov
>>
>> 2015-12-09 10:07 GMT+03:00 Alexey Kuznetsov :
>>
>> > I'm working on Ignite Web Console.
>> > And this utility is generating XML and java code with cluster
>> > configuration.
>> >
>> > For server-side I generate XML and java code that describe caches.
>> >
>> > But should I do the same when generating client node configuration?
>> >
>> > I think that I should only generate NearCacheConfiguration in case
>> > of client node
>> > and do not generate CacheConfiguration in XML and java.
>> >
>> > Also, it is a good idea to generate NearCacheConfiguration for each
>> cache
>> > by default?
>> > Or better to give a choice of caches?
>> >
>> >
>> > Thoughts?
>> >
>> > --
>> > Alexey Kuznetsov
>> > GridGain Systems
>> > www.gridgain.com
>> >
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-2119) Tasks can get stuck in case of communication error

[Avihai Berkovitz (JIRA)]

Avihai Berkovitz created IGNITE-2119:


 Summary: Tasks can get stuck in case of communication error
 Key: IGNITE-2119
 URL: https://issues.apache.org/jira/browse/IGNITE-2119
 Project: Ignite
  Issue Type: Bug
Affects Versions: ignite-1.4
 Environment: Ubuntu 12.04 64 bit
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
Ignite 1.4.0
Reporter: Avihai Berkovitz


After running a cluster of 20 nodes for a couple of hours under heavy load 
(hundreds of tasks per minute) we have a problem with one of the nodes. The 
public thread pool is completely full, and all the threads are stuck here:
{noformat}
 - sun.misc.Unsafe.park(boolean, long) @bci=0 (Compiled frame; information may 
be imprecise)
 - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, 
line=175 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt() 
@bci=1, line=836 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(int)
 @bci=72, line=997 (Compiled frame)
 - 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(int)
 @bci=24, line=1304 (Compiled frame)
 - org.apache.ignite.internal.util.future.GridFutureAdapter.get0(boolean) 
@bci=23, line=157 (Compiled frame)
 - org.apache.ignite.internal.util.future.GridFutureAdapter.get() @bci=5, 
line=115 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(org.apache.ignite.cluster.ClusterNode)
 @bci=413, line=2017 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.plugin.extensions.communication.Message, 
org.apache.ignite.lang.IgniteInClosure) @bci=185, line=1914 (Compiled frame)
 - 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.plugin.extensions.communication.Message, 
org.apache.ignite.lang.IgniteInClosure) @bci=4, line=1880 (Compiled frame)
 - 
org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
 java.lang.Object, int, 
org.apache.ignite.plugin.extensions.communication.Message, byte, boolean, long, 
boolean, org.apache.ignite.lang.IgniteInClosure) @bci=227, line=1066 (Compiled 
frame)
 - 
org.apache.ignite.internal.managers.communication.GridIoManager.send(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.internal.GridTopic, 
org.apache.ignite.plugin.extensions.communication.Message, byte) @bci=14, 
line=1214 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(org.apache.ignite.cluster.ClusterNode,
 org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) @bci=123, 
line=652 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(java.util.UUID,
 org.apache.ignite.internal.processors.cache.GridCacheMessage, byte) @bci=64, 
line=801 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(java.util.UUID,
 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
 @bci=108, line=474 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.access$1200(org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture,
 java.util.UUID, 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest)
 @bci=3, line=73 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.map(org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
 @bci=560, line=880 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapOnTopology()
 @bci=253, line=422 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.map()
 @bci=60, line=291 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
 @bci=4, line=844 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$14.apply()
 @bci=1, line=842 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.asyncOp(org.apache.ignite.internal.util.typedef.CO)
 @bci=86, line=648 (Compiled frame)
 - 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsync0(java.util.Map,
 java.util.Map, java.lang.Object[], java.util.Map, java.util.Map, 

[jira] [Created] (IGNITE-2120) Rename Binarylizable -> Binarizable

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2120:
---

 Summary: Rename Binarylizable -> Binarizable
 Key: IGNITE-2120
 URL: https://issues.apache.org/jira/browse/IGNITE-2120
 Project: Ignite
  Issue Type: Task
  Components: general, interop
Affects Versions: ignite-1.4
Reporter: Vladimir Ozerov
Priority: Critical
 Fix For: 1.5






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

[GitHub] ignite pull request: IGNITE-1993 remove non-standard SQL clause so...

[westbury]

GitHub user westbury opened a pull request:

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

IGNITE-1993 remove non-standard SQL clause so table for JDBC discovery…

Note that the tests do not run locally.  They fail because portable/test1 
and portable/test2 are not available (see IGNITE-1462).  However I note that 
the instructions at 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute instruct 
to use -DskipTests so I did that.

This pull request supercedes the patch as per Denis Magda's comment.

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

$ git pull https://github.com/westbury/ignite ignite-1993

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

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


commit e8088e92e409eff80c6622cda55201c6719abe4e
Author: Nigel Westbury 
Date:   2015-12-09T14:49:36Z

IGNITE1993 remove non-standard SQL clause so table for JDBC discovery works 
in Oracle




---
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-2123) Need to add EntryProcessorExample to cache examples

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-2123:
-

 Summary: Need to add EntryProcessorExample to cache examples
 Key: IGNITE-2123
 URL: https://issues.apache.org/jira/browse/IGNITE-2123
 Project: Ignite
  Issue Type: Task
Reporter: Yakov Zhdanov


One can take {{CacheAffinityExample}} as an example.

# call entry processors in a loop, if entry is null then create it in entry 
processor
# do gets in a loop and show that entries are in cache
# call entry processors in a loop and modify existing entries
# do gets in a loop and show the results of modification



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

[GitHub] ignite pull request: IGNITE-2012 Add support for ConcurrentLinkedQ...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2012 Add support for ConcurrentLinkedQueue type in .NET/C++



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

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

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

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


commit b9f14ad2f173677d430b293224a3785d68b4458c
Author: Pavel Tupitsyn 
Date:   2015-12-09T16:23:35Z

IGNITE-2012 Add support for ConcurrentLinkedQueue type in .NET/C++




---
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-2100 - Fixes for Externalizable classe...

[agoncharuk]

GitHub user agoncharuk opened a pull request:

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

IGNITE-2100 - Fixes for Externalizable classes and queries.



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

$ git pull https://github.com/agoncharuk/ignite ignite-2100

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

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


commit e84b268f8c3ff85a8e2af8c763b10b41a3659a18
Author: Alexey Goncharuk 
Date:   2015-12-09T17:29:12Z

IGNITE-2100 - Fixes for Externalizable classes and queries.




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

Accidental deserialization of BinaryObject key on a remote node

[Denis Magda]

Igniters,

I've faced with the following issue today
https://issues.apache.org/jira/browse/IGNITE-2124

Could someone who is working on BinaryMarshaller presently investigate 
and fix the bug before 1.5 GA release?


--
Denis

[jira] [Created] (IGNITE-2124) Deserialization of a BinaryObject key on a remote node

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2124:
---

 Summary: Deserialization of a BinaryObject key on a remote node
 Key: IGNITE-2124
 URL: https://issues.apache.org/jira/browse/IGNITE-2124
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5
 Environment: Windows 7
Reporter: Denis Magda
Priority: Blocker
 Fix For: 1.5


BinaryObject key gets deserialized on a remote node. In my understanding this 
mustn't happen when {{BinaryMarshaller}} is enabled.

Steps to reproduce:
- start a remote node using ignite.bat/sh;
- launch {{CacheClientBinaryQueryExample}};

The example will fail with the following stack trace:

{noformat}
Exception in thread "main" org.apache.ignite.cache.CachePartialUpdateException: 
Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
organizationId=2]]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1620)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1806)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1078)
at 
org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.populateCache(CacheClientBinaryQueryExample.java:301)
at 
org.apache.ignite.examples.binary.datagrid.CacheClientBinaryQueryExample.main(CacheClientBinaryQueryExample.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)
Caused by: class 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: [EmployeeKey [id=4, 
organizationId=2]]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1189)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:658)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:352)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2617)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:127)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:262)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:260)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:579)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:277)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:201)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
update keys on primary node.
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:368)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1384)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1193)
at 

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

Yup, much better now! Thanks man!

On Wed, Dec 09, 2015 at 07:54PM, Andrey Gura wrote:
> Configuration sample added.
> 
> On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> wrote:
> 
> > Thanks Andrey!
> >
> > In my view, we should also provide a sample XML configuration file,
> > especially given that we refer to it in the sample URL.
> >
> > D.
> >
> > On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura  wrote:
> >
> > > Done. I hope that is more clear now.
> > >
> > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan  > >
> > > wrote:
> > >
> > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > wrote:
> > > >
> > > > > Cos,
> > > > >
> > > > >  sepcifies configuration file for Ignite client node that
> > > > will
> > > > > be started during connection establishing by JDBC driver. So this
> > file
> > > > > should be available for JDBC driver client.
> > > > >
> > > >
> > > > Andrey, should this be documented here?
> > > > https://apacheignite.readme.io/docs/jdbc-driver
> > > >
> > > > D.
> > > >
> > > >
> > > > >
> > > > > On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik 
> > > > wrote:
> > > > >
> > > > > > Thanks Andrey!
> > > > > >
> > > > > > Still a bit unclear: the doc says
> > > > > > " is required and represents any valid URL which points
> > > to
> > > > > > Ignite configuration file"
> > > > > >
> > > > > > So, that's server side URL then, something like
> > > > > > jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
> > > > > >
> > > > > > assuming that server nodes have said configuration under
> > > > > > /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a bit
> > > > > dense,
> > > > > > or
> > > > > > the doc isn't written to a layman
> > > > > >
> > > > > > Thanks in advance!
> > > > > >   Cos
> > > > > >
> > > > > > On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > > > > > > Cos,
> > > > > > >
> > > > > > > JDBC driver was reworked in order to use Ignite client node
> > instead
> > > > of
> > > > > > > Ignite Java client. It gives better performance. So now JDBC
> > dirver
> > > > > uses
> > > > > > > Ignite xml configuration file using jdbc:ignite:cfg protocol. See
> > > > > > > documentation for version 1.4
> > > > > > > https://apacheignite.readme.io/v1.4/docs/jdbc-driver
> > > > > > >
> > > > > > > At the same time we still support old version of JDBC driver that
> > > > uses
> > > > > > > jdbc:ignite protocol. See documentation for version 1.3
> > > > > > > https://apacheignite.readme.io/v1.3/docs/jdbc-driver
> > > > > > >
> > > > > > > Thus you can control used JDBC driver type (new or old) just with
> > > > > choosen
> > > > > > > protocol.
> > > > > > >
> > > > > > > Please, note, that old JDBC driver is deprecated and can be
> > removed
> > > > > from
> > > > > > > future releases.
> > > > > > >
> > > > > > > On Mon, Dec 7, 2015 at 6:41 AM, Konstantin Boudnik <
> > c...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Guys, I am looking into [1] and see a reference to
> > > > > > > >
> > > > > > > > ignite.jdbc.url = "jdbc:ignite:cfg://"
> > > > > > > >
> > > > > > > > So, I am curious if there's a way to fetch node's config via
> > JDBC
> > > > > > somehow?
> > > > > > > > Or
> > > > > > > > this is just a simple error in the doc, which needs to be
> > fixed?
> > > > > > > >
> > > > > > > > Would appreciate the insight from the team. Thanks!
> > > > > > > >   Cos
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Andrey Gura
> > > > > > > GridGain Systems, Inc.
> > > > > > > www.gridgain.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Andrey Gura
> > > > > GridGain Systems, Inc.
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Andrey Gura
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
> 
> 
> 
> -- 
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com


signature.asc
Description: Digital signature

Re: EA versioning

[Konstantin Boudnik]

Yup! It will remove any uncertainties about version sequence. And if anything
extra needs to be said about the quality of the release, it should be
communicated via documentation, README, releaseNotes, or else.

Thanks
  Cos

On Tue, Dec 08, 2015 at 04:56PM, Sergi Vladykin wrote:
> Cos,
> 
> I think you are right, probably we have to release 1.5.0-b1 then stable
> bug-fix versions will be 1.5.1, 1.5.2...
> And then next release from master should be 1.6.0. Yes, this should work
> and then we will not need
> *final *qualifier.
> 
> Sergi
> 
> 
> 2015-12-07 7:23 GMT+03:00 Konstantin Boudnik :
> 
> > Oh, and not to say - JIRA would have to have a corresponding versions. Say
> > right now I see only 1.5 in JIRA and it has 161 unresolved bugs. However,
> > the
> > -b1 release is already voted for and is almost official.
> >
> > Cos
> >
> > On Sun, Dec 06, 2015 at 03:11PM, Konstantin Boudnik wrote:
> > > On Sun, Dec 06, 2015 at 11:30AM, Sergi Vladykin wrote:
> > > > Cos and Brane,
> > > >
> > > > This issue arised not from our feeling of beautiful, but from practical
> > > > reasons,
> > > > namely we need to conform existing Maven and OSGi version models at the
> > > > same time.
> > > >
> > > > We did not invent Maven or OSGi, but if we want to play with them well,
> > > > we have to keep in mind their own quirks and bad design decisions,
> > > > when choosing how our versions will look like.
> > >
> > > Very true. However, both Maven and OSGi are supporting normal semver
> > schema,
> > > so the argument doesn't apply ;)
> > >
> > > > Cos,
> > > >
> > > > JDK and Linux kernel are bad examples here exactly because
> > > > they were free to choose any good or bad versioning they want,
> > > > we are not that free.
> > >
> > > We are free to stick to simver and don't make convoluted choices, that
> > will
> > > confuse the hell out of the users. I am seen 1.5.0-b1 getting released
> > and I
> > > already have no idea if it is better than 1.5.0 or worst. If the latter -
> > > where's 1.5.0 then?
> > >
> > > > Could you please clarify what exactly happened with HBase?
> > > > And why do you think we will have the same problems?
> > >
> > > Hbase used to have 0.98.16.1-hadoop2 and 0.98.16.1-hadoop1 classifiers to
> > > distinguish between different versions of HDFS base. Considering that
> > maven
> > > classifiers are designed to differentiate between _types_ of artifacts,
> > not
> > > the platforms, hooking up to the hbase artifacts from different
> > dependency
> > > management systems were a royal PITA.
> > >
> > > We'll have the same problem exactly because these are arbitrary choices
> > and have
> > > no similarities with anything else out there. The most effective
> > engineering
> > > principal is KISS: anything that goes against it will have a higher
> > friction
> > > with the users. Meaning more disoriented emails on the user@ list, more
> > > frustration and incorrectly filed bug reports, reflecting in a lower
> > > traction with future contributors.
> > >
> > > Cheers,
> > >   Cos
> > >
> > > > 2015-12-06 4:24 GMT+03:00 Konstantin Boudnik :
> > > >
> > > > > On Tue, Dec 01, 2015 at 07:18PM, Raul Kripalani wrote:
> > > > > > On Tue, Dec 1, 2015 at 7:15 PM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Raul, as an OSGI expert, do you confirm?
> > > > > > >
> > > > > >
> > > > > > Yep, it was my proposal only to add "-final". Just to be clear,
> > this is a
> > > > > > Maven qualifier. The maven-bundle-plugin will translate the hyphen
> > to a
> > > > > > dot, for compatibility with OSGi.
> > > > >
> > > > > For the die-hard fans of "-lksfdiuye" classifiers in Maven
> > artifacts, I'd
> > > > > suggest to check how well it has played for HBase. Hadoop been there
> > as
> > > > > well -
> > > > > they still are fighting the consequences of once thought to be a neat
> > > > > "-alpha"
> > > > > idea. Seriously guys, this is gonna be mess, confusing the hell out
> > of
> > > > > everybody.
> > > > >
> > > > > Cos
> > > > >
> > > > > > *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
> > > > >
> >
> >
> >


signature.asc
Description: Digital signature

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

Thanks Andrey!

Why are we enabling peer class loading for the JDBC driver in your example?
To my knowledge, we are not deploying any classes, are we? Also, the TCP
discovery with multicast is the default, so no reason to specify it either.

It seems that the only properly required is clientMode=true, no?

D.

On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura  wrote:

> Configuration sample added.
>
> On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> wrote:
>
> > Thanks Andrey!
> >
> > In my view, we should also provide a sample XML configuration file,
> > especially given that we refer to it in the sample URL.
> >
> > D.
> >
> > On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura  wrote:
> >
> > > Done. I hope that is more clear now.
> > >
> > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > > wrote:
> > >
> > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > wrote:
> > > >
> > > > > Cos,
> > > > >
> > > > >  sepcifies configuration file for Ignite client node
> that
> > > > will
> > > > > be started during connection establishing by JDBC driver. So this
> > file
> > > > > should be available for JDBC driver client.
> > > > >
> > > >
> > > > Andrey, should this be documented here?
> > > > https://apacheignite.readme.io/docs/jdbc-driver
> > > >
> > > > D.
> > > >
> > > >
> > > > >
> > > > > On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik  >
> > > > wrote:
> > > > >
> > > > > > Thanks Andrey!
> > > > > >
> > > > > > Still a bit unclear: the doc says
> > > > > > " is required and represents any valid URL which
> points
> > > to
> > > > > > Ignite configuration file"
> > > > > >
> > > > > > So, that's server side URL then, something like
> > > > > > jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
> > > > > >
> > > > > > assuming that server nodes have said configuration under
> > > > > > /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a
> bit
> > > > > dense,
> > > > > > or
> > > > > > the doc isn't written to a layman
> > > > > >
> > > > > > Thanks in advance!
> > > > > >   Cos
> > > > > >
> > > > > > On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > > > > > > Cos,
> > > > > > >
> > > > > > > JDBC driver was reworked in order to use Ignite client node
> > instead
> > > > of
> > > > > > > Ignite Java client. It gives better performance. So now JDBC
> > dirver
> > > > > uses
> > > > > > > Ignite xml configuration file using jdbc:ignite:cfg protocol.
> See
> > > > > > > documentation for version 1.4
> > > > > > > https://apacheignite.readme.io/v1.4/docs/jdbc-driver
> > > > > > >
> > > > > > > At the same time we still support old version of JDBC driver
> that
> > > > uses
> > > > > > > jdbc:ignite protocol. See documentation for version 1.3
> > > > > > > https://apacheignite.readme.io/v1.3/docs/jdbc-driver
> > > > > > >
> > > > > > > Thus you can control used JDBC driver type (new or old) just
> with
> > > > > choosen
> > > > > > > protocol.
> > > > > > >
> > > > > > > Please, note, that old JDBC driver is deprecated and can be
> > removed
> > > > > from
> > > > > > > future releases.
> > > > > > >
> > > > > > > On Mon, Dec 7, 2015 at 6:41 AM, Konstantin Boudnik <
> > c...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Guys, I am looking into [1] and see a reference to
> > > > > > > >
> > > > > > > > ignite.jdbc.url = "jdbc:ignite:cfg://"
> > > > > > > >
> > > > > > > > So, I am curious if there's a way to fetch node's config via
> > JDBC
> > > > > > somehow?
> > > > > > > > Or
> > > > > > > > this is just a simple error in the doc, which needs to be
> > fixed?
> > > > > > > >
> > > > > > > > Would appreciate the insight from the team. Thanks!
> > > > > > > >   Cos
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Andrey Gura
> > > > > > > GridGain Systems, Inc.
> > > > > > > www.gridgain.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Andrey Gura
> > > > > GridGain Systems, Inc.
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Andrey Gura
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>

Re: Accidental deserialization of BinaryObject key on a remote node

[Alexey Goncharuk]

Denis,

I will take a look at this tomorrow.

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> Thanks Andrey!
> 
> Why are we enabling peer class loading for the JDBC driver in your example?
> To my knowledge, we are not deploying any classes, are we? Also, the TCP
> discovery with multicast is the default, so no reason to specify it either.
> 
> It seems that the only properly required is clientMode=true, no?

If this is the case, then _no_ config is really needed, perhaps?

> 
> D.
> 
> On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura  wrote:
> 
> > Configuration sample added.
> >
> > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> > wrote:
> >
> > > Thanks Andrey!
> > >
> > > In my view, we should also provide a sample XML configuration file,
> > > especially given that we refer to it in the sample URL.
> > >
> > > D.
> > >
> > > On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura  wrote:
> > >
> > > > Done. I hope that is more clear now.
> > > >
> > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > > wrote:
> > > > >
> > > > > > Cos,
> > > > > >
> > > > > >  sepcifies configuration file for Ignite client node
> > that
> > > > > will
> > > > > > be started during connection establishing by JDBC driver. So this
> > > file
> > > > > > should be available for JDBC driver client.
> > > > > >
> > > > >
> > > > > Andrey, should this be documented here?
> > > > > https://apacheignite.readme.io/docs/jdbc-driver
> > > > >
> > > > > D.
> > > > >
> > > > >
> > > > > >
> > > > > > On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik  > >
> > > > > wrote:
> > > > > >
> > > > > > > Thanks Andrey!
> > > > > > >
> > > > > > > Still a bit unclear: the doc says
> > > > > > > " is required and represents any valid URL which
> > points
> > > > to
> > > > > > > Ignite configuration file"
> > > > > > >
> > > > > > > So, that's server side URL then, something like
> > > > > > > jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
> > > > > > >
> > > > > > > assuming that server nodes have said configuration under
> > > > > > > /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a
> > bit
> > > > > > dense,
> > > > > > > or
> > > > > > > the doc isn't written to a layman
> > > > > > >
> > > > > > > Thanks in advance!
> > > > > > >   Cos
> > > > > > >
> > > > > > > On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > > > > > > > Cos,
> > > > > > > >
> > > > > > > > JDBC driver was reworked in order to use Ignite client node
> > > instead
> > > > > of
> > > > > > > > Ignite Java client. It gives better performance. So now JDBC
> > > dirver
> > > > > > uses
> > > > > > > > Ignite xml configuration file using jdbc:ignite:cfg protocol.
> > See
> > > > > > > > documentation for version 1.4
> > > > > > > > https://apacheignite.readme.io/v1.4/docs/jdbc-driver
> > > > > > > >
> > > > > > > > At the same time we still support old version of JDBC driver
> > that
> > > > > uses
> > > > > > > > jdbc:ignite protocol. See documentation for version 1.3
> > > > > > > > https://apacheignite.readme.io/v1.3/docs/jdbc-driver
> > > > > > > >
> > > > > > > > Thus you can control used JDBC driver type (new or old) just
> > with
> > > > > > choosen
> > > > > > > > protocol.
> > > > > > > >
> > > > > > > > Please, note, that old JDBC driver is deprecated and can be
> > > removed
> > > > > > from
> > > > > > > > future releases.
> > > > > > > >
> > > > > > > > On Mon, Dec 7, 2015 at 6:41 AM, Konstantin Boudnik <
> > > c...@apache.org
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Guys, I am looking into [1] and see a reference to
> > > > > > > > >
> > > > > > > > > ignite.jdbc.url = "jdbc:ignite:cfg://"
> > > > > > > > >
> > > > > > > > > So, I am curious if there's a way to fetch node's config via
> > > JDBC
> > > > > > > somehow?
> > > > > > > > > Or
> > > > > > > > > this is just a simple error in the doc, which needs to be
> > > fixed?
> > > > > > > > >
> > > > > > > > > Would appreciate the insight from the team. Thanks!
> > > > > > > > >   Cos
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Andrey Gura
> > > > > > > > GridGain Systems, Inc.
> > > > > > > > www.gridgain.com
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrey Gura
> > > > > > GridGain Systems, Inc.
> > > > > > www.gridgain.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Andrey Gura
> > > > GridGain Systems, Inc.
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >


signature.asc
Description: 

Re: NPE issue with trying to submit Hadoop MapReduce

[Vladimir Ozerov]

 Currently if peerClassLoadingEnabled=true and Hadoop is in classpath, we
simply do not load Hadoop module silently. This is definitely a problem and
I created a ticket to fix this in 1.6.

On Thu, Dec 10, 2015 at 10:38 AM, Dmitriy Setrakyan 
wrote:

> Moving this question to the dev list.
>
> Vladimir, any reason why we even allow peerClassLoadingEnabled set to true
> in IGFS/HadoopMR? I think the proper approach is to either ignore this
> setting or throw exception on startup, no?
>
> D.
>
>
>
> On Wed, Dec 9, 2015 at 2:51 AM, Vladimir Ozerov 
> wrote:
>
>> Mike,
>>
>> Thanks for attaching the project. It helped me got to the bottom of the
>> problem. Please remove the following line from example-igfs.xml file:
>>
>> 
>>
>> After that you should be able to use Hadoop Accelerator. This is a kind
>> of subtle usability issue. We will address it in the nearest feature
>> ensuring that meaningful error/warning is printed in such situations.
>> Please let me know if it resolves your problem.
>>
>> Vladimir.
>>
>>
>> On Wed, Dec 9, 2015 at 3:10 AM, mikep 
>> wrote:
>>
>>> Hi Vladimir
>>>
>>> Heres a recreated example as standalone mini example with the same
>>> failing
>>> example in case it helps, recreating the same issue.
>>>
>>> Using intellij,
>>>
>>> run the IgniteNode class that starts up the ignite node (using spring).
>>>
>>> then run the TestExample class,
>>>
>>> this execute a few HDFS commands successfully and sets up a file on
>>> IgniteFS
>>> using HDFS api.
>>> and then executes the same job as mentioned before, on the cluster which
>>> suffers the issue.
>>>
>>>
>>> exampleignite.zip
>>> <
>>> http://apache-ignite-users.70518.x6.nabble.com/file/n2180/exampleignite.zip
>>> >
>>>
>>> just incase, java version is jdk1.8.0_25.jdk
>>>
>>> Cheers
>>> Mike
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-ignite-users.70518.x6.nabble.com/NPE-issue-with-trying-to-submit-Hadoop-MapReduce-tp2146p2180.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>

Re: ignite-osgi-karaf on maven repository

[Dmitriy Setrakyan]

Raul, can you please comment?

On Wed, Dec 9, 2015 at 4:28 AM, Sergey Kozlov  wrote:

> Hi Igniters.
>
> I tried to create a staging url from latest ignite-1.5 branch and found
> that ignite-osgi-karaf has following file
> *
> https://repository.apache.org/content/repositories/orgapacheignite-1207/org/apache/ignite/ignite-osgi-karaf/1.5.0-b2/ignite-osgi-karaf-1.5.0-b2-features.xml
> <
> https://repository.apache.org/content/repositories/orgapacheignite-1207/org/apache/ignite/ignite-osgi-karaf/1.5.0-b2/ignite-osgi-karaf-1.5.0-b2-features.xml
> >*
>  where ignite-hibernate defined.
>
> I'm a bit concerning that actually we don't have this module in Apache
> Maven repository due license reasons (it's LGPL) and it's available only by
> compiling from sources.
>
> Could someone confirm is that ok or not.
>
> --
> Sergey Kozlov
>

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Configuration sample added.

On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
wrote:

> Thanks Andrey!
>
> In my view, we should also provide a sample XML configuration file,
> especially given that we refer to it in the sample URL.
>
> D.
>
> On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura  wrote:
>
> > Done. I hope that is more clear now.
> >
> > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan  >
> > wrote:
> >
> > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> wrote:
> > >
> > > > Cos,
> > > >
> > > >  sepcifies configuration file for Ignite client node that
> > > will
> > > > be started during connection establishing by JDBC driver. So this
> file
> > > > should be available for JDBC driver client.
> > > >
> > >
> > > Andrey, should this be documented here?
> > > https://apacheignite.readme.io/docs/jdbc-driver
> > >
> > > D.
> > >
> > >
> > > >
> > > > On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik 
> > > wrote:
> > > >
> > > > > Thanks Andrey!
> > > > >
> > > > > Still a bit unclear: the doc says
> > > > > " is required and represents any valid URL which points
> > to
> > > > > Ignite configuration file"
> > > > >
> > > > > So, that's server side URL then, something like
> > > > > jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
> > > > >
> > > > > assuming that server nodes have said configuration under
> > > > > /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a bit
> > > > dense,
> > > > > or
> > > > > the doc isn't written to a layman
> > > > >
> > > > > Thanks in advance!
> > > > >   Cos
> > > > >
> > > > > On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > > > > > Cos,
> > > > > >
> > > > > > JDBC driver was reworked in order to use Ignite client node
> instead
> > > of
> > > > > > Ignite Java client. It gives better performance. So now JDBC
> dirver
> > > > uses
> > > > > > Ignite xml configuration file using jdbc:ignite:cfg protocol. See
> > > > > > documentation for version 1.4
> > > > > > https://apacheignite.readme.io/v1.4/docs/jdbc-driver
> > > > > >
> > > > > > At the same time we still support old version of JDBC driver that
> > > uses
> > > > > > jdbc:ignite protocol. See documentation for version 1.3
> > > > > > https://apacheignite.readme.io/v1.3/docs/jdbc-driver
> > > > > >
> > > > > > Thus you can control used JDBC driver type (new or old) just with
> > > > choosen
> > > > > > protocol.
> > > > > >
> > > > > > Please, note, that old JDBC driver is deprecated and can be
> removed
> > > > from
> > > > > > future releases.
> > > > > >
> > > > > > On Mon, Dec 7, 2015 at 6:41 AM, Konstantin Boudnik <
> c...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Guys, I am looking into [1] and see a reference to
> > > > > > >
> > > > > > > ignite.jdbc.url = "jdbc:ignite:cfg://"
> > > > > > >
> > > > > > > So, I am curious if there's a way to fetch node's config via
> JDBC
> > > > > somehow?
> > > > > > > Or
> > > > > > > this is just a simple error in the doc, which needs to be
> fixed?
> > > > > > >
> > > > > > > Would appreciate the insight from the team. Thanks!
> > > > > > >   Cos
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > >
> > > >
> > >
> >
> https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrey Gura
> > > > > > GridGain Systems, Inc.
> > > > > > www.gridgain.com
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Andrey Gura
> > > > GridGain Systems, Inc.
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>



-- 
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com