[jira] [Created] (IGNITE-2183) Broken UI after killing web agent

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2183:
--

 Summary: Broken UI after killing web agent
 Key: IGNITE-2183
 URL: https://issues.apache.org/jira/browse/IGNITE-2183
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov


Some time after I'm killing web agent a getting broken UI (please see 
attachment)



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

Re: store examples

[Valentin Kulichenko]

Yakov,

Code in Spring example was not ignoring txs. There
was CacheJdbcStoreSessionListener which handles this automatically. That's
how Spring works - it enlists all calls to jdbcTemplate into transaction if
it was opened by tx manager in this thread.

-Val

On Wed, Dec 16, 2015 at 6:35 AM, Yakov Zhdanov  wrote:

> Guys,
>
> I refactored JDBC store example to use h2 server startup.
>
> I decided to remove spring store example since code will be too complex
> after fixing all issues with transactions along with jdbcTemplate (current
> code absolutely ignores txs)
> + I removed dummy example as per Val's suggestion.
>
> --Yakov
>
> 2015-12-16 9:23 GMT+03:00 Dmitriy Setrakyan :
>
> > Got it. Yakov, I think this will work without any coding change. Can you
> > confirm?
> >
> > On Tue, Dec 15, 2015 at 6:30 PM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > wrote:
> >
> > > I think mentioned examples could be easily fixed by switching from use
> of
> > > H2 started from example to o.a.i.examples.util.DbH2ServerStartup.
> > > This will start full fledged H2 server with in-memory db and all nodes
> > will
> > > work with it.
> > >
> > > >> Ignite nodes, then why not switch to using H2 disk store?
> > > Dima, this would not work, because file will be locked by first started
> > > process and other will failed.
> > >
> > > I think we should go as I mentioned above.
> > >
> > >
> > > On Wed, Dec 16, 2015 at 7:23 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > If the problem is the H2 in-memory store not being shared between
> > > multiple
> > > > Ignite nodes, then why not switch to using H2 disk store?
> > > >
> > > > On Tue, Dec 15, 2015 at 4:11 PM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > As far as I understand, the issue is that CacheJdbcStoreExample
> > > > > and CacheSpringStoreExample use in-memory H2 database, so the cache
> > > store
> > > > > is not shared among nodes. What if we just switch to a file-based
> DB?
> > > It
> > > > > looks like a simple change to me.
> > > > >
> > > > > And I would remove CacheDummyStoreExample. It looks weird and
> doesn't
> > > > > demonstrate anything that is not shown in other store examples.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Tue, Dec 15, 2015 at 2:03 PM, Dmitriy Setrakyan <
> > > > dsetrak...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > I think we should fix all the examples. What has changed that
> makes
> > > > these
> > > > > > examples so difficult to fix?
> > > > > >
> > > > > > I really do not like removing the examples that have been
> > > continuously
> > > > > > shipped in every release. If it is so difficult for us to upgrade
> > > them
> > > > to
> > > > > > 1.5, how difficult will it be for our users?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Dec 15, 2015 at 7:24 AM, Yakov Zhdanov <
> > yzhda...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > We still have very advanced and cool
> CacheBinaryAutoStoreExample
> > > and
> > > > it
> > > > > > > works properly
> > > > > > >
> > > > > > > --Yakov
> > > > > > >
> > > > > > > 2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >:
> > > > > > >
> > > > > > > > If it is an example issue, why can’t we fix the examples? I
> am
> > > not
> > > > > > > > comfortable removing CacheJdbcStoreExample from the release.
> > > > > > > >
> > > > > > > > On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov <
> > > > yzhda...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-2158
> > > > > > > > >
> > > > > > > > > Guys,
> > > > > > > > >
> > > > > > > > > It seems that CacheDummyStoreExample, CacheJdbcStoreExample
> > and
> > > > > > > > > CacheSpringStoreExample do not work correctly in
> distributed
> > > > > > > environment
> > > > > > > > > after code modifications to demonstrate clear() and
> > > > withSkipStore()
> > > > > > > > >
> > > > > > > > > This is an old issue and it is 100% examples' issue, so I
> > > suggest
> > > > > > > > removing
> > > > > > > > > them from 1.5 and fix and return back to distro in 1.6
> > > > > > > > >
> > > > > > > > > Thoughts?
> > > > > > > > >
> > > > > > > > > --Yakov
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>

