Integration with RocketMQ

[Roman Shtykh]

Igniters,
Recently I am looking into a new pub/sub messaging Apache incubator project 
called RocketMQ [1], originally developed at Alibaba. And I am thinking about 
implementing a streamer for Ignite.
Do you think it has to be placed under modules/ of Ignite project, or better to 
have it together with other RocketMQ Community Projects [2]? I talked to the 
project's lead -- any approach seems to be ok.
I anticipate quite frequent releases of the project this year (much more 
frequent than Ignite's), and I think it will be easier to release such 
integration updates with the 2nd approach, as soon as a new RocketMQ's (or 
Ignite's) version is available.
Any thoughts?
[1] http://rocketmq.apache.org/[2] https://github.com/rocketmq
Roman

Re: classnames.properties file is not updated and missed in 1.8 release

[Alexey Kuznetsov]

I'm not sure about sources.

But "mvn clean package" should generate
"modules/core/target/classes/META-INF/classnames.properties"

And yes, I think we should also push "fresh" classnames.properties as one
of pre-release steps.

On Tue, Jan 10, 2017 at 7:51 AM, Denis Magda  wrote:

> Committers, especially Anton V. and Vovan,
>
> I’ve been looking at the following ticket [1] and found out that the issue
> happens simply because both
>
> org.apache.ignite.binary.BinaryObjectBuilder
>
> and
>
> org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl
>
> are not added to META-INF/classnames.properties file.
>
> However, when I build the project from scratch I don’t see the file to be
> updated. There is still no entries for BinaryObjectBuilder* classes. Even
> more, if I download 1.8 release there is not META-INF/classnames.properties
> file at all. Did we introduce a bug or change the logic?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-2422 <
> https://issues.apache.org/jira/browse/IGNITE-2422>
>
> —
> Denis




-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

classnames.properties file is not updated and missed in 1.8 release

[Denis Magda]

Committers, especially Anton V. and Vovan,

I’ve been looking at the following ticket [1] and found out that the issue 
happens simply because both 

org.apache.ignite.binary.BinaryObjectBuilder

and

org.apache.ignite.internal.binary.builder.BinaryObjectBuilderImpl

are not added to META-INF/classnames.properties file.

However, when I build the project from scratch I don’t see the file to be 
updated. There is still no entries for BinaryObjectBuilder* classes. Even more, 
if I download 1.8 release there is not META-INF/classnames.properties file at 
all. Did we introduce a bug or change the logic?


[1] https://issues.apache.org/jira/browse/IGNITE-2422 


—
Denis

[GitHub] ignite pull request #1411: IGNITE-2422: Prevent serialization of BinaryObjec...

[dream-x]

GitHub user dream-x opened a pull request:

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

IGNITE-2422: Prevent serialization of BinaryObjectBuilder



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

$ git pull https://github.com/dream-x/ignite ignite-2422

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

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


commit 48059532376a625421b6a2b8e0359f06f1d0d81c
Author: Max Kozlov 
Date:   2017-01-09T23:58:55Z

Add method testSerializeBinaryObjectBuilder() in 
BinaryObjectBuilderAdditionalSelfTest class.

commit 9eb4b4420b5e0fd90f8a923bb096c6ee99b9e9da
Author: Max Kozlov 
Date:   2017-01-10T00:02:56Z

Change method setField(String name, Object val0) for prevent serialization 
BinaryObjectBuilder

commit 9154c568bd2eb478998186a43298e5979fdeb78f
Author: Max Kozlov 
Date:   2017-01-10T00:05:55Z

Delete unused import.




---
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: Adding blog posts to Apache Ignite's blogs list

[Dmitriy Setrakyan]

On Mon, Jan 9, 2017 at 1:18 PM, Shamim  wrote:

> Dimitriy,
>   Glad to see you again. Thank'x a lot to purchase the book ( it was
> unnecessary, we can send you a gift copy of the book), we will be glad to
> hear from you any constructive criticisms and suggestions.
>

You did great work, I was happy to pay for the book :)


>
>

>
> With best regards
>Shamim Ahmed
>
> On 9 янв. 2017 г., at 23:40, Dmitriy Setrakyan 
> wrote:
>
> I just bought the book. Looking forward to reading it.
>
> On Mon, Jan 9, 2017 at 12:18 PM, Shamim  wrote:
>
>> Good evening, Denis,
>> The direct URL of the post is as follows:
>> http://frommyworkshop.blogspot.ru/2016/09/book-high-performa
>> nce-in-memory.html
>>
>> If I will have any new post, I will let you know about it.
>>
>> With best regards
>>Shamim Ahmed
>>
>> > On 9 янв. 2017 г., at 21:48, Denis Magda  wrote:
>> >
>> > Hi Shamim,
>> >
>> > Suddenly I came across your personal blog that has a lot of thoughtful
>> and well-detailed Apache Ignite posts.
>> > http://frommyworkshop.blogspot.ru
>> >
>> > If you don’t mind we will your latest post about the published Ignite
>> book to Ignite’s blog list. BTW, how to get a direct reference to this
>> post? Can you share it with us?
>> > https://ignite.apache.org/blogs.html
>> >
>> > Going forward, could you write a message to the dev list and me every
>> time your write something new. We will make sure to add your posts to
>> Ignite’s blogs list.
>> >
>> > —
>> > Denis
>> >
>>
>
>

