[jira] [Created] (IGNITE-2538) RDD.isEmpty method should be overriden in IgniteRDD to use IgniteCache API

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2538:
---

 Summary: RDD.isEmpty method should be overriden in IgniteRDD to 
use IgniteCache API
 Key: IGNITE-2538
 URL: https://issues.apache.org/jira/browse/IGNITE-2538
 Project: Ignite
  Issue Type: Improvement
  Components: Ignite RDD
Reporter: Valentin Kulichenko


Currently calling {{IgniteRDD.isEmpty}} ends up in execution of 1024 Spark 
jobs, which is not fast. We should override this method and use native 
{{IgniteCache}} API there. Other methods should be also revisited.



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

Full API coverage enhancement

[Artem Shutak]

Igniters,

I'm working on an enhancement of Full API coverage [1] [2].

Ignite already has Full API test, but currently it's hard to test all
configuration combinations.

Feel free to add comments in the jira if you have any thought.

[1] https://issues.apache.org/jira/browse/IGNITE-2521
[2] https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests

Thanks,
-- Artem --

Fwd: [jira] [Commented] (IGNITE-1523) Need to always serialize user objects with configured marshaller

[Valentin Kulichenko]

Anton,

If you're working in this issue, can you please assign it to yourself?

-Val

-- Forwarded message --
From: Anton Vinogradov (JIRA) 
Date: Tue, Feb 2, 2016 at 4:43 AM
Subject: [jira] [Commented] (IGNITE-1523) Need to always serialize user
objects with configured marshaller
To: valentin.kuliche...@gmail.com



[
https://issues.apache.org/jira/browse/IGNITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128185#comment-15128185
]

Anton Vinogradov commented on IGNITE-1523:
--

Fixed unmarshalling of Enum
Fixed unmarshalling of CacheStoreFactory within CacheConfiguration
All new checks added to GridCacheReplicatedPreloadSelfTest

> Need to always serialize user objects with configured marshaller
> 
>
> Key: IGNITE-1523
> URL: https://issues.apache.org/jira/browse/IGNITE-1523
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
>  Labels: important, user-request
> Fix For: 1.6
>
>
> Currently some components (at least discovery) use {{JdkMarshaller}} for
all objects.



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

Re: Full API coverage enhancement

[Artem Shutak]

Dmitriy,

There is a branch at my fork and a pull request at Ignite. See comment
about pull request at the ticket (PR-446).

But I have to notice that the branch under hard development and you it can
not work (have compilation or test errors) at some moments.

Good luck!

-- Artem --

On Tue, Feb 2, 2016 at 9:45 PM, Dmitriy Setrakyan 
wrote:

> Artem,
>
> This is great. I have noticed from the ticket that you have created some
> initial suite already. Is there a branch I can look at it?
>
> D.
>
> On Tue, Feb 2, 2016 at 10:02 AM, Artem Shutak 
> wrote:
>
> > Igniters,
> >
> > I'm working on an enhancement of Full API coverage [1] [2].
> >
> > Ignite already has Full API test, but currently it's hard to test all
> > configuration combinations.
> >
> > Feel free to add comments in the jira if you have any thought.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-2521
> > [2]
> https://cwiki.apache.org/confluence/display/IGNITE/Implementing+Tests
> >
> > Thanks,
> > -- Artem --
> >
>

Re: streamer documentation

[Dmitriy Setrakyan]

Denis,

Is there any chance you can mention the names of the contributors, so we
could reach out to them personally and ask for help with the documentation?
I know that Camel streamer was done by Raul, but not sure about the other
two.

D.

On Tue, Feb 2, 2016 at 12:37 AM, Denis Magda  wrote:

> The tickets are already there
>
> Twitter: https://issues.apache.org/jira/browse/IGNITE-2413
> MQTT: https://issues.apache.org/jira/browse/IGNITE-2411
> Camel: https://issues.apache.org/jira/browse/IGNITE-2530
>
> It would be perfect if Igniters who contributed this functionality will
> add the documentation as well.
>
> --
> Denis
>
>
> On 2/2/2016 11:31 AM, Dmitriy Setrakyan wrote:
>
>> Igniters,
>>
>> I have been trying to find documentation for the following streamers but
>> couldn’t:
>>
>> - Camel
>> - MQTT
>> - Twitter
>>
>> Can I ask the contributors to document these features on readme?
>>
>> Thanks,
>> D.
>>
>>
>

Re: streamer documentation

[Denis Magda]

The tickets are already there

Twitter: https://issues.apache.org/jira/browse/IGNITE-2413
MQTT: https://issues.apache.org/jira/browse/IGNITE-2411
Camel: https://issues.apache.org/jira/browse/IGNITE-2530

It would be perfect if Igniters who contributed this functionality will 
add the documentation as well.


--
Denis

On 2/2/2016 11:31 AM, Dmitriy Setrakyan wrote:

Igniters,

I have been trying to find documentation for the following streamers but
couldn’t:

- Camel
- MQTT
- Twitter