[jira] [Created] (IGNITE-2182) Failed to initialize cache store (data source is not provided).

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-2182:
--

 Summary: Failed to initialize cache store (data source is not 
provided).
 Key: IGNITE-2182
 URL: https://issues.apache.org/jira/browse/IGNITE-2182
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Alexey Kuznetsov


{code}
Failed to initialize cache store (data source is not provided).
at 
org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8385)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1269)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1638)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1563)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:944)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:511)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to initialize cache 
store (data source is not provided).
at 
org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.start(CacheAbstractJdbcStore.java:297)
at 
org.apache.ignite.internal.util.IgniteUtils.startLifecycleAware(IgniteUtils.java:8381)
... 8 more
{code}



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

Re: Missing ways to get access to Ignite CacheEntry

[Romain Gilles]

Hi Denis,
Thanks for you replay. And sorry to not double check it before. I see that
if I want to work with CacheEntry, I need to use the invoke method in order
to return the CacheEntry. This is the way I should do it. It sounds like
complicated for "just" getting an entry. But if you say this is the way I
will do it like that. I was just think that it could be a common use case
and therefore provide it as a shortcut.

Thanks,

Romain.

Le mer. 16 déc. 2015 à 11:34, Denis Magda  a écrit :

> Hi Romain,
>
> As the current documentation of org.apache.ignite.cache.CacheEntry
> states it's possible to get a reference to CacheEntry and its version
> only for methods that are executed over local data set stored on a node.
> Among such methods are invoke & invokeAll and randomEntry.
>
> You probably can get a CacheEntry and its non null version when a cache
> iterator is in use but the version will be 'null', as far as I remember,
> for those entries that are loaded from remote nodes.
> Presently Ignite doesn't transfer the version from remote nodes as a
> part of response by perform reasons.
>
> Please elaborate more on your particular use case and what API you would
> like to add in order to support it.
>
> --
> Denis
>
> On 12/16/2015 12:58 PM, Romain Gilles wrote:
> > Hi Igniters,
> > I'm looking for a way to get access to the Ignite CacheEntry. For now
> this
> > is the ways I found:
> >
> > - Through the queris
> > - Through jsr 107 Cache Iterable
> > - Through jsr 107 Cache itterator
> > - Through IgniteCache::randomEntry()
> >
> > If I remember correctly it was possible to get the CacheEntry from a
> given
> > key in old version of gridgain community
> > version: GridCacheProjection::entry(K key) GridCacheEntry
> > I think it could be a good to introduce this feature at IgniteCache
> level.
> > Or maybe there is an other way to do it.
> >
> > Thanks,
> >
> > Romain.
> >
>
>

[GitHub] ignite pull request: IGNITE-2138 Introduced toBuilder() method.

[agoncharuk]

Github user agoncharuk closed the pull request at:

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


---
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: Abandoned ticket: Provide Integration with Spring Data [IGNITE-1192]

[Jörn Franke]

Sent from my iPhone

> On 16 Dec 2015, at 10:45, Denis Magda  wrote:
> 
> I've unassigned the ticket from Vikrant.
> 
> Is anyone in the community is interesting in taking over this task?
> 
> --
> Denis
> 
>> On 12/15/2015 3:36 PM, Denis Magda wrote:
>> Hi Vikrant,
>> 
>> Do you have free time to complete the integration in the nearest month?
>> 
>> This integration is becoming quite urgent. So if you don’t have time for now 
>> someone else from the community will pick this ticket up.
>> 
>> Regards,
>> Denis
> 

Re: Missing ways to get access to Ignite CacheEntry

[Denis Magda]

Romain,

If it's implemented this way for now it doesn't mean that we can't 
enhance the API for other use cases ;)
As I said presently it's supported for limited number of methods mostly 
by performance reasons.


Please go ahead and try invoke/invokeAll and if it doesn't work fine for 
you we can keep discussing what to do next.


Regards,
Denis

On 12/16/2015 1:53 PM, Romain Gilles wrote:

Hi Denis,
Thanks for you replay. And sorry to not double check it before. I see that
if I want to work with CacheEntry, I need to use the invoke method in order
to return the CacheEntry. This is the way I should do it. It sounds like
complicated for "just" getting an entry. But if you say this is the way I
will do it like that. I was just think that it could be a common use case
and therefore provide it as a shortcut.

