[GitHub] ignite pull request: Created a property to create the caches autom...

GitHub user brunoml opened a pull request: https://github.com/apache/ignite/pull/388 Created a property to create the caches automatically for hibernate Created a property to create the caches automatically for hibernadefault is true. This is the default behavior for ehCache,

Re: Providing an example as part of contribution

Agree that every new feature should have documentation. As far as OSGI, Raul did create the documentation on readme: https://apacheignite.readme.io/docs/osgi-installation-in-karaf https://apacheignite.readme.io/docs/osgi-supported-modules

Re: IGNITE-944 HTTP REST log command doesn't work

Thank you Denis !!! Regards Saikat On Tue, Dec 29, 2015 at 3:02 PM, Denis Magda wrote: > Hi Saikat, thanks! > > I've reviewed your changes and left my review notes in JIRA. > > Regards, > Denis > > > On 12/29/2015 6:35 AM, Saikat Maitra wrote: > >> Hi, >> >> I have raised

Re: GridFunc.view

I think this ticket should also describe examples of how to remove these GridFunc methods. For example, what is an alternative code for GridFunc.veiw(Collection) method? D. On Tue, Dec 29, 2015 at 6:12 AM, Sergi Vladykin wrote: > Cool :) > > Sergi > > 2015-12-29 17:08

[GitHub] ignite pull request: Created a property to create the caches autom...

GitHub user brunoml opened a pull request: https://github.com/apache/ignite/pull/389 Created a property to create the caches automatically for hibernate Created a property to create the caches automatically for hibernadefault is true. This is the default behavior for ehCache,

Re: ignite is not listed among Apache projects

IIRC INFRA doesn't need to be involved - doap discovery is an automatic thing. Just recently same oddity was discovered in Groovy as well - nice catch Raul! Cos On Tue, Dec 29, 2015 at 01:59PM, Dmitriy Setrakyan wrote: > Finally got to it. > > Here is the doap file: >

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 [binding] sha1 checksum is correct signature is correct RAT is clean I can build the binary release from the source code. I have bumped up IGNITE-1656 to be fixed in the next release so we can start supplying real checksums instead of the toyish md5's Thanks! Cos On Tue, Dec 29, 2015 at

Re: GridFunc.view

Responded in jira. Sergi 2015-12-29 21:10 GMT+03:00 Dmitriy Setrakyan : > I think this ticket should also describe examples of how to remove these > GridFunc methods. For example, what is an alternative code for > GridFunc.veiw(Collection) method? > > D. > > On Tue, Dec

ASP.NET SignalR?

Should we think about integrating our .NET/C# edition with Microsoft ASP.NET SignalR library? http://www.asp.net/signalr D.

Re: ignite is not listed among Apache projects

Finally got to it. Here is the doap file: https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob;f=doap_Ignite.rdf;hb=HEAD INFRA ticket to track: https://issues.apache.org/jira/browse/INFRA-11010 D. On Thu, Nov 26, 2015 at 7:53 AM, Raul Kripalani wrote: > On Thu, Nov

Incorrect setter method

Hello. I found in IgniteConfiguration incorrectly named pair of getter and setter methods: Get method is: getMarshallerCacheThreadPoolSize Set method is: setMarshallerCachePoolSize I think we should to deprecate setMarshallerCachePoolSize method and create new setMarshallerCacheThreadPoolSize

[jira] [Created] (IGNITE-2315) GridSpinReadWriteLock doesn't give any performance benefit

Vladimir Ozerov created IGNITE-2315: --- Summary: GridSpinReadWriteLock doesn't give any performance benefit Key: IGNITE-2315 URL: https://issues.apache.org/jira/browse/IGNITE-2315 Project: Ignite

[jira] [Created] (IGNITE-2316) Replace GridSpinBusyLock with improved version of GridStripedSpinBusyLock

Vladimir Ozerov created IGNITE-2316: --- Summary: Replace GridSpinBusyLock with improved version of GridStripedSpinBusyLock Key: IGNITE-2316 URL: https://issues.apache.org/jira/browse/IGNITE-2316

Re: IGNITE-944 HTTP REST log command doesn't work

Hi Saikat, thanks! I've reviewed your changes and left my review notes in JIRA. Regards, Denis On 12/29/2015 6:35 AM, Saikat Maitra wrote: Hi, I have raised a PR for the issue IGNITE-944 Http Rest command doesn't work. https://github.com/apache/ignite/pull/383 Can someone please review the

Re: Abandoned ticket: Implement IgniteStormStreamer to stream data from Apache Storm

Hi Denis, I am really sorry for replying late. I was occupied with office work lately. Can someone from community pick this up and finish? Thanks On Fri, Dec 25, 2015 at 4:23 PM, Denis Magda wrote: > HI Chandresh, > > Do you have any progress on the ticket or do you need

Re: Abandoned ticket: Implement IgniteStormStreamer to stream data from Apache Storm

Hi Chandresh, Thanks for letting us know! I'll unassign the ticket from you then. Igniters, is anyone interested in picking up and finishing this task? It would be perfect if someone who did the other streamer-related integrations will take care of this. Regards, Denis On 12/29/2015 12:40