Can I ask the contributors to document these features on readme?

Thanks,
D.

Re: streamer documentation

[Denis Magda]

Dmitriy,

Raul contributed both Camel and MQTT.
Twitter streamer was implemented by Lalit Kumar Jha.

Actually I tried reach out both Raul and Lalit Kumar Jha earlier 
regarding this topic but seems that they were too busy because I didn't 
get any response from them.


Raul, Lalit Kumar Jha, do you have time to add the documentation or 
someone else from the community should take care of this?


Regards,
Denis

On 2/2/2016 11:42 AM, Dmitriy Setrakyan wrote:

Denis,

Is there any chance you can mention the names of the contributors, so we
could reach out to them personally and ask for help with the documentation?
I know that Camel streamer was done by Raul, but not sure about the other
two.

D.

On Tue, Feb 2, 2016 at 12:37 AM, Denis Magda  wrote:


The tickets are already there

Twitter: https://issues.apache.org/jira/browse/IGNITE-2413
MQTT: https://issues.apache.org/jira/browse/IGNITE-2411
Camel: https://issues.apache.org/jira/browse/IGNITE-2530

It would be perfect if Igniters who contributed this functionality will
add the documentation as well.

--
Denis


On 2/2/2016 11:31 AM, Dmitriy Setrakyan wrote:


Igniters,

I have been trying to find documentation for the following streamers but
couldn’t:

- Camel
- MQTT
- Twitter

Can I ask the contributors to document these features on readme?

Thanks,
D.

new committer and PMC member: Roman Shtykh

[Anton Vinogradov]

The Project Management Committee (PMC) for Apache Ignite has asked Roman
Shtykh
to become a committer and PMC member and we are pleased to announce
that Roman has accepted.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity. Being a PMC member enables assistance with the management and
to guide the direction of the project.

streamer documentation

[Dmitriy Setrakyan]

Igniters,

I have been trying to find documentation for the following streamers but
couldn’t:

- Camel
- MQTT
- Twitter

Can I ask the contributors to document these features on readme?

Thanks,
D.

[jira] [Created] (IGNITE-2530) Camel streamer documentation is missing on readme.io

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2530:
---

 Summary: Camel streamer documentation is missing on readme.io
 Key: IGNITE-2530
 URL: https://issues.apache.org/jira/browse/IGNITE-2530
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Denis Magda
 Fix For: 1.5.0.final


Camel streamer was released as a part of 1.5. However there is no documentation 
available on readme.io describing the new streaming functionality.
Following documentation can be used as a reference
https://apacheignite.readme.io/docs/jms-data-streamer
https://apacheignite.readme.io/docs/flume-data-streamer



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

[jira] [Created] (IGNITE-2534) Aliases

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2534:
--

 Summary: Aliases
 Key: IGNITE-2534
 URL: https://issues.apache.org/jira/browse/IGNITE-2534
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Tupitsyn


QueryEntity.aliases should be taken into account



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

[jira] [Created] (IGNITE-2535) Assert in GridCacheMapEntry.innerUpdate (invalid entry)

[Noam Liran (JIRA)]

Noam Liran created IGNITE-2535:
--

 Summary: Assert in GridCacheMapEntry.innerUpdate (invalid entry)
 Key: IGNITE-2535
 URL: https://issues.apache.org/jira/browse/IGNITE-2535
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Noam Liran


Discussed previously with Semyon on IGNITE-560.
Cache settings:
{noformat}
.setCacheMode(CacheMode.PARTITIONED)
.setAtomicityMode(CacheAtomicityMode.ATOMIC)
.setBackups(0)
.setCacheStoreFactory(..)
.setEvictionPolicy(new LruEvictionPolicy(1_000_000))
.setLoadPreviousValue(true)
{noformat}

{noformat}
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys 
(retry update if possible).: 
[com.adallom.lograbber.tables.UserTable$EmailsCacheKey@713dfd15]
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1604)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1841)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1079)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at com.adallom.lograbber.GrabberBase.call(GrabberBase.java:24) 
[lograbber.jar:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_60]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_60]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
Caused by: 
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException: 
Failed to update keys (retry update if possible).: 
[com.adallom.lograbber.tables.UserTable$EmailsCacheKey@713dfd15]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.addFailedKeys(GridNearAtomicUpdateFuture.java:1241)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture$UpdateState.onResult(GridNearAtomicUpdateFuture.java:661)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.onResult(GridNearAtomicUpdateFuture.java:344)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateResponse(GridDhtAtomicCache.java:2618)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$700(GridDhtAtomicCache.java:128)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:263)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$6.apply(GridDhtAtomicCache.java:261)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:821)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:784)
 ~[ignite-core-1.5.0.final.jar:1.5.0.final]
... 3 common frames omitted
Suppressed: org.apache.ignite.IgniteCheckedException: Failed to update 
keys on primary node.
at 

[jira] [Created] (IGNITE-2536) cache.invoke() for single key and OFFHEAP_TIERED doesn't work

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-2536:
---

 Summary: cache.invoke() for single key and OFFHEAP_TIERED doesn't 
