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 met
Guys,
I've noticed a couple places on ignite.apache.org on Download page where
'incubating' version is still pointed.
Could somebody who have write access fix them?
1. "*Download from Maven*" - the sentence "The latest version is
*1.1.0-incubating*."
2. "*Building the Binaries*"
"
# Unpack the s
Vasiliy Sisko created IGNITE-2319:
-
Summary: Inconsistent size of work area on Profile page.
Key: IGNITE-2319
URL: https://issues.apache.org/jira/browse/IGNITE-2319
Project: Ignite
Issue Type
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 29, 2015 at 6:12 AM, Serg
+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 01
Konstantin Boudnik created IGNITE-2318:
--
Summary: Let's start providing more robust checksumming meshanism
Key: IGNITE-2318
URL: https://issues.apache.org/jira/browse/IGNITE-2318
Project: Ignite
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:
> https://git-wip-us.apache.o
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 26, 2015 at 1:22 PM,
Should we think about integrating our .NET/C# edition with Microsoft ASP.NET
SignalR library?
http://www.asp.net/signalr
D.
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 a PR for the issue IGN
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 GMT+03:00 Vladimir Ozerov
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
https://apacheignite.readme.io/docs/osgi-starting-inside-a
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, Hazelc
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, Hazelc
Vladimir Ozerov created IGNITE-2317:
---
Summary: Get rid of lean maps.
Key: IGNITE-2317
URL: https://issues.apache.org/jira/browse/IGNITE-2317
Project: Ignite
Issue Type: Sub-task
C
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 quite a few usages of *F.view* in the project. I
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 performance and correctness. Bette
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 *GridDiscoveryManager
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 co
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 ex
You should download sourcess to work with Tests.
Examples is a part of binary distribution.
On Tue, Dec 29, 2015 at 4:47 PM, Pavel Tupitsyn
wrote:
> 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,
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 be nice to see OSGi example
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 decision on whether to
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 introduce the requirem
+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!
> > >
> > > We have uploaded release candidate to
> > > https://dis
+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 using/testing by the
> communit
+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/
> >
> > This is very important release cont
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 using/testing by the
community and may be for review process as well.
--
Sergey Kozlov
+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 many other import
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: Ini
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 unassign the ticket fr
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 be perfect if someone
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 P
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 any assistance?
>
> Re
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
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
Proje
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
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
Project
38 matches
Mail list logo