SQL query collocated flag

[Valentin Kulichenko]

Folks,

One of the users faced an interesting case [1]. Basically, there is a query
[2] which returns correct result when collocated flag is not set, but if
it's true, several counts for each node is received by the client without
being aggregated. Is this expected? I'm also attaching the test that
reproduces behavior.

Actually, the flag seems to be very confusing and documentation description
[3] doesn't help a lot. I'm reading it and it's not clear what has to be
collocated, what would happen if I incorrectly set the flag to true, etc.
Probably, some examples could help. Can someone elaborate?

[1]
http://apache-ignite-users.70518.x6.nabble.com/NOT-IN-in-ignite-td9861.html
[2] SELECT count(*) as COUNT FROM Person p join table(joinId VARCHAR(50) =
?) i on p.id = i.joinId
[3]
https://apacheignite.readme.io/docs/configuration-parameters#section--sqlfields-and-sqlfieldsquery-configuration-properties

-Val

Re: Hi guys /Artem Schitow/

[Denis Magda]

Hi Artem,

Welcome to the Ignite community! I’ve added you to the contributors list in 
JIRA.

A piece of other relevant information that might be useful to you.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEAL
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup

Once you got familiar and were able to run a few examples, you should pick
a Jira ticket you would like to start on. Send an email to the dev list, so
we can add you as a contributor in Jira.

You can find interesting tickets to get started here:
https://ignite.apache.org/community/contribute.html#pick-ticket

Looking forward to your contributions!

Regards,
Denis


> On Jan 9, 2017, at 12:46 PM, Artem Schitow  wrote:
> 
> Hi guys!
> 
> I would like to join the development of Apache Ignite. I’m Artem Schitow, 
> Russia. I did work with Ignite as a “user” at my previous job at e-commerce 
> firm, and I’m interested in becoming more involved with the community as I 
> find the project useful and unique in its own way.
> 
> I would be grateful for some introductory guidelines and Jira access 
> (username: artem.schitow) and it would be just good if my experience would 
> prove useful to the community in some way. :)
> 
> Thanks in Advance!

Re: Adding blog posts to Apache Ignite's blogs list

[Shamim]

Dimitriy,
  Glad to see you again. Thank'x a lot to purchase the book ( it was 
unnecessary, we can send you a gift copy of the book), we will be glad to hear 
from you any constructive criticisms and suggestions.

With best regards
   Shamim Ahmed

> On 9 янв. 2017 г., at 23:40, Dmitriy Setrakyan  wrote:
> 
> I just bought the book. Looking forward to reading it.
> 
>> On Mon, Jan 9, 2017 at 12:18 PM, Shamim  wrote:
>> Good evening, Denis,
>> The direct URL of the post is as follows:
>> http://frommyworkshop.blogspot.ru/2016/09/book-high-performance-in-memory.html
>> 
>> If I will have any new post, I will let you know about it.
>> 
>> With best regards
>>Shamim Ahmed
>> 
>> > On 9 янв. 2017 г., at 21:48, Denis Magda  wrote:
>> >
>> > Hi Shamim,
>> >
>> > Suddenly I came across your personal blog that has a lot of thoughtful and 
>> > well-detailed Apache Ignite posts.
>> > http://frommyworkshop.blogspot.ru
>> >
>> > If you don’t mind we will your latest post about the published Ignite book 
>> > to Ignite’s blog list. BTW, how to get a direct reference to this post? 
>> > Can you share it with us?
>> > https://ignite.apache.org/blogs.html
>> >
>> > Going forward, could you write a message to the dev list and me every time 
>> > your write something new. We will make sure to add your posts to Ignite’s 
>> > blogs list.
>> >
>> > —
>> > Denis
>> >
> 

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Sally Khudairi]

Thanks, Denis. I'm working on a draft and will send it over for review in the 
next couple of days.
Kind regards,Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]


 
 
  On Mon, Jan 9, 2017 at 13:33, Denis Magda wrote:   Roman, 
perfect! Well done!
*Prachi*, please add Roman’s blog to Apache Ignite’s blogs 
list:https://ignite.apache.org/blogs.html
*Sally*, considering that all the information is already at place is it a good 
time to wrap it up in an Apache official announcement?
—Denis

On Jan 9, 2017, at 1:43 AM, Roman Shtykh  wrote:
Denis, I published a short article on 
https://dzone.com/articles/handling-apache-ignite-cluster-data-via-redis-prot 
-Roman 

On Saturday, December 31, 2016 12:50 AM, Denis Magda  
wrote:
 

 Roman, amazing thanks!
