New module

Hello everybody I wan to create a new module to integrate Ignite with Spring data, I was to the developer guide to see if there specific steps to build a module but I only saw the notice about the README and the license, but I have a very silly doubt but I want to do everything perfect, when you cr

[GitHub] ignite pull request: IGNITE-1690 : Re-enabled test.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/753 IGNITE-1690 : Re-enabled test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilantukh/ignite ignite-1690 Alternatively you can review and ap

[GitHub] ignite pull request: IGNITE-1690 testing.

Github user ilantukh closed the pull request at: https://github.com/apache/ignite/pull/746 --- 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 en

Re: Interested in this ticket IGNITE-2344

Hi Saikat, Looks like this ticket was unassigned, so feel free to start on it. Feel free to send your questions here. D. On Tue, May 24, 2016 at 10:34 AM, Saikat Maitra wrote: > Hello, > > I am interested to pick up this ticket and wanted to know if anyone already > started working on it. > >

Re: [apache/ignite] [IGNITE-2929] IgniteContext should not have type parameters (#740)

Folks, The PR looks good to me. There is one concern - even though the type parameters were placed to IgniteContext by mistake, removing them will break backward compatibility. Are we ok with that? Val, can you comment? 2016-05-21 8:32 GMT-07:00 MaBiao : > @agoncharuk

[GitHub] ignite pull request: Ignite 3183

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/752 Ignite 3183 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3183 Alternatively you can review and apply the

Interested in this ticket IGNITE-2344

Hello, I am interested to pick up this ticket and wanted to know if anyone already started working on it. https://issues.apache.org/jira/browse/IGNITE-2344 - WebSessionFilter doesn't support session ID renewal Regards Saikat

[GitHub] ignite pull request: IGNITE-3189 .NET: TestCallJavaService fails o...

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/751 IGNITE-3189 .NET: TestCallJavaService fails on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com/ptupitsyn/ignite ignite-3189 Alternatively

[jira] [Created] (IGNITE-3190) OffHeap cache metrics do not detected get from OffHeap

Vladislav Pyatkov created IGNITE-3190: - Summary: OffHeap cache metrics do not detected get from OffHeap Key: IGNITE-3190 URL: https://issues.apache.org/jira/browse/IGNITE-3190 Project: Ignite

[jira] [Created] (IGNITE-3189) .NET: TestCallJavaService fails on TC

Pavel Tupitsyn created IGNITE-3189: -- Summary: .NET: TestCallJavaService fails on TC Key: IGNITE-3189 URL: https://issues.apache.org/jira/browse/IGNITE-3189 Project: Ignite Issue Type: Test

Re: About web console and web agent

Hi! >> I would like to ask, Web Console and Web Agent module,how to install,config and use? Are the documents related is OK? What are you trying to achieve? If you want to use Web Conosle - you may simply go to GridGain hosted https://console.gridgain.com/ Register and give a try. If you want

Re: Cache metrics return incorrect values

Hi Vlad, In my understanding this should work or implemented this way for OFFHEAP_TIRED cache. CacheMetrics.getCacheEvictions - incremented on every put & get operation because an entry “goes through” heap memory and evicted from there when it’s no longer needed (usually at the end of get or p

About web console and web agent

Hi: I would like to ask, Web Console and Web Agent module,how to install,config and use? Are the documents related is OK? 在 16/5/18 00:23, Alexey Kuznetsov 写道: First version of Web Console merged to ignite-1.6. On Tue, May 17, 2016 at 9:31 PM, Pavel Tupitsyn wrote: All done from .NET sid

Re: Integration with Apache Apex (incubating)

Hi, I just recently started working on this, you can track progress here [1] and of course here [2], we also started a separate thread here [3]. Best regards, Vladisav [1] https://issues.apache.org/jira/browse/IGNITE-3131 [2] https://issues.apache.org/jira/browse/APEXMALHAR-2091 [3] https://mail

[GitHub] ignite pull request: 7.5.23 2941 2942

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/750 7.5.23 2941 2942 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.23-2941-2942 Alternatively you can

Cache metrics return incorrect values

I try to understand how statistics work and fixe some problem. I first case: cache.put(46744, "val 46744"); cache.get(46744); In statistic I see: 2016-05-24 14:19:31 INFO ServerNode:78 - Swap put 0 get 0 (0, 0) entries count 0 2016-05-24 14:19:31 INFO ServerNode:81 - OffHeap put 1 get 0 (0, 0) en

[GitHub] ignite pull request: IGNITE-2865 Continuous query event passed to ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/744 --- 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 enab

Re: Integration with Apache Apex (incubating)

Hello D, I landed on this thread while searching for the Apache Ignite integration with Apex. Is there an update on this topic somewhere that I might missing? Thanks! -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Integration-with-Apache-Apex-incubatin

IgniteConfiguration.gridName is very confusing

Igniters, We have got a TON of questions on gridName property. Everyone thinks that clusters are formed based on the gridName, that is, nodes with the same grid name will join one cluster, and nodes with a different name will be in a separate cluster. I suggest to deprecate this property and add

[jira] [Created] (IGNITE-3188) Binary marshaller doesn't unmarshal a void type

Nikolay Tikhonov created IGNITE-3188: Summary: Binary marshaller doesn't unmarshal a void type Key: IGNITE-3188 URL: https://issues.apache.org/jira/browse/IGNITE-3188 Project: Ignite Issu

[GitHub] ignite pull request: ignite-2620

Github user sboikov closed the pull request at: https://github.com/apache/ignite/pull/738 --- 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 ena

Re: [IGNITE-2323] Improvments for http client

Sure. Thank you Denis. On May 24, 2016 1:00 PM, "Denis Magda" wrote: > Chandresh, > > As I see development of NodeJS integration is presently postponed by the > community and bunch of efforts is needed to make a decision on where to > move with this. > > I would suggest you picking up another ti

Re: [IGNITE-2323] Improvments for http client

Chandresh, As I see development of NodeJS integration is presently postponed by the community and bunch of efforts is needed to make a decision on where to move with this. I would suggest you picking up another ticket for now. — Denis > On May 21, 2016, at 7:24 PM, chandresh pancholi > wrot

Re: Deadlock detection usage

Andrey, thanks for additional details. The doc is updated https://apacheignite.readme.io/docs/transactions#deadlock-detection-in-pessimistic-transactions — Denis > On May 23, 2016, at 2:28 PM, Andr