Thanks,

Romain.

Le mer. 16 déc. 2015 à 11:34, Denis Magda  a écrit :


Hi Romain,

As the current documentation of org.apache.ignite.cache.CacheEntry
states it's possible to get a reference to CacheEntry and its version
only for methods that are executed over local data set stored on a node.
Among such methods are invoke & invokeAll and randomEntry.

You probably can get a CacheEntry and its non null version when a cache
iterator is in use but the version will be 'null', as far as I remember,
for those entries that are loaded from remote nodes.
Presently Ignite doesn't transfer the version from remote nodes as a
part of response by perform reasons.

Please elaborate more on your particular use case and what API you would
like to add in order to support it.

--
Denis

On 12/16/2015 12:58 PM, Romain Gilles wrote:

Hi Igniters,
I'm looking for a way to get access to the Ignite CacheEntry. For now

this

is the ways I found:

 - Through the queris
 - Through jsr 107 Cache Iterable
 - Through jsr 107 Cache itterator
 - Through IgniteCache::randomEntry()

If I remember correctly it was possible to get the CacheEntry from a

given

key in old version of gridgain community
version: GridCacheProjection::entry(K key) GridCacheEntry
I think it could be a good to introduce this feature at IgniteCache

level.

Or maybe there is an other way to do it.

Thanks,

Romain.

Re: store examples

[Yakov Zhdanov]

Guys,

I refactored JDBC store example to use h2 server startup.

I decided to remove spring store example since code will be too complex
after fixing all issues with transactions along with jdbcTemplate (current
code absolutely ignores txs)
+ I removed dummy example as per Val's suggestion.

--Yakov

2015-12-16 9:23 GMT+03:00 Dmitriy Setrakyan :

> Got it. Yakov, I think this will work without any coding change. Can you
> confirm?
>
> On Tue, Dec 15, 2015 at 6:30 PM, Alexey Kuznetsov  >
> wrote:
>
> > I think mentioned examples could be easily fixed by switching from use of
> > H2 started from example to o.a.i.examples.util.DbH2ServerStartup.
> > This will start full fledged H2 server with in-memory db and all nodes
> will
> > work with it.
> >
> > >> Ignite nodes, then why not switch to using H2 disk store?
> > Dima, this would not work, because file will be locked by first started
> > process and other will failed.
> >
> > I think we should go as I mentioned above.
> >
> >
> > On Wed, Dec 16, 2015 at 7:23 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > If the problem is the H2 in-memory store not being shared between
> > multiple
> > > Ignite nodes, then why not switch to using H2 disk store?
> > >
> > > On Tue, Dec 15, 2015 at 4:11 PM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > As far as I understand, the issue is that CacheJdbcStoreExample
> > > > and CacheSpringStoreExample use in-memory H2 database, so the cache
> > store
> > > > is not shared among nodes. What if we just switch to a file-based DB?
> > It
> > > > looks like a simple change to me.
> > > >
> > > > And I would remove CacheDummyStoreExample. It looks weird and doesn't
> > > > demonstrate anything that is not shown in other store examples.
> > > >
> > > > -Val
> > > >
> > > > On Tue, Dec 15, 2015 at 2:03 PM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > I think we should fix all the examples. What has changed that makes
> > > these
> > > > > examples so difficult to fix?
> > > > >
> > > > > I really do not like removing the examples that have been
> > continuously
> > > > > shipped in every release. If it is so difficult for us to upgrade
> > them
> > > to
> > > > > 1.5, how difficult will it be for our users?
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Dec 15, 2015 at 7:24 AM, Yakov Zhdanov <
> yzhda...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > We still have very advanced and cool CacheBinaryAutoStoreExample
> > and
> > > it
> > > > > > works properly
> > > > > >
> > > > > > --Yakov
> > > > > >
> > > > > > 2015-12-15 18:11 GMT+03:00 Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >:
> > > > > >
> > > > > > > If it is an example issue, why can’t we fix the examples? I am
> > not
> > > > > > > comfortable removing CacheJdbcStoreExample from the release.
> > > > > > >
> > > > > > > On Tue, Dec 15, 2015 at 4:02 AM, Yakov Zhdanov <
> > > yzhda...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-2158
> > > > > > > >
> > > > > > > > Guys,
> > > > > > > >
> > > > > > > > It seems that CacheDummyStoreExample, CacheJdbcStoreExample
> and
> > > > > > > > CacheSpringStoreExample do not work correctly in distributed
> > > > > > environment
> > > > > > > > after code modifications to demonstrate clear() and
> > > withSkipStore()
> > > > > > > >
> > > > > > > > This is an old issue and it is 100% examples' issue, so I
> > suggest
> > > > > > > removing
> > > > > > > > them from 1.5 and fix and return back to distro in 1.6
> > > > > > > >
> > > > > > > > Thoughts?
> > > > > > > >
> > > > > > > > --Yakov
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