You can use any blogging engine you like. After the blog post is ready notify 
the community and Prachi will send your material to dzone.com and when it’s 
accepted there we will public it on Ignite’s blogging page 
(https://ignite.apache.org/blogs.html). 
As for the format, I would suggest making a quick walk-through guidance 
including code snippets and showing how to connect to the cluster from Python 
or Ruby (whatever you like most) and work with it. You can do something like I 
did for 
PHPhttps://dzone.com/articles/apache-ignite-enables-full-fledged-sql-support-for
—Denis

On Dec 30, 2016, at 4:09 AM, Roman Shtykh  wrote:
Sure, Denis, I can write about Redis protocol support. Can you please instruct 
me about the format and how/where to submit?
Roman


    On Friday, December 30, 2016 8:11 AM, Sally Khudairi  
wrote:


 Boop! Sorry about that...indeed, I wrote Roman's name in my notes next to "1.8 
release manager?" and clearly combined the two.
Apologies for alarming you.
But that is a good hint, Denis 
Cheers,Sally


[From the mobile; please excuse top-posting, spelling/spacing errors, and 
brevity]




  On Thu, Dec 29, 2016 at 17:58, Denis Magda wrote:  Sally, 
looks like you got confused with this

On Dec 29, 2016, at 2:38 PM, Sally Khudairi  wrote:
And thanks in advance, Roman Shtykh, for acting as project spokesperson in your 
role as release manager. Participation from the community at-large is greatly 
appreciated!

Roman have never been a release manager yet. However, this is just a matter of 
time and his interest/intention ;)
—Denis  





   

  

Re: Contributing to Ignite.NET

[Denis Magda]

Great, Sergey thanks! I’ve added you to the contributors list on Ignite’s main 
site.
https://ignite.apache.org/community/resources.html#people 


Pavel, could you add a number of .NET related tickets to this “Pick a Ticket” 
section?
https://ignite.apache.org/community/contribute.html#pick-ticket 


—
Denis

> On Jan 9, 2017, at 4:40 AM, Pavel Tupitsyn  wrote:
> 
> Sergey, I've merged your fix for IGNITE-4412.
> 
> Looking forward to more contributions from you!
> 
> Pavel
> 
> On Thu, Jan 5, 2017 at 8:15 PM, Pavel Tupitsyn  wrote:
> 
>> Hi Sergey,
>> 
>> I've added you to project contributors in Jira.
>> 
>> I can suggest the following .NET tickets to get familiar with the project:
>> 
>> IGNITE-4412 .NET: NLogLoggerTest is not thread safe
>> 
>> IGNITE-3170 .NET: Add user-friendly ToString overrides for public types
>> 
>> IGNITE-1508 .NET: Create common ToString() method
>> 
>> 
>> Let me know if you have any questions.
>> 
>> Thanks,
>> 
>> Pavel.
>> 
>> 
>> On Thu, Jan 5, 2017 at 8:10 PM, Guru Stron 
>> wrote:
>> 
>>> Hi,
>>> 
>>> My name is Sergey, i would like to contribute to Ignite.NET.
>>> Can you please suggest a ticket for me to start. My Jira username is
>>> GuruStron.
>>> 
>> 
>> 

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Prachi Garg]

Roman's blog has been added to the website - https://ignite.apache.org/
blogs.html

-Prachi




On Mon, Jan 9, 2017 at 10:33 AM, Denis Magda  wrote:

> Roman, perfect! Well done!
>
> *Prachi*, please add Roman’s blog to Apache Ignite’s blogs list:
> https://ignite.apache.org/blogs.html
>
> *Sally*, considering that all the information is already at place is it a
> good time to wrap it up in an Apache official announcement?
>
> —
> Denis
>
> On Jan 9, 2017, at 1:43 AM, Roman Shtykh  wrote:
>
> Denis, I published a short article on https://dzone.com/articles/
> handling-apache-ignite-cluster-data-via-redis-prot
>
> -Roman
>
>
> On Saturday, December 31, 2016 12:50 AM, Denis Magda 
> wrote:
>
>
> Roman, amazing thanks!
>
> You can use any blogging engine you like. After the blog post is ready
> notify the community and Prachi will send your material to dzone.com and
> when it’s accepted there we will public it on Ignite’s blogging page (
> https://ignite.apache.org/blogs.html).
>
> As for the format, I would suggest making a quick walk-through guidance
> including code snippets and showing how to connect to the cluster from
> Python or Ruby (whatever you like most) and work with it. You can do
> something like I did for PHP
> https://dzone.com/articles/apache-ignite-enables-full-
> fledged-sql-support-for
>
> —
> Denis
>
> On Dec 30, 2016, at 4:09 AM, Roman Shtykh 
> wrote:
>
> Sure, Denis, I can write about Redis protocol support. Can you please
> instruct me about the format and how/where to submit?
> Roman
>
>
>On Friday, December 30, 2016 8:11 AM, Sally Khudairi 
> wrote:
>
>
> Boop! Sorry about that...indeed, I wrote Roman's name in my notes next to
> "1.8 release manager?" and clearly combined the two.
> Apologies for alarming you.
> But that is a good hint, Denis 
> Cheers,Sally
>
>
> [From the mobile; please excuse top-posting, spelling/spacing errors, and
> brevity]
>
>
>
>
>   On Thu, Dec 29, 2016 at 17:58, Denis Magda wrote:
> Sally, looks like you got confused with this
>
> On Dec 29, 2016, at 2:38 PM, Sally Khudairi  wrote:
> And thanks in advance, Roman Shtykh, for acting as project spokesperson in
> your role as release manager. Participation from the community at-large is
> greatly appreciated!
>
> Roman have never been a release manager yet. However, this is just a
> matter of time and his interest/intention ;)
> —Denis
>
>
>
>
>
>