work
 Key: IGNITE-2536
 URL: https://issues.apache.org/jira/browse/IGNITE-2536
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.5.0.final
Reporter: Andrey Gura


cache.invoke() for single key and OFFHEAP_TIERED fails with the following 
exception:

{noformat}
Exception in thread 
"sys-#68%version.CacheVersionedEntryPartitionedAtomicOffHeapSelfTest1%" 
java.lang.AssertionError
at 
org.apache.ignite.internal.processors.cache.CacheObjectAdapter.writeExternal(CacheObjectAdapter.java:61)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeExternalizable(OptimizedObjectOutputStream.java:319)
at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:754)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:247)
at 
org.apache.ignite.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:161)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:343)
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.marshal(OptimizedMarshaller.java:193)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:158)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:130)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:443)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1044)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:627)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:669)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:198)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:130)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.marshal(GridBinaryMarshaller.java:233)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.marshalToBinary(CacheObjectBinaryProcessorImpl.java:514)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toBinary(CacheObjectBinaryProcessorImpl.java:858)
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.toCacheObject(CacheObjectBinaryProcessorImpl.java:805)
at 
org.apache.ignite.internal.processors.cache.GridCacheContext.toCacheObject(GridCacheContext.java:1807)
at 
org.apache.ignite.internal.processors.cache.GridCacheReturn.addEntryProcessResult(GridCacheReturn.java:257)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2153)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1441)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1316)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:2726)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:129)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:258)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:256)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:605)
{noformat}





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

[jira] [Created] (IGNITE-2532) NPE in TcpDiscoveryMulticastIpFinder.getTimeToLive

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-2532:
--

 Summary: NPE in TcpDiscoveryMulticastIpFinder.getTimeToLive
 Key: IGNITE-2532
 URL: https://issues.apache.org/jira/browse/IGNITE-2532
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.1.4
Reporter: Pavel Tupitsyn
Priority: Critical
 Fix For: 1.6


ttl field is Integer, property is int

{code}
public int getTimeToLive() { return ttl; }
{code}



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

[GitHub] ignite pull request: IGNITE-1906 .Net: Ignite configuration withou...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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-2533) Get rid of CompoundFutures and MiniFutures where possible.

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-2533:


 Summary: Get rid of CompoundFutures and MiniFutures where possible.
 Key: IGNITE-2533
 URL: https://issues.apache.org/jira/browse/IGNITE-2533
 Project: Ignite
  Issue Type: Sub-task
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh






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

Re: About the Jira https://issues.apache.org/jira/browse/IGNITE-1481

[Ken Cheng]

I prefer to throw a IgniteCheckerException.

Thanks,
kcheng

On Wed, Feb 3, 2016 at 2:41 PM, Ken Cheng  wrote:

> Hi Andrey Gura,
>
>
> What's the expected behavior when the cache mode is "Local" but affinity
> function is not  "LocalAffinityFunction"?
>
> 1: Throw an exception?
> 2: or change the affinity function rudely as "LocalAffinityFunction" and
> log the warning message at same time?
>
>
> Thanks,
> kcheng
>
> On Wed, Feb 3, 2016 at 10:35 AM, Ken Cheng  wrote:
>
>> Hi Andrey Gura,
>>
>> Thank you very much! I would study this part of code first.
>>
>> Thanks,
>> kcheng
>>
>> On Mon, Feb 1, 2016 at 6:37 PM, Andrey Gura  wrote:
>>
>>> Ken,
>>>
>>> cache configuration validation and initialization occurs in
>>> GridCacheProcessor class (methods validate() and initialize()).
>>>
>>> From my point of view two changes should be made:
>>>
>>> - during cache intialization LocalAffinityFunction should be set to cache
>>> configuration if cache mode is LOCAL;
>>> - warning about ignoring affinity function parameter should be moved from
>>> validate() method to intialize() method.
>>>
>>> I hope this will help you.
>>>
>>> On Mon, Feb 1, 2016 at 12:12 PM, Ken Cheng  wrote:
>>>
>>> > Hi Andrey Gura,
>>> >
>>> > I am very new to Ignite, I am going to pick up
>>> > https://issues.apache.org/jira/browse/IGNITE-1481.
>>> >
>>> > Can you please give more hint?
>>> >
>>> >
>>> >
>>> >
>>> > Thanks,
>>> > kcheng
>>> >
>>>
>>>
>>>
>>> --
>>> Andrey Gura
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>>
>>
>

[GitHub] ignite pull request: GridNearLockRequestV2 example implementation.

[ilantukh]

GitHub user ilantukh opened a pull request:

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

GridNearLockRequestV2 example implementation.

Do not merge.

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

$ git pull https://github.com/ilantukh/ignite future-v2

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

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


commit 6805ee650412baf6346d9d7cc3aa3a2a09f9bc01
Author: Ilya Lantukh 
Date:   2016-02-02T12:27:17Z

GridNearLockRequestV2 example implementation.




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