[jira] [Created] (IGNITE-2180) Javadocs for some modules are missing from Maven repository

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-2180:
--

 Summary: Javadocs for some modules  are missing from Maven 
repository 
 Key: IGNITE-2180
 URL: https://issues.apache.org/jira/browse/IGNITE-2180
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.5
 Environment: Apache Ignite 1.5.0-b2 build #112
Reporter: Vasilisa  Sidorova
 Fix For: 1.5


Javadocs are missing from Maven repository for following modules:

* ignite-clients
* ignite-extdata-uri
* ignite-osgi-karaf
* ignite-osgi-paxlogging
* ignite-scalar
* ignite-scalar_2.10
* ignite-spark
* ignite-spark_2.10
* ignite-visor-console
* ignite-visor-console_2.10

Please, fix it



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

[GitHub] ignite pull request: IGNITE-2178 - Fixed primary key set for scan ...

[agoncharuk]

GitHub user agoncharuk opened a pull request:

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

IGNITE-2178 - Fixed primary key set for scan query.



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

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

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

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


commit ac6b70e64b3bb9b16821231764844a8e9b5e8dfa
Author: Alexey Goncharuk 
Date:   2015-12-16T12:10:10Z

IGNITE-2178 - Fixed primary key set for scan query.




---
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: Abandoned ticket: Provide Integration with Spring Data [IGNITE-1192]

[Vikrant Navalgund]

Thank you Denis, I was unable to focus on the task.

Regards,
Vikrant

On Wed, Dec 16, 2015 at 10:17 PM, Jörn Franke  wrote:

>
>
> Sent from my iPhone
>
> > On 16 Dec 2015, at 10:45, Denis Magda  wrote:
> >
> > I've unassigned the ticket from Vikrant.
> >
> > Is anyone in the community is interesting in taking over this task?
> >
> > --
> > Denis
> >
> >> On 12/15/2015 3:36 PM, Denis Magda wrote:
> >> Hi Vikrant,
> >>
> >> Do you have free time to complete the integration in the nearest month?
> >>
> >> This integration is becoming quite urgent. So if you don’t have time
> for now someone else from the community will pick this ticket up.
> >>
> >> Regards,
> >> Denis
> >
>



-- 
*Regards*,
*Vikrant Navalgund*

[GitHub] ignite pull request: IGNITE-2153 .NET: Package descriptions are mi...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2153 .NET: Package descriptions are missing in doxygen-generated 
files.



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

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

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

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


commit 1b2d64d2000282c85fdcad4b8f75601cd96fdbc5
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:46:06Z

IGNITE-2152 .NET: Introduction page is missing.

commit 30657ac100f761a0c77bd26359c921850ca9980d
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:49:21Z

wip

commit f49e7028e79770d780f6f3dc6065ce68acfc1ca2
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:52:19Z

wip

commit 0c4f0c2875532d21f7661f8c62d31a9acf231b18
Author: Pavel Tupitsyn 
Date:   2015-12-16T06:56:36Z

cleanup

commit 3e41268605cd814365b8943d4027de918f013dcc
Author: Pavel Tupitsyn 
Date:   2015-12-16T07:05:57Z

wip

commit 199311dbf1a927d65d0f25c57736aad82c2c121e
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:02:24Z

Merge from ignite-1.5

commit 8d38433c081e06dc107c96cb9a1585695a014735
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:07:27Z

wip

commit 9a2aa2bd419267bab33a9c538fd7b0ee99899768
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:16:26Z

wip

commit 1bbeafcb2e7e0a2e9e77029dc290c9f32658a906
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:20:39Z

Fix xmldocs