Hi guys /Artem Schitow/

[Artem Schitow]

Hi guys!

I would like to join the development of Apache Ignite. I’m Artem Schitow, 
Russia. I did work with Ignite as a “user” at my previous job at e-commerce 
firm, and I’m interested in becoming more involved with the community as I find 
the project useful and unique in its own way.

I would be grateful for some introductory guidelines and Jira access (username: 
artem.schitow) and it would be just good if my experience would prove useful to 
the community in some way. :)

Thanks in Advance!

Re: Extend TcpDiscoveryVmIpFinder functionality

[Dmitriy Setrakyan]

On Mon, Jan 9, 2017 at 12:19 PM, Sergey Kozlov  wrote:

> Hi
>
> Thanks Yakov and Vladimir!
>
> In general I'm ok for Yakov's suggestion though a bit not clear why
> discovery by network mask will take long time. Is the discovery spi
> single-threaded and Ignite processes the addresses consequentially?
>

Sergey, I think trying out every address within the mask will take a while.
I like Yakov's suggestion as well.


>
>
> On Mon, Jan 9, 2017 at 2:39 PM, Vladimir Ozerov 
> wrote:
>
> > +1
> >
> > On Mon, Jan 9, 2017 at 2:11 PM, Yakov Zhdanov 
> wrote:
> >
> > > Agree with Vladimir.
> > >
> > > However, this functionality maybe useful in some cases. As far as I
> > > remember we support port range notation, e.g. 127.0.0.1:47500..47509,
> > but
> > > we don't have this for addresses. If we implement this I would suggest
> > the
> > > same approach, e.g 192.168.0.1..5:47500
> > >
> > > Thoughts?
> > >
> > > --Yakov
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Re: Adding blog posts to Apache Ignite's blogs list

[Dmitriy Setrakyan]

I just bought the book. Looking forward to reading it.

On Mon, Jan 9, 2017 at 12:18 PM, Shamim  wrote:

> Good evening, Denis,
> The direct URL of the post is as follows:
> http://frommyworkshop.blogspot.ru/2016/09/book-high-
> performance-in-memory.html
>
> If I will have any new post, I will let you know about it.
>
> With best regards
>Shamim Ahmed
>
> > On 9 янв. 2017 г., at 21:48, Denis Magda  wrote:
> >
> > Hi Shamim,
> >
> > Suddenly I came across your personal blog that has a lot of thoughtful
> and well-detailed Apache Ignite posts.
> > http://frommyworkshop.blogspot.ru
> >
> > If you don’t mind we will your latest post about the published Ignite
> book to Ignite’s blog list. BTW, how to get a direct reference to this
> post? Can you share it with us?
> > https://ignite.apache.org/blogs.html
> >
> > Going forward, could you write a message to the dev list and me every
> time your write something new. We will make sure to add your posts to
> Ignite’s blogs list.
> >
> > —
> > Denis
> >
>

Re: Adding blog posts to Apache Ignite's blogs list

[Shamim]

Good evening, Denis,
The direct URL of the post is as follows:
http://frommyworkshop.blogspot.ru/2016/09/book-high-performance-in-memory.html

If I will have any new post, I will let you know about it. 

With best regards
   Shamim Ahmed

> On 9 янв. 2017 г., at 21:48, Denis Magda  wrote:
> 
> Hi Shamim,
> 
> Suddenly I came across your personal blog that has a lot of thoughtful and 
> well-detailed Apache Ignite posts. 
> http://frommyworkshop.blogspot.ru
> 
> If you don’t mind we will your latest post about the published Ignite book to 
> Ignite’s blog list. BTW, how to get a direct reference to this post? Can you 
> share it with us?
> https://ignite.apache.org/blogs.html
> 
> Going forward, could you write a message to the dev list and me every time 
> your write something new. We will make sure to add your posts to Ignite’s 
> blogs list.
> 
> —
> Denis
> 

Re: Extend TcpDiscoveryVmIpFinder functionality

[Sergey Kozlov]

Hi

Thanks Yakov and Vladimir!

In general I'm ok for Yakov's suggestion though a bit not clear why
discovery by network mask will take long time. Is the discovery spi
single-threaded and Ignite processes the addresses consequentially?


On Mon, Jan 9, 2017 at 2:39 PM, Vladimir Ozerov 
wrote:

> +1
>
> On Mon, Jan 9, 2017 at 2:11 PM, Yakov Zhdanov  wrote:
>
> > Agree with Vladimir.
> >
> > However, this functionality maybe useful in some cases. As far as I
> > remember we support port range notation, e.g. 127.0.0.1:47500..47509,
> but
> > we don't have this for addresses. If we implement this I would suggest
> the
> > same approach, e.g 192.168.0.1..5:47500
> >
> > Thoughts?
> >
> > --Yakov
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[GitHub] ignite pull request #1410: ignite-4499

[agura]

GitHub user agura opened a pull request:

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

ignite-4499



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

$ git pull https://github.com/agura/incubator-ignite ignite-4499

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

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


commit 626f1d5614930bca0ab744a6049e5f83f321d46a
Author: Andrey V. Mashenkov 
Date:   2016-12-23T09:18:07Z

IGNITE-4142: Fixed assertion while update metrics. This closes #1372.

commit 28744f33fb5959ed9728f71e5259d376d7f13569
Author: agura 
Date:   2017-01-09T19:05:21Z

ignite-4499 Drop node from topology in case when connection creation is 
impossible




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

Adding blog posts to Apache Ignite's blogs list

[Denis Magda]

Hi Shamim,

Suddenly I came across your personal blog that has a lot of thoughtful and 
well-detailed Apache Ignite posts. 
http://frommyworkshop.blogspot.ru 

If you don’t mind we will your latest post about the published Ignite book to 
Ignite’s blog list. BTW, how to get a direct reference to this post? Can you 
share it with us?
https://ignite.apache.org/blogs.html

Going forward, could you write a message to the dev list and me every time your 
write something new. We will make sure to add your posts to Ignite’s blogs list.

—
Denis

Re: [ANNOUNCE] Apache Ignite 1.8.0 Released

[Denis Magda]

Roman, perfect! Well done!

*Prachi*, please add Roman’s blog to Apache Ignite’s blogs list:
https://ignite.apache.org/blogs.html 

*Sally*, considering that all the information is already at place is it a good 
time to wrap it up in an Apache official announcement?

—
Denis

> On Jan 9, 2017, at 1:43 AM, Roman Shtykh  wrote:
> 
> Denis, I published a short article on 
> https://dzone.com/articles/handling-apache-ignite-cluster-data-via-redis-prot 
> 
>  
> -Roman
> 
> 
> On Saturday, December 31, 2016 12:50 AM, Denis Magda  
> wrote:
> 
> 
> Roman, amazing thanks!
> 
> You can use any blogging engine you like. After the blog post is ready notify 
> the community and Prachi will send your material to dzone.com 
>  and when it’s accepted there we will public it on 
> Ignite’s blogging page (https://ignite.apache.org/blogs.html 
> ). 
> 
> As for the format, I would suggest making a quick walk-through guidance 
> including code snippets and showing how to connect to the cluster from Python 
> or Ruby (whatever you like most) and work with it. You can do something like 
> I did for PHP
> https://dzone.com/articles/apache-ignite-enables-full-fledged-sql-support-for 
> 
> 
> —
> Denis
> 
>> On Dec 30, 2016, at 4:09 AM, Roman Shtykh > > wrote:
>> 
>> Sure, Denis, I can write about Redis protocol support. Can you please 
>> instruct me about the format and how/where to submit?
>> Roman
>> 
>> 
>>On Friday, December 30, 2016 8:11 AM, Sally Khudairi > > wrote:
>> 
>> 
>> Boop! Sorry about that...indeed, I wrote Roman's name in my notes next to 
>> "1.8 release manager?" and clearly combined the two.
>> Apologies for alarming you.
>> But that is a good hint, Denis 
>> Cheers,Sally
>> 
>> 
>> [From the mobile; please excuse top-posting, spelling/spacing errors, and 
>> brevity]
>> 
>> 
>> 
>> 
>>   On Thu, Dec 29, 2016 at 17:58, Denis Magda> > wrote:  Sally, looks like you got confused with 
>> this
>> 
>> On Dec 29, 2016, at 2:38 PM, Sally Khudairi > > wrote:
>> And thanks in advance, Roman Shtykh, for acting as project spokesperson in 
>> your role as release manager. Participation from the community at-large is 
>> greatly appreciated!
>> 
>> Roman have never been a release manager yet. However, this is just a matter 
>> of time and his interest/intention ;)
>> —Denis  
>> 
> 
> 
> 

[GitHub] ignite pull request #1409: Ignite 4219

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

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

Ignite 4219



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

$ git pull https://github.com/gridgain/apache-ignite ignite-4219

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

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


commit c893da70a9757b16b0799adc8eaa29fa1b03d06e
Author: tledkov-gridgain 
Date:   2016-12-21T11:54:33Z

IGNITE-4399: IGFS: Merged IgfsSecondaryFileSystem and 
IgfsSecondaryFileSystemV2 interfaces. This closes #1346.

commit c5882a85f4e3a1f61723ac54fd92f087684df6da
Author: devozerov 
Date:   2016-12-26T11:15:42Z

Merge branch 'master' into ignite-2.0

commit 7e73d0223a3f09cbe0b7094a2c04bdf9d63ca9be
Author: devozerov 
Date:   2016-12-28T09:54:47Z