[jira] [Created] (IGNITE-2314) Evaluate MPSC queue implementation from Dmitry Vyukov in GridNioServer

Vladimir Ozerov created IGNITE-2314: --- Summary: Evaluate MPSC queue implementation from Dmitry Vyukov in GridNioServer Key: IGNITE-2314 URL: https://issues.apache.org/jira/browse/IGNITE-2314

Re: Providing an example as part of contribution

I suggest no rules here. Let's take the decision on whether to add example or not relying on what functionality is being added. --Yakov 2015-12-29 16:21 GMT+03:00 Sergey Kozlov : > Hi > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > I propose to

Re: Providing an example as part of contribution

I do not mean that adding an example should be the mandatory rule for every new feature but only if make sense (e.g. new package in org.apache.ignite.* introduced). Moreover from my standpoint every new feature should properly presented on readme.io as well. It will reduce time which we (and the

Re: GridFunc.view

Cool :) Sergi 2015-12-29 17:08 GMT+03:00 Vladimir Ozerov : > I created ticket for this several days ago: > https://issues.apache.org/jira/browse/IGNITE-2263 > > On Tue, Dec 29, 2015 at 5:05 PM, Sergi Vladykin > wrote: > > > Guys, > > > > We have

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 (binding) On Tue, Dec 29, 2015 at 4:17 PM, 姜 为 wrote: > +1 nice job! > > > 在 2015年12月29日，下午6:54，Anton Vinogradov 写道： > > > > Dear Sirs! > > > > We have uploaded release candidate to > > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ > >

Re: Providing an example as part of contribution

This should be at least discussable for each new feature/functionalitiy. It would be nice to see OSGi example at this release. It's still riddle for me what our OSGi modules do. On Tue, Dec 29, 2015 at 4:41 PM, Yakov Zhdanov wrote: > I suggest no rules here. Let's take the

Re: Providing an example as part of contribution

+100500 On Tue, Dec 29, 2015 at 4:21 PM, Sergey Kozlov wrote: > Hi > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > > I propose to introduce the requirement to add an example for new > features/functionalities. It will make easier further

GridFunc.view

Guys, We have quite a few usages of *F.view* in the project. I believe this thing is usually harmful for performance and correctness. Better thing would look like: *Collection filter(Collection src, CollectionFactory dstFactory, IgnitePredicate p)* For example it is used in

Re: Abandoned ticket: Implement IgniteStormStreamer to stream data from Apache Storm

Roman, perfect! Please assign the ticket on yourself then. -- Denis On 12/29/2015 1:14 PM, Roman Shtykh wrote: Denis, I can probably do it next week. -Roman On Tuesday, December 29, 2015 6:45 PM, Denis Magda wrote: Hi Chandresh, Thanks for letting us know! I'll

Re: Providing an example as part of contribution

I do not see too much of a difference between examples and tests. You can usually see how a feature works from a proper test. On Tue, Dec 29, 2015 at 4:46 PM, Anton Vinogradov wrote: > This should be at least discussable for each new feature/functionalitiy. > It would

Re: Abandoned ticket: Implement IgniteStormStreamer to stream data from Apache Storm

Denis, I can probably do it next week. -Roman On Tuesday, December 29, 2015 6:45 PM, Denis Magda wrote: Hi Chandresh, Thanks for letting us know! I'll unassign the ticket from you then. Igniters, is anyone interested in picking up and finishing this task? It would

[VOTE] Apache Ignite 1.5.0.final RC3

Dear Sirs! We have uploaded release candidate to https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ This is very important release containing initial versions of Ignite.NET and Ignite C++ and many other important features. Tag name is 1.5.0.final-rc3 1.5.0 changes: * Ignite.NET:

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 nice job! > 在 2015年12月29日，下午6:54，Anton Vinogradov 写道： > > Dear Sirs! > > We have uploaded release candidate to > https://dist.apache.org/repos/dist/dev/ignite/1.5.0.final-rc3/ > > This is very important release containing initial versions of Ignite.NET > and Ignite C++ and

Re: [VOTE] Apache Ignite 1.5.0.final RC3

+1 (binding) On Tue, Dec 29, 2015 at 4:23 PM, Anton Vinogradov wrote: > +1 (binding) > > On Tue, Dec 29, 2015 at 4:17 PM, 姜 为 wrote: > > > +1 nice job! > > > > > 在 2015年12月29日，下午6:54，Anton Vinogradov 写道： > > > > > > Dear Sirs! >

Re: GridFunc.view

I created ticket for this several days ago: https://issues.apache.org/jira/browse/IGNITE-2263 On Tue, Dec 29, 2015 at 5:05 PM, Sergi Vladykin wrote: > Guys, > > We have quite a few usages of *F.view* in the project. I believe this thing > is usually harmful for

Re: Providing an example as part of contribution

Agree with Sergey, such a rule should be added to the to-do list of a contributor and to the check-list of reviewers. However, this must be an optional rule cause it's obvious that there is no sense to provide an example for every kind of functionality. In regards to OSGi I would add both an