commit cbdc3d68257256913080fa572df2f8800b8cfa1c
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:23:04Z

wip

commit 5a4903490e38849c553ea0d1d4359298a3a089ed
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:26:31Z

wip

commit f6d53e23a3b79a65faa928d819b43297a8bc654f
Author: Pavel Tupitsyn 
Date:   2015-12-16T12:28:46Z

wip




---
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-2181) Refactoring summary page, implement form fields

[Dmitriyff (JIRA)]

Dmitriyff created IGNITE-2181:
-

 Summary: Refactoring summary page, implement form fields
 Key: IGNITE-2181
 URL: https://issues.apache.org/jira/browse/IGNITE-2181
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.6
Reporter: Dmitriyff
Assignee: Dmitriyff
 Fix For: 1.6






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

Re: Abandoned ticket: Provide Integration with Spring Data [IGNITE-1192]

[Denis Magda]

I've unassigned the ticket from Vikrant.

Is anyone in the community is interesting in taking over this task?

--
Denis

On 12/15/2015 3:36 PM, Denis Magda wrote:

Hi Vikrant,

Do you have free time to complete the integration in the nearest month?

This integration is becoming quite urgent. So if you don’t have time for now 
someone else from the community will pick this ticket up.

Regards,
Denis

[GitHub] ignite pull request: Reproduce entry processor bug in presence of ...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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-2123: Added CacheEntryProcessorExample...

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-2123: Added CacheEntryProcessorExample to cache examples.



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

$ git pull https://github.com/shroman/ignite ignite-2123

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

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


commit 4ee94b32edacbbb56ef77b3bde5b1282ba3643de
Author: shtykh_roman 
Date:   2015-12-16T08:32:54Z

IGNITE-2123: Added CacheEntryProcessorExample to cache examples.




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

Missing ways to get access to Ignite CacheEntry

[Romain Gilles]

Hi Igniters,
I'm looking for a way to get access to the Ignite CacheEntry. For now this
is the ways I found:

   - Through the queris
   - Through jsr 107 Cache Iterable
   - Through jsr 107 Cache itterator
   - Through IgniteCache::randomEntry()

If I remember correctly it was possible to get the CacheEntry from a given
key in old version of gridgain community
version: GridCacheProjection::entry(K key) GridCacheEntry
I think it could be a good to introduce this feature at IgniteCache level.
Or maybe there is an other way to do it.

Thanks,

Romain.

[jira] [Created] (IGNITE-2177) User defined aggregate functions for SQL

[Sergi Vladykin (JIRA)]

Sergi Vladykin created IGNITE-2177:
--

 Summary: User defined aggregate functions for SQL
 Key: IGNITE-2177
 URL: https://issues.apache.org/jira/browse/IGNITE-2177
 Project: Ignite
  Issue Type: Wish
Reporter: Sergi Vladykin
 Fix For: 1.6


Need to design some factory like abstraction for creating map part and reduce 
part of the aggregate. 



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

[GitHub] ignite pull request: IGNITE-1626 .Net: Create NuGet package.

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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: Missing ways to get access to Ignite CacheEntry

[Denis Magda]

Hi Romain,

As the current documentation of org.apache.ignite.cache.CacheEntry 
states it's possible to get a reference to CacheEntry and its version 
only for methods that are executed over local data set stored on a node.

Among such methods are invoke & invokeAll and randomEntry.

You probably can get a CacheEntry and its non null version when a cache 
iterator is in use but the version will be 'null', as far as I remember, 
for those entries that are loaded from remote nodes.
Presently Ignite doesn't transfer the version from remote nodes as a 
part of response by perform reasons.


Please elaborate more on your particular use case and what API you would 
like to add in order to support it.


--
Denis

On 12/16/2015 12:58 PM, Romain Gilles wrote:

Hi Igniters,
I'm looking for a way to get access to the Ignite CacheEntry. For now this
is the ways I found:

- Through the queris
- Through jsr 107 Cache Iterable
- Through jsr 107 Cache itterator
- Through IgniteCache::randomEntry()

If I remember correctly it was possible to get the CacheEntry from a given
key in old version of gridgain community
version: GridCacheProjection::entry(K key) GridCacheEntry
I think it could be a good to introduce this feature at IgniteCache level.
Or maybe there is an other way to do it.

Thanks,

Romain.