Merge branch 'master' into ignite-2.0

commit 7d82d6a06b5e9f1f8cd2909b865e37d46b8da03f
Author: devozerov 
Date:   2016-12-28T09:58:11Z

IGNITE-3875: Introduced separate thread pool for data streamer. This closes 
#1173. This closes #1383.

commit a61b0eaff1817d84c0659e8a7e095f29e22800e1
Author: tledkov-gridgain 
Date:   2016-12-28T11:09:38Z

IGNITE-4405: Hadoop: implemented "readLine" method for HadoopDataInStream 
and HadoopDirectDataInput classes. This closes #1358.

commit 2df39a80d80e2575be61a902ccd48615796fcde9
Author: tledkov-gridgain 
Date:   2016-12-28T13:47:24Z

IGNITE-3961: IGFS: Added IgfsSecondaryFileSystem.affintiy() method. This 
closes #1114. This closes #1252.

commit 2e691d80ea4870c3e7b5b127792b66c920f72c39
Author: tledkov-gridgain 
Date:   2016-12-29T08:00:01Z

IGNITE-4462: IGFS: removed grid name from HadoopIgfsEndpoint. This closes 
#1368.

commit a9b1fc2b3840d47d7c978d9296e8ae6bdeb10be5
Author: tledkov-gridgain 
Date:   2016-12-29T08:07:22Z

IGNITE-4459: Hadoop: weighted planned is default one from now on. This 
closes #1391.

commit 1f743465d6875ef48b1835d03a78a0dbaf339bf6
Author: tledkov-gridgain 
Date:   2016-12-29T08:14:10Z

IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This 
closes #1390.

commit 3e701588f1304e3e86f9d719fb2e311af63a2789
Author: iveselovskiy 
Date:   2017-01-09T17:13:39Z

IGNITE-4219: fixed, added test.




---
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 #1408: IGNITE-4374

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-4374

Check of "Basic JVM Configuration" added.
Link to the tuning article added.
https://apacheignite.readme.io/docs/jvm-and-system-tuning

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

$ git pull https://github.com/daradurvs/ignite ignite-4374

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

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


commit 9cbce4fff70b7ac6a0b23bd8884e6c1f4bfb0f9c
Author: daradurvs 
Date:   2016-12-28T09:02:27Z

ignite-4374: add link to article about performance tuning

commit 2387f3fec5c3b82c82f1bd686704c778e0e4535d
Author: daradurvs 
Date:   2017-01-09T15:26:30Z

ignite-4374: check of Basic JVM Configuration added

commit bc193741acd368bdfcd1221e3506c347eb9739c4
Author: daradurvs 
Date:   2017-01-09T15:55:32Z

ignite-4374: rename GridPerformanceSuggestions to ConfigurationSuggestions

commit b22aa1c4e2ffc374e4bb084217c549aba7e4eb7f
Author: daradurvs 
Date:   2017-01-09T16:33:15Z

ignite-4374: JvmPerformanceSuggestions simplified




---
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 #1407: IGNITE-3430 .NET: Run Ignite transactions via sta...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-3430 .NET: Run Ignite transactions via standard TransactionScope API



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

$ git pull https://github.com/gridgain/apache-ignite ignite-3430

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

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


commit 813092c9c000ba97c233de3c887d0aacd68de953
Author: Pavel Tupitsyn 
Date:   2017-01-09T15:22:23Z

IGNITE-3430 .NET: Run Ignite transactions via standard TransactionScope API




---
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 #1406: IGNITE-3867: ScanQuery ignores pageSize property

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-3867: ScanQuery ignores pageSize property

Fixed.
Test added.

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

$ git pull https://github.com/gridgain/apache-ignite ignite-3867

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

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


commit b6d6e30d73ef9d9950da0448412d3b02ba96d224
Author: Andrey V. Mashenkov 
Date:   2017-01-09T14:13:07Z

Fixed




---
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 #1078: IGNITE-3867: ScanQuery ignores pageSize propertry

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
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: Contributing to Ignite.NET

[Pavel Tupitsyn]

Sergey, I've merged your fix for IGNITE-4412.

Looking forward to more contributions from you!

Pavel

On Thu, Jan 5, 2017 at 8:15 PM, Pavel Tupitsyn  wrote:

> Hi Sergey,
>
> I've added you to project contributors in Jira.
>
> I can suggest the following .NET tickets to get familiar with the project:
>
> IGNITE-4412 .NET: NLogLoggerTest is not thread safe
> 
> IGNITE-3170 .NET: Add user-friendly ToString overrides for public types
> 
> IGNITE-1508 .NET: Create common ToString() method
> 
>
> Let me know if you have any questions.
>
> Thanks,
>
> Pavel.
>
>
> On Thu, Jan 5, 2017 at 8:10 PM, Guru Stron 
> wrote:
>
>> Hi,
>>
>> My name is Sergey, i would like to contribute to Ignite.NET.
>> Can you please suggest a ticket for me to start. My Jira username is
>> GuruStron.
>>
>
>

[GitHub] ignite pull request #1401: IGNITE-4412 fix NLogLoggerTest thread safety issu...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: Extend TcpDiscoveryVmIpFinder functionality

[Vladimir Ozerov]

+1

On Mon, Jan 9, 2017 at 2:11 PM, Yakov Zhdanov  wrote:

> Agree with Vladimir.
>
> However, this functionality maybe useful in some cases. As far as I
> remember we support port range notation, e.g. 127.0.0.1:47500..47509, but
> we don't have this for addresses. If we implement this I would suggest the
> same approach, e.g 192.168.0.1..5:47500
>
> Thoughts?
>
> --Yakov
>

Re: Extend TcpDiscoveryVmIpFinder functionality

[Yakov Zhdanov]

Agree with Vladimir.

However, this functionality maybe useful in some cases. As far as I
remember we support port range notation, e.g. 127.0.0.1:47500..47509, but
we don't have this for addresses. If we implement this I would suggest the
same approach, e.g 192.168.0.1..5:47500

Thoughts?

--Yakov

Re: Extend TcpDiscoveryVmIpFinder functionality

[Vladimir Ozerov]

Sergey,

This could be very dangerous in terms of node startup time. The very first
node in topology will have to scan the whole range trying to find any other
node. It might take significant time not only on Windows, but on Linux
environments as well, especially when some addresses are not available.

On Mon, Jan 9, 2017 at 12:25 PM, Sergey Kozlov  wrote:

> Hi Igniters
>
> I found that TcpDiscoveryVmIpFinder could be improved for Spring
> configuration by introducing new format: *address/mask:port(port range) or
> address/prefix:port(port range)*. From my standpoint it will reduce the
> efforts for ignite deployment and administration.
> For instance if we've a dedicated network for the grid and not able to use
> multicast way we should put each IP to the address list:
>
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.
> TcpDiscoveryVmIpFinder">
> 
>   
> 10.0.0.1:48500
> 10.0.0.2:48500
> 10.0.0.3:48500
> ...
> 10.0.0.100:48500
>   
> 
>   
> 
>
> but can be simplified to
>
> 1) with using of the netmask
>
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.
> TcpDiscoveryVmIpFinder">
> 
>   
> 10.0.0.1/255.255.255.0:48500
>   
> 
>   
> 
>
> 2) with using of the network prefix
>
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.
> TcpDiscoveryVmIpFinder">
> 
>   
> 10.0.0.1/24:48500
>   
> 
>   
> 
>
> Any comments/objections are welcome
>
>
> --
> Sergey Kozlov
>

[GitHub] ignite pull request #1405: Ignite 1.7.6

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 1.7.6



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

$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.6

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

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


commit 626f1d5614930bca0ab744a6049e5f83f321d46a
Author: Andrey V. Mashenkov 
Date:   2016-12-23T09:18:07Z

IGNITE-4142: Fixed assertion while update metrics. This closes #1372.




---
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-4532) .NET: Fix build warnings

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4532:
--

 Summary: .NET: Fix build warnings
 Key: IGNITE-4532
 URL: https://issues.apache.org/jira/browse/IGNITE-4532
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
Priority: Minor
 Fix For: 2.0


There are ~70 warnings in VS 2015 after build.



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

Extend TcpDiscoveryVmIpFinder functionality

[Sergey Kozlov]

Hi Igniters

I found that TcpDiscoveryVmIpFinder could be improved for Spring
configuration by introducing new format: *address/mask:port(port range) or
address/prefix:port(port range)*. From my standpoint it will reduce the
efforts for ignite deployment and administration.
For instance if we've a dedicated network for the grid and not able to use
multicast way we should put each IP to the address list:


  

  
10.0.0.1:48500
10.0.0.2:48500
10.0.0.3:48500
...
10.0.0.100:48500
  

  


but can be simplified to

1) with using of the netmask


  

  
10.0.0.1/255.255.255.0:48500
  

  


2) with using of the network prefix


  

  
10.0.0.1/24:48500
  

  


Any comments/objections are welcome


-- 
Sergey Kozlov

[jira] [Created] (IGNITE-4531) Update DML operation not working for QuerySQLField with name

[David Albrecht (JIRA)]

David Albrecht created IGNITE-4531:
--

 Summary: Update DML operation not working for QuerySQLField with 
name
 Key: IGNITE-4531
 URL: https://issues.apache.org/jira/browse/IGNITE-4531
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: David Albrecht
Priority: Critical


After putting a java class Operation with

@QuerySqlField(name = "operationNumber", index = true)
private String mOperationNumber;

in the cache. Via debug console I can see the following fields:

_val:

Operation [... ,mUuid=FF42930B6D3242B5A0B9D631E017027E, mOperationNumber = 
0010, ...]

and a column named: OPERATIONNUMBER with value 0010.

When I use 
{code}
UPDATE Operation set operationNumber =  ? WHERE mUuid =  ? 
{code}

with the arguments

[SCHEDULED, FF42930B6D3242B5A0B9D631E017027E]

I can see the following values:

Operation [... ,mUuid=FF42930B6D3242B5A0B9D631E017027E, mOperationNumber = 
0010, operationNumber=SCHEDULED, ...]

and a column named: OPERATIONNUMBER with value 0010.

So the column 'OPERATIONNUMBER' and the field 'mOperationNumber' is not updated.





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

Re: IGNITE-4487 - NPE on query execution

[Alexey Goncharuk]

Alexander,

I left my comments in the ticket.

2017-01-06 20:35 GMT+03:00 Denis Magda :

> Thanks Alexander.
>
> Someone will review and merge your changes in the nearest time. Alex G.,
> can you do that?
>
> —
> Denis
>
> > On Jan 6, 2017, at 5:07 AM, Александр Меньшиков 
> wrote:
> >
> > http://ci.ignite.apache.org/project.html?projectId=IgniteTests&tab=
> projectOverview&branch_IgniteTests=pull%2F1388%2Fmerge
> >
> > There are overview of tests. It seems okay. A little unclear because
> there
> > are tests which  failed also in master branch.
> >
> > 2016-12-29 19:49 GMT+03:00 Denis Magda :
> >
> >> Alexander, thanks.
> >>
> >> Please move the ticket from “open” into “patch available” state in JIRA
> >> and run the tests on TeamCity. Refer to the details covered there
> >> https://cwiki.apache.org/confluence/display/IGNITE/How+
> >> to+Contribute#HowtoContribute-1.CreateGitHubpull-request <
> >> https://cwiki.apache.org/confluence/display/IGNITE/How+
> >> to+Contribute#HowtoContribute-1.CreateGitHubpull-request>
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 29, 2016, at 3:45 AM, Александр Меньшиков  >
> >> wrote:
> >>>
> >>> Alexey, I'm already make pull request where throw exception in that
> >> place.
> >>>
> >>> https://github.com/apache/ignite/pull/1388/commits
> >>>
> >>> 2016-12-29 11:16 GMT+03:00 Alexey Goncharuk <
> alexey.goncha...@gmail.com
> >>> :
> >>>
>  I think that If fallbacks(...) returns an empty nodes collection, then
> >> we
>  should fail with an exception.
> 
>  2016-12-28 22:06 GMT+03:00 Denis Magda :
> 
> > Alexander, added you to the contributors list. Please check that you
> >> can
> > assign the ticket on yourself.
> >
> > —
> > Denis
> >
> >> On Dec 28, 2016, at 2:15 AM, Александр Меньшиков <
> >> sharple...@gmail.com
> >
> > wrote:
> >>
> >>
> >> Username: sharpler
> >>
> >> Full Name: Alexander Menshikov
> >>
> >>
> >>
> >> 2016-12-27 22:57 GMT+03:00 Denis Magda  > dma...@apache.org>>:
> >> Alexander,
> >>
> >> I need to know your JIRA ID in order to add you to the contributors
>  list.
> >>
> >> As for your questions, this situation might be caused by the race
> when
>  a
> > cache is being stopped and there are still scan queries running in
> > parallel. So, in general it’s not about data loss.
> >>
> >> Sam, Alex G., could you share your thoughts in regards to the proper
>  fix?
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 26, 2016, at 2:43 AM, Александр Меньшиков <
>  sharple...@gmail.com
> > > wrote:
> >>>
> >>> Hello everyone.
> >>>
> >>> I want to pick up *https://issues.apache.org/
> jira/browse/IGNITE-4487
>  <
> > https://issues.apache.org/jira/browse/IGNITE-4487>
> >>>  > https://issues.apache.org/jira/browse/IGNITE-4487>>* as my
> >>> first issue.
> >>>
> >>> Please add me as contributor.
> >>>
> >>> I already found that: in inner class
> >>> 'GridCacheQueryAdapter.ScanQueryFallbackClosableIterator' in
> > constructor is
> >>> called with method 'init()', but method 'init()' cannot be called
>  with
> > an
> >>> empty field 'nodes'. In source code it looks like:
> >>>
> >>> private ScanQueryFallbackClosableIterator(int part,
> > GridCacheQueryAdapter
> >>> qry,
> >>>  GridCacheQueryManager qryMgr, GridCacheContext cctx) {
> >>>  this.qry = qry;
> >>>  this.qryMgr = qryMgr;
> >>>  this.cctx = cctx;
> >>>  this.part = part;
> >>>
> >>>  nodes = fallbacks(cctx.discovery().topologyVersionEx());
> >>>  // !!! Here nodes.isEmpty()==true, and init() will fail in
> > the
> >>> future. !!!
> >>>  init();
> >>>  }
> >>>
> >>> I can fix it by adding some check in code, but i must know what
> > behavior
> >>> are best in this case? As I understand it, the list of nodes is
> empty
> > if
> >>> there are no nodes with the current partition, which means data
> loss,
> > and
> >>> either need to return a meaningful exception, or ignore this
> > situation. But
> >>> maybe I missed something.
> >>
> >>
> >
> >
> 
> >>
> >>
>
>