Capacity Planning - Calculating Memory Usage

2016-12-12 Thread Alexandr Kuramshin 
Hello, Igniters,

I'd like to represent updated article [1] about the subject.

And I'll very appreciate your comments and questions about it.

Please review.

[1] http://apacheignite.gridgain.org/docs/capacity-planning

-- 
Thanks,
Alexandr Kuramshin

[jira] [Created] (IGNITE-4417) OptimizedMarshaller: show property path causing ClassNotFoundException

2016-12-12 Thread Alexandr Kuramshin (JIRA) 
Alexandr Kuramshin created IGNITE-4417:
--

 Summary: OptimizedMarshaller: show property path causing 
ClassNotFoundException
 Key: IGNITE-4417
 URL: https://issues.apache.org/jira/browse/IGNITE-4417
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Alexandr Kuramshin
Priority: Minor


When OptimizedMarshaller could not unmarshal an object on remote side by cause 
of ClassNotFoundException, then IgniteCheckedException is thrown.

We could see in stack trace the class loader toString() value and the name of 
the class which was not found. This information is insufficient.

We should also know which field or property of an object causes 
ClassNotFoundException. And, if this object contains inside another object, we 
should know the type of this object and its field or property as well.

For example, IgniteCheckedException: Failed to unmarshal an object ClassName1 
root.ClassName2 fieldName2.ClassName3 propName3. Given class loader: 
classLoaderToString.



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

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-12 Thread Denis Magda 
Sergey K., Anton,

Please double check that we met all the requirements from this page during
the release
https://maven.apache.org/guides/mini/guide-central-repository-upload.html

If somethings was missed the artifacts wouldn't be uploaded to Maven
Central automatically.

--
Denis


On Mon, Dec 12, 2016 at 4:15 PM, Dmitriy Setrakyan 
wrote:

> On Mon, Dec 12, 2016 at 4:08 PM, Konstantin Boudnik 
> wrote:
>
> > I don't think INFRA has any control of how something is pushed into Maven
> > central.
>
>
> But isn't INFRA responsible to ensure that the mirror between apache and
> maven central works correctly?
>

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-12 Thread Denis Magda 

> On Dec 12, 2016, at 4:08 PM, Konstantin Boudnik  wrote:
> 
> Interestingly enough, looking thought the artifacts in Maven, I see
> a whole bunch of the component that are pulled from the latest releases yet
> are presented in the Maven. Say geospacial is only published up to 1.2.0, etc.

It looks weird to me as well. Could you start a separate discussion on the dev 
list in order to trigger attention of the guys who usually take care about 
Ignite’s build system?

—
Denis

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-12 Thread Dmitriy Setrakyan 
On Mon, Dec 12, 2016 at 4:08 PM, Konstantin Boudnik  wrote:

> I don't think INFRA has any control of how something is pushed into Maven
> central.


But isn't INFRA responsible to ensure that the mirror between apache and
maven central works correctly?

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-12 Thread Konstantin Boudnik 
I don't think INFRA has any control of how something is pushed into Maven
central. Interestingly enough, looking thought the artifacts in Maven, I see
a whole bunch of the component that are pulled from the latest releases yet
are presented in the Maven. Say geospacial is only published up to 1.2.0, etc.

Looks like some house-cleaning needs to be done.
  Cos

On Mon, Dec 12, 2016 at 12:42PM, Denis Magda wrote:
>Cos, Roman S.,
>Is there any hint on or some other way on how we can get attention of
>Apache Infra team to this issue?
>https://issues.apache.org/jira/browse/INFRA-13073
>a**
>Denis
> 
>  On Dec 10, 2016, at 7:45 AM, Denis Magda  wrote:
>  Created an INFRA ticket to double check that this is not an
>  infrastructure issue
>  https://issues.apache.org/jira/browse/INFRA-13073
>  
>    >
> 
>  Sergey, Anton, please keep an eye on it.
> 
>  a**
>  Denis
> 
>On Dec 10, 2016, at 6:49 AM, Denis Magda  wrote:
> 
>Well, thanks for pointing out to this.
> 
>Sergey, looks like you missed something at some releasing phase. If I
>create a project from 1.8 examples then Maven cana**t locate binaries
>for 1.8.0. Please fix this ASAP.
> 
>a**
>Denis
> 
>  On Dec 10, 2016, at 3:57 AM, ae**c,**c,**@163 <18624049...@163.com>
>  wrote:
> 
>  Hi:
> 
>  http://repo.maven.apache.org/maven2/org/apache/ignite
> 
>  the site above, not updated?
> 
>  aa*" 2016/12/9 22:06, Sergey Kozlov aa**e**:
> 
>Hi
> 
>Maven repository has been released.
> 
>
> https://repository.apache.org/content/repositories/releases/org/apache/ignite/
> 
>On Fri, Dec 9, 2016 at 4:41 PM, ae**c,**c,**@163
><18624049...@163.com> wrote:
> 
>  maven repo is not updated?
> 
>  aa*" 2016/12/9 21:37, D-*N*D-uD- 1/2D-,N* D- N*D-+-D-DEGD--oD-
>  3/4D-^2D-DEG aa**e**:
> 
>Hi,
> 
>Update notifier for 1.7.0 shows that version is up to date.
>Could anybody
>fix it please?
> 
>
> +--+
> 
>  Ignite ver. 1.7.0#20160801-sha1:383273e3f6
>  6f702de2482466dce954d570a8ccf2
>  
> +---
>  ---+
> 
>...
> 
>[16:32:54,180][INFO ][main][GridDiscoveryManager] Topology
>snapshot
>[ver=1,
>servers=1, clients=0, CPUs=4, heap=1.0GB]
>[16:33:03,833][INFO
>][ignite-update-notifier-timer][GridUpdateNotifier]
>Your version is up to date.
> 
>--
>Thanks,
>Ksenia
> 
>On Fri, Dec 9, 2016 at 4:14 PM, Pavel Tupitsyn
>
>wrote:
> 
>I've updated the site, there were commented parts on Download
>page from
> 
>  Denis, so that was easy :)
>  Main and News pages also updated.
> 
>  Just a reminder - any committer can update the site, just
>  modify files in
>  SVN, and changes will appear online:
>  https://svn.apache.org/repos/asf/ignite/site/trunk
> 
>  On Fri, Dec 9, 2016 at 1:07 PM, Vladimir Ozerov
>  
>  wrote:
> 
>  Denis,
> 
>Release has been propagated to mirrors, so you can go
>ahead with site
>update.
> 
>Vladimir.
> 
>On Fri, Dec 9, 2016 at 1:28 AM, Denis Magda
> wrote:
> 
>Great, thanks!
> 
>  Released all the docs (Java, .NET, C++, etc.) and update
>  the site
>  partially.
> 
>  I cana**t go ahead and update the downloads page [1] on
>  the site because
> 
>the
> 
>  binaries and sources havena**t been uploaded yet. I get
>  404 error every
> 
>time
> 
>  I try to download one of the below.
>  
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip
>  <
>  
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip>
>

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Denis Magda 
Cos,

> The fact that some of the PMC members here still consider
> themselves first as an employee of company X and only then the as a member of
> Ignite PMC

I consider myself as a free son of the Earth who lives his life the way he 
likes :) The rest is of the same priority.

Well, the whole point of my previous reply is that no matter who you’re and who 
pays you it’s, eventually, up to you where and how to go.
 
—
Denis

> On Dec 12, 2016, at 3:37 PM, Konstantin Boudnik  wrote:
> 
> On Mon, Dec 12, 2016 at 12:12PM, Denis Magda wrote:
>> Denis Magda
>> 
>> 
>> Regardless of the fact that I’m a GridGain employee and that GridGain still
>> represents the majority of our community, I would truly like to make our
> 
> One's affiliation is mostly the fact of one's biography and quite irrelevant
> for the Foundation. The fact that some of the PMC members here still consider
> themselves first as an employee of company X and only then the as a member of
> Ignite PMC is a strong indication that we need to revisit some of the lessons
> from the incubation. Without a solid separation of church and the state,
> errr  the project and where the paycheck is coming from - all the yearning
> for "diversity" is just a wishful thinking.
> 
> Cos
> 
>> community more diversified and transparent and less dependent of GridGain.
>> Being a PMC chair will motivate me to learn even more about Apache
>> processes, principles and leverage the overall knowledge and fully relying
>> on your support and experience of other open source project move our
>> community to the diversified future.
>> 
>> —
>> Denis
>> 
>>> On Dec 10, 2016, at 12:24 PM, Dmitriy Setrakyan  
>>> wrote:
>>> 
>>> According to the discussion on the dev list [1], the following candidates
>>> were proposed for the Apache Ignite PMC Chair position:
>>> 
>>> Vladimir Ozerov
>>> Konstantin Boudnik
>>> Valentin Kulichenko
>>> Denis Magda
>>> Branko Čibej
>>> 
>>> The vote is taking place on the dev list, however only votes from Apache
>>> Ignite PMC members will be considered as binding.
>>> 
>>> *Note that this is not +1 or -1 vote. Please reply to this email specifying
>>> the name of your preferred candidate for the Ignite PMC chair position
>>> (feel free to explain why).*
>>> 
>>> The vote will go for 72 hours. Candidate who gets the most amount of votes
>>> (not the majority) will be elected.
>>> 
>>> Note, that I specifically removed my name from the list, because the whole
>>> point is to rotate a PMC chair, and not to reelect one.
>>> 
>>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-PMC-Chair-
>>> rotation-time-td11941.html
>>

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Konstantin Boudnik 
On Mon, Dec 12, 2016 at 12:12PM, Denis Magda wrote:
> Denis Magda
> 
> 
> Regardless of the fact that I’m a GridGain employee and that GridGain still
> represents the majority of our community, I would truly like to make our

One's affiliation is mostly the fact of one's biography and quite irrelevant
for the Foundation. The fact that some of the PMC members here still consider
themselves first as an employee of company X and only then the as a member of
Ignite PMC is a strong indication that we need to revisit some of the lessons
from the incubation. Without a solid separation of church and the state,
errr  the project and where the paycheck is coming from - all the yearning
for "diversity" is just a wishful thinking.

Cos

> community more diversified and transparent and less dependent of GridGain.
> Being a PMC chair will motivate me to learn even more about Apache
> processes, principles and leverage the overall knowledge and fully relying
> on your support and experience of other open source project move our
> community to the diversified future.
> 
> —
> Denis
> 
> > On Dec 10, 2016, at 12:24 PM, Dmitriy Setrakyan  
> > wrote:
> > 
> > According to the discussion on the dev list [1], the following candidates
> > were proposed for the Apache Ignite PMC Chair position:
> > 
> > Vladimir Ozerov
> > Konstantin Boudnik
> > Valentin Kulichenko
> > Denis Magda
> > Branko Čibej
> > 
> > The vote is taking place on the dev list, however only votes from Apache
> > Ignite PMC members will be considered as binding.
> > 
> > *Note that this is not +1 or -1 vote. Please reply to this email specifying
> > the name of your preferred candidate for the Ignite PMC chair position
> > (feel free to explain why).*
> > 
> > The vote will go for 72 hours. Candidate who gets the most amount of votes
> > (not the majority) will be elected.
> > 
> > Note, that I specifically removed my name from the list, because the whole
> > point is to rotate a PMC chair, and not to reelect one.
> > 
> > [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-PMC-Chair-
> > rotation-time-td11941.html
>

Re: affinityCall in one distributed transaction

2016-12-12 Thread Dmitriy Setrakyan 
Anton,

Looking at this sequence, I don't see any way of achieving it other than
enrolling all transactions into one JTA transaction. If you seen another
way, can you please suggest it here?

D.

On Sat, Dec 10, 2016 at 2:07 PM, Антон Чураев  wrote:

> Dmitriy, it's ok
>
> To be abstract simple business transaction for execution payment
> (preparation done before)  from the card looks like:
> 1) Create a payment document (cache API);
> 2) Write-off funds from the payer's card;
> 2.1) Change in register #1 (cache API);
> 2.2) Change in register #2 (cache API);
> 2.3) Change in register #... (cache API);
> 2.4) Change limits of card (cache API);
> 3) Payment to service provider;
> 3.1) Change in the balance of business unit having the contract with payer
> (cache API);
> 3.2) Change in the balance of business unit having the contract with
> provider (cache API);
> 3.3) Change in the balance of the account (cache API);
> 3.4.1) Some change in registers... (cache API);
> 3.4.2) ...;
> 3.3) ...
> 3.4) Invoke provider's API for billing payment of payer;
> 4) Formation of financial statements (it's possible to implement off-line -
> in other transational)
> 4.1) ...
> 4.2) ...
>
> And all steps have been designed into separate microservices. And, of
> course, it have been designed via asynchronous transport.
> On the other hand it seems to be that implementation of coordination of
> 10-20 local transactions is not a good idea
>
> 2016-12-10 23:30 GMT+03:00 Dmitriy Setrakyan :
>
> > Anton,
> >
> > Thanks for the explanation. I am sorry to keep asking questions on this.
> > Can you change your example to include concrete Ignite calls on Compute
> or
> > Cache APIs (or other APIs)? I am still struggling to understand the
> > boundaries between business and Ignite logic.
> >
> > D.
> >
> > On Sat, Dec 10, 2016 at 5:46 AM, Антон Чураев 
> > wrote:
> >
> > > For example:
> > > 1) Front-end sends a request to perform a complex transaction.
> > > 2) Some application (like a business transactional coordinator)
> receives
> > > message via asynchronous transport. This application implements logic
> of
> > > calling different services sequentially or in parallel via asynchronous
> > > transport.
> > > 3) Each service implement some little changes in a cache.
> > >
> > > Or:
> > > 1) Front-end sends a request to perform a complex transaction.
> > > 2) This transaction is implemented in microservice architecture (large
> > > number microservices + asynchronous transport).
> > > 3) Each microservice implement some little changes in a cache.
> > >
> > > I think it is possible to implement distributed transactional using XA
> > > coordinator outside Ignite and local transaction in each service. But
> its
> > > cost may be unacceptable especially in the case of using a large number
> > of
> > > services.
> > >
> > > I think distributed transaction inside Ignite could be useful also for
> > > using multiple ComputeTask in one transaction.
> > >
> > > 2016-12-09 21:45 GMT+03:00 Dmitriy Setrakyan :
> > >
> > > > Sounds like you need a centralized JTA server for this type of
> purpose,
> > > no?
> > > > In that case, Ignite transactions can already merge into ongoing JTA
> > > > transactions.
> > > >
> > > > I would prefer to see a distributed flow of events to fully
> understand
> > > the
> > > > issue. For example,
> > > >
> > > > Client
> > > >   - start transaction
> > > >   - send compute
> > > >
> > > > Server
> > > >   - receive compute
> > > >   - execute ...
> > > >   - execute ...
> > > >
> > > > etc.
> > > >
> > > > D.
> > > >
> > > > On Fri, Dec 9, 2016 at 1:26 AM, Антон Чураев 
> > > wrote:
> > > >
> > > > > In some cases it is necessary to implement a transaction processing
> > > logic
> > > > > in several different application servers. In this case, working
> with
> > > > Ignite
> > > > > cache will be performed within the various applications. But all
> > these
> > > > > changes must be made within the same distributed transaction.
> > > > >
> > > > > In my opinion this will require context transfer between the
> threads
> > > > within
> > > > > a single node or multiple Ignite nodes.
> > > > >
> > > > > 2016-12-08 12:53 GMT+03:00 Alexei Scherbakov <
> > > > alexey.scherbak...@gmail.com
> > > > > >:
> > > > >
> > > > > > Hi.
> > > > > >
> > > > > > It's unclear from your description what are you trying to
> achieve.
> > > > > >
> > > > > > AffinityCall is unicast and wil be send to single node.
> > > > > >
> > > > > > To parallelise task among the cluster I would recommend to use
> > > compute
> > > > > task
> > > > > > API [1]
> > > > > >
> > > > > > But the task execution is not transactional. Nevertheless, each
> job
> > > > > > triggered by task can use it's own local transaction.
> > > > > >
> > > > > > And please explain, why can't you use a generic Ignite
> transaction
> > > for
> > > > > you
> > > >

Re: Rework Sql Queries use case to SQL Grid one

2016-12-12 Thread Dmitriy Setrakyan 
Denis, can you sketch the SQL Grid diagram and take a picture? This way we
can have a designer draw it out.

On Mon, Dec 12, 2016 at 12:47 PM, Denis Magda  wrote:

> Igniters,
>
> It’s time to update SQL queries use case page [1] to SQL Grid one
> preparing the content referring to the latest SQL grid documentation [2].
> Prachi, could you take over as? I do remember that you were updating the
> origins SQL queries page.
>
> In addition, I think we need to create a banner for SQL Grid similar to
> the one we have to Data Grid (attached) and place it one the site. I
> suggest to base it on this image [3]. Any other ideas?
>
>
> [1] https://ignite.apache.org/features/sql.html
> [2] https://apacheignite.readme.io/docs/sql-grid
> [3] https://files.readme.io/ee4c650-SQL-Grid-Diagram_v4.png
>
> 
>
>

Re: [RESULT] [VOTE] Apache Ignite 1.8.0 Release (RC1)

2016-12-12 Thread Denis Magda 
Cos, Roman S.,

Is there any hint on or some other way on how we can get attention of Apache 
Infra team to this issue?
https://issues.apache.org/jira/browse/INFRA-13073 


—
Denis

> On Dec 10, 2016, at 7:45 AM, Denis Magda  wrote:
> 
> Created an INFRA ticket to double check that this is not an infrastructure 
> issue
> https://issues.apache.org/jira/browse/INFRA-13073 
>  
>  >
> 
> Sergey, Anton, please keep an eye on it.
> 
> —
> Denis
> 
>> On Dec 10, 2016, at 6:49 AM, Denis Magda  wrote:
>> 
>> Well, thanks for pointing out to this.
>> 
>> Sergey, looks like you missed something at some releasing phase. If I create 
>> a project from 1.8 examples then Maven can’t locate binaries for 1.8.0. 
>> Please fix this ASAP. 
>> 
>> —
>> Denis
>> 
>>> On Dec 10, 2016, at 3:57 AM, 李玉珏@163 <18624049...@163.com> wrote:
>>> 
>>> Hi:
>>> 
>>> 
>>> http://repo.maven.apache.org/maven2/org/apache/ignite
>>> 
>>> the site above, not updated?
>>> 
>>> 
>>> 在 2016/12/9 22:06, Sergey Kozlov 写道:
 Hi
 
 Maven repository has been released.
 
 https://repository.apache.org/content/repositories/releases/org/apache/ignite/
 
 On Fri, Dec 9, 2016 at 4:41 PM, 李玉珏@163 <18624049...@163.com> wrote:
 
> maven repo is not updated?
> 
> 
> 
> 在 2016/12/9 21:37, Ксения Рыбакова 写道:
> 
>> Hi,
>> 
>> Update notifier for 1.7.0 shows that version is up to date. Could anybody
>> fix it please?
>> 
>> +--+
> Ignite ver. 1.7.0#20160801-sha1:383273e3f6
> 6f702de2482466dce954d570a8ccf2
> +---
> ---+
> 
 ...
>> [16:32:54,180][INFO ][main][GridDiscoveryManager] Topology snapshot
>> [ver=1,
>> servers=1, clients=0, CPUs=4, heap=1.0GB]
>> [16:33:03,833][INFO ][ignite-update-notifier-timer][GridUpdateNotifier]
>> Your version is up to date.
>> 
>> --
>> Thanks,
>> Ksenia
>> 
>> On Fri, Dec 9, 2016 at 4:14 PM, Pavel Tupitsyn 
>> wrote:
>> 
>> I've updated the site, there were commented parts on Download page from
>>> Denis, so that was easy :)
>>> Main and News pages also updated.
>>> 
>>> Just a reminder - any committer can update the site, just modify files 
>>> in
>>> SVN, and changes will appear online:
>>> https://svn.apache.org/repos/asf/ignite/site/trunk
>>> 
>>> On Fri, Dec 9, 2016 at 1:07 PM, Vladimir Ozerov 
>>> wrote:
>>> 
>>> Denis,
 Release has been propagated to mirrors, so you can go ahead with site
 update.
 
 Vladimir.
 
 On Fri, Dec 9, 2016 at 1:28 AM, Denis Magda  wrote:
 
 Great, thanks!
> Released all the docs (Java, .NET, C++, etc.) and update the site
> partially.
> 
> I can’t go ahead and update the downloads page [1] on the site because
> 
 the
 
> binaries and sources haven’t been uploaded yet. I get 404 error every
> 
 time
 
> I try to download one of the below.
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip <
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-1.8.0-src.zip>
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-
> 
 fabric-1.8.0-bin.zip
 <
 
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-
> 
 fabric-1.8.0-bin.zip
 http://apache.osuosl.org/ignite/1.8.0/apache-ignite-
 hadoop-1.8.0-bin.zip
 <
 
> http://apache.osuosl.org/ignite/1.8.0/apache-ignite-
> 
 hadoop-1.8.0-bin.zip
> Sergey K., will you handle this?
> 
> In addition, we need to update our cloud images. Nick, please dedicate
> some time tomorrow for this.
> https://issues.apache.org/jira/browse/IGNITE-4402 <
> https://issues.apache.org/jira/browse/IGNITE-4402>
> 
> [1] https://ignite.apache.org/download.cgi  download.cgi>
> 
> —
> Denis
> 
> On Dec 8, 2016, at 12:08 PM, Sergey Kozlov 
> wrote:
> Hi
>> I've completed release procedure in SVN and maven repository.
>> 
>> https://dist.apache.org/repos/dist/release/ignite/1.8.0/
>> https://svn.apache.org/repos/asf/ignite/site/trunk/releases/1.8.0/
>> 
>> Who could update the sites

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Denis Magda 
Denis Magda


Regardless of the fact that I’m a GridGain employee and that GridGain still 
represents the majority of our community, I would truly like to make our 
community more diversified and transparent and less dependent of GridGain. 
Being a PMC chair will motivate me to learn even more about Apache processes, 
principles and leverage the overall knowledge and fully relying on your support 
and experience of other open source project move our community to the 
diversified future.

—
Denis

> On Dec 10, 2016, at 12:24 PM, Dmitriy Setrakyan  wrote:
> 
> According to the discussion on the dev list [1], the following candidates
> were proposed for the Apache Ignite PMC Chair position:
> 
> Vladimir Ozerov
> Konstantin Boudnik
> Valentin Kulichenko
> Denis Magda
> Branko Čibej
> 
> The vote is taking place on the dev list, however only votes from Apache
> Ignite PMC members will be considered as binding.
> 
> *Note that this is not +1 or -1 vote. Please reply to this email specifying
> the name of your preferred candidate for the Ignite PMC chair position
> (feel free to explain why).*
> 
> The vote will go for 72 hours. Candidate who gets the most amount of votes
> (not the majority) will be elected.
> 
> Note, that I specifically removed my name from the list, because the whole
> point is to rotate a PMC chair, and not to reelect one.
> 
> [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-PMC-Chair-
> rotation-time-td11941.html

[jira] [Created] (IGNITE-4416) Document logging capabilities of Ignite

2016-12-12 Thread Denis Magda (JIRA) 
Denis Magda created IGNITE-4416:
---

 Summary: Document logging capabilities of Ignite
 Key: IGNITE-4416
 URL: https://issues.apache.org/jira/browse/IGNITE-4416
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda


Ignite supports a variety of logging provides but neither of them is documented 
on readme.io. We have to fill this gap.




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

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Konstantin Boudnik 

On Sat, Dec 10, 2016 at 12:24PM, Dmitriy Setrakyan wrote:
> According to the discussion on the dev list [1], the following candidates
> were proposed for the Apache Ignite PMC Chair position:
> 
>  Vladimir Ozerov
>  Konstantin Boudnik
>  Valentin Kulichenko
>  Denis Magda
>  Branko Čibej
> 
> The vote is taking place on the dev list, however only votes from Apache
> Ignite PMC members will be considered as binding.

Yes, think "electoral" vs "popular" ;)

> *Note that this is not +1 or -1 vote. Please reply to this email specifying
> the name of your preferred candidate for the Ignite PMC chair position
> (feel free to explain why).*
> 
> The vote will go for 72 hours. Candidate who gets the most amount of votes
> (not the majority) will be elected.
> 
> Note, that I specifically removed my name from the list, because the whole
> point is to rotate a PMC chair, and not to reelect one.
> 
> [1] http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-PMC-Chair-
> rotation-time-td11941.html

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Igor Rudyak 
Konstantin Boudnik

On Sun, Dec 11, 2016 at 2:39 AM, Sergi Vladykin 
wrote:

> Konstantin Boudnik
>
> Sergi
>

Re: NullPointerException on ScanQuery

2016-12-12 Thread Alper Tekinalp 
>
> Hi,
>

Hi Andrey.

First of all thanks for your responces.

First of all you have races in your code. For example your start two
> threads and destroy caches before thread is finished and it leads to
> cache closed error.


It is of course reasonable to get "cache closed" errors in that case and I
am OK with that.


> Moreover, you stops application before any thread
> finished and it leads to topology changing and NPE.
>

Correct me if I am wrong but I dont think that is true. NPE occurs before
stopping the application. Hence, before any topology changes.

I can understand that this error occurs in a topology change but in that
case it is not.


> The second, I don't understand why do you use threads at all? Usually
> you should start Ignite cluster, connect to it using client node and
> run scan query.
>
> Starting of several instances of Ignite in one JVM makes sense only
> for test purposes. Anyway, you should start Ignite instances, creates
> caches and after it run threads with your tasks.


Actually this is a test code I try to simulate our real use case. In our
application we have two server nodes that internally running in our
application and we run scan query in that server nodes. In some cases both
of the servers destroy cache and I expect to get the cache closed errors.
But not NPEs because there is no change in topology.

Again thanks for your responses.

Regards.

-- 
Alper Tekinalp

Software Developer
Evam Streaming Analytics

Atatürk Mah. Turgut Özal Bulv.
Gardenya 5 Plaza K:6 Ataşehir
34758 İSTANBUL

Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
www.evam.com.tr

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Nikolai Tikhonov 
Denis Magda

On Mon, Dec 12, 2016 at 8:02 PM, Roman Shaposhnik  wrote:

> On Sat, Dec 10, 2016 at 12:24 PM, Dmitriy Setrakyan
>  wrote:
> > According to the discussion on the dev list [1], the following candidates
> > were proposed for the Apache Ignite PMC Chair position:
> >
> >  Vladimir Ozerov
> >  Konstantin Boudnik
> >  Valentin Kulichenko
> >  Denis Magda
> >  Branko Čibej
>
> Konstantin Boudnik
>
> Thanks,
> Roman.
>

Re: [VOTE] Apche Ignite PMC Chair Election

2016-12-12 Thread Roman Shaposhnik 
On Sat, Dec 10, 2016 at 12:24 PM, Dmitriy Setrakyan
 wrote:
> According to the discussion on the dev list [1], the following candidates
> were proposed for the Apache Ignite PMC Chair position:
>
>  Vladimir Ozerov
>  Konstantin Boudnik
>  Valentin Kulichenko
>  Denis Magda
>  Branko Čibej

Konstantin Boudnik

Thanks,
Roman.

[GitHub] ignite pull request #1341: IGNITE-4413 .NET: Fix DateTime argument handling ...

2016-12-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 #1261: IGNITE-4033 Streamline platform callback interfac...

2016-12-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 #1341: IGNITE-4413 .NET: Fix DateTime argument handling ...

2016-12-12 Thread ptupitsyn 
GitHub user ptupitsyn opened a pull request:

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

IGNITE-4413 .NET: Fix DateTime argument handling in SqlQuery



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

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

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

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


commit e71b900b052f99425940437018a5bf3e2c1aa1f7
Author: Pavel Tupitsyn 
Date:   2016-12-12T13:23:54Z

IGNITE-4413 .NET: SqlQuery with DateTime arguments does not work

commit 0979a57dbab1db630d4870faab8be78ea230f853
Author: Pavel Tupitsyn 
Date:   2016-12-12T13:28:25Z

wip

commit bb75df3f2bf714d71824dae6908ff8181829e4b0
Author: Pavel Tupitsyn 
Date:   2016-12-12T13:39:33Z

revert

commit a154406b8de2b4b4aaae19ba7581145c330e190b
Author: Pavel Tupitsyn 
Date:   2016-12-12T13:42:54Z

wip

commit 5f240fe60e59ead1bdde5c0cfbe9fe5dc23b6f8a
Author: Pavel Tupitsyn 
Date:   2016-12-12T13:50:33Z

wip tests

commit 9700a492137e9df570c0dc4397ab7f0bb4872386
Author: Pavel Tupitsyn 
Date:   2016-12-12T14:02:53Z

Fix DateTime args serialization

commit 65f1c0dd9d85f67805b0458e6771ce5f35d0228a
Author: Pavel Tupitsyn 
Date:   2016-12-12T14:04:43Z

Fix 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 #1302: Ignite 4341

2016-12-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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 #1321: Ignite 4341 master2

2016-12-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-4415) .NET: EntityFramework 2nd level cache fails for some complex queries

2016-12-12 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-4415:
--

 Summary: .NET: EntityFramework 2nd level cache fails for some 
complex queries
 Key: IGNITE-4415
 URL: https://issues.apache.org/jira/browse/IGNITE-4415
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


This EF query (sent by user) fails when EF caching is enabled:
{code}
var regionsAsm = user.GetAllChildRegions()
.Where(w => w.RegionToRole.Any(a => a.RoleID == 
(int)UserRoles.ASM));
 
var allInvestTitle = user.RepositoryFactory.InvestTitle.All();
 
var isFutureYear = filters.ActualYear.Value.Year >
   
user.RepositoryFactory.Version.All().SingleOrDefault(w => 
w.IsCurrent)?.ActualYear;
 
var distributorToRegionAsmBindings = !isFutureYear
? regionsAsm.SelectMany(s => s.DistributorToRegionAsmBinding)
: regionsAsm.SelectMany(s => 
s.DistributorToRegionAsmBinding.Where(b => b.IsActual));
 
 
var resultAllBudgets = distributorToRegionAsmBindings
.Select(d => new { Distributor = d.Distributor, RegionAsm = 
d.Region, d })
.SelectMany(dr => allInvestTitle, (dr, t) => new { 
dr.Distributor, dr.RegionAsm, InvestTitle = t, dr.d });
 
var allBudgets = resultAllBudgets
.Select(b => new BudgetResult
{
AsmRegionId = b.RegionAsm.ID,
AsmRegionName = b.RegionAsm.Name,
DistributorId = b.Distributor.ID,
DistributorName = b.Distributor.Name,
RsmRegionId = b.RegionAsm.RegionExpand
.Where(w => w.Region1.RegionToRole.Any(a => 
a.RoleID == (int) UserRoles.RSM))
.Select(ss => ss.ParentRegionID)
.FirstOrDefault(),
RsmRegionName = b.RegionAsm.RegionExpand
.Where(w => w.Region1.RegionToRole.Any(a => 
a.RoleID == (int) UserRoles.RSM))
.Select(ss => ss.Region1.Name)
.FirstOrDefault(),
InvestTitleId = b.InvestTitle.ID,
InvestTitleName = b.InvestTitle.Name,
});
 
var result = allBudgets.ToList();
{code}

Error:
{code}
class org.apache.ignite.binary.BinaryObjectException: Unexpected flag value 
[pos=43775, expected=12, actual=0]
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.checkFlag(BinaryReaderExImpl.java:1403)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readByteArray(BinaryReaderExImpl.java:468)
at 
org.apache.ignite.internal.processors.platform.entityframework.PlatformDotNetEntityFrameworkCacheExtension.processInOutStreamLong(PlatformDotNetEntityFrameworkCacheExtension.java:125)
at 
org.apache.ignite.internal.processors.platform.cache.PlatformCache.processInStreamOutLong(PlatformCache.java:761)
at 
org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inStreamOutLong(PlatformAbstractTarget.java:78)
{code}

Generated SQL:
{code}
SELECT 
[Project17].[ID2] AS [ID], 
[Project17].[ID1] AS [ID1], 
[Project17].[Name1] AS [Name], 
[Project17].[ID] AS [ID2], 
[Project17].[Name] AS [Name1], 
CASE WHEN ([Project17].[C1] IS NULL) THEN 0 ELSE [Project17].[C2] END AS 
[C1], 
[Project17].[C3] AS [C2], 
[Project17].[Name2] AS [Name2]
FROM ( SELECT 
[Project13].[ID] AS [ID], 
[Project13].[Name] AS [Name], 
[Project13].[ID1] AS [ID1], 
[Project13].[Name1] AS [Name1], 
[Project13].[ID2] AS [ID2], 
[Project13].[Name2] AS [Name2], 
[Project13].[C1] AS [C1], 
[Project13].[C2] AS [C2], 
(SELECT TOP (1) 
[Project14].[Name] AS [Name]
FROM ( SELECT 
[Extent14].[ParentRegionID] AS [ParentRegionID], 
[Extent15].[ID] AS [ID], 
[Extent15].[Name] AS [Name]
FROM  [dbo].[RegionExpand] AS [Extent14]
INNER JOIN [dbo].[Region] AS [Extent15] ON 
[Extent14].[ParentRegionID] = [Extent15].[ID]
WHERE [Project13].[ID1] = [Extent14].[RegionID]
)  AS [Project14]
WHERE  EXISTS (SELECT 
1 AS [C1]
FROM [dbo].[RegionToRole] AS [Extent16]
WHERE ([Project14].[ParentRegionID] = [Extent16].[RegionID]) 
AND (5 = [Extent16].[RoleID])
)) AS [C3]
FROM ( SELECT 
[Project12].[ID] AS [ID], 
[Project12].[Name] AS [Name], 
[Project12].[ID1] AS [ID1], 
[Project12].[Name1] AS [Name1],

[jira] [Created] (IGNITE-4414) Add JUnit test for local queries against a partitoned cache with 2 backups

2016-12-12 Thread Sergey Kozlov (JIRA) 
Sergey Kozlov created IGNITE-4414:
-

 Summary: Add JUnit test for local queries against a partitoned 
cache with 2 backups
 Key: IGNITE-4414
 URL: https://issues.apache.org/jira/browse/IGNITE-4414
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.8
Reporter: Sergey Kozlov
 Fix For: 2.0


Add the JUnit test covers the following case:
 - partitioned cache with 2 backups (may be include backups=0,1 as well)
 - put 100 entries

When I execute a local sql field query it returns more entries than the local 
size depending on the number of backup.





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

[GitHub] ignite pull request #1340: Ignite 4363

2016-12-12 Thread alexpaschenko 
GitHub user alexpaschenko opened a pull request:

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

Ignite 4363

Inner properties handling/general UPDATE fix

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

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

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

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


commit 76d2e43c063660179bf6223b493ae0e9b1aa552e
Author: Alexander Paschenko 
Date:   2016-12-12T10:35:47Z

IGNITE-4363 Non binary UPDATE/inner properties general UPDATE fix

commit 55d0710baec0705625dc77be71441138fe155f41
Author: Alexander Paschenko 
Date:   2016-12-12T10:37:21Z

Merge branch 'master' into ignite-4363

commit ed577b65532c83d1e2863c99d06945af9263af49
Author: Alexander Paschenko 
Date:   2016-12-12T12:48:58Z

IGNITE-4363 Nested fields handling fix for INSERT/MERGE




---
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-4413) .NET: SqlQuery with DateTime arguments does not work

2016-12-12 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-4413:
--

 Summary: .NET: SqlQuery with DateTime arguments does not work
 Key: IGNITE-4413
 URL: https://issues.apache.org/jira/browse/IGNITE-4413
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8, 1.7, 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


DateTime arguments are serialized incorrectly when using SqlQuery.
This is not the case with SqlFieldsQuery and LINQ. See CacheImpl.WriteQueryArgs 
and QueryBase.WriteQueryArgs.



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

Re: NullPointerException on ScanQuery

2016-12-12 Thread Andrey Gura 
Hi,

I've looked at your code.

First of all you have races in your code. For example your start two
threads and destroy caches before thread is finished and it leads to
cache closed error. Moreover, you stops application before any thread
finished and it leads to topology changing and NPE.

The second, I don't understand why do you use threads at all? Usually
you should start Ignite cluster, connect to it using client node and
run scan query.

Starting of several instances of Ignite in one JVM makes sense only
for test purposes. Anyway, you should start Ignite instances, creates
caches and after it run threads with your tasks.

On Mon, Dec 12, 2016 at 11:23 AM, Alper Tekinalp  wrote:
> Hi Andrey.
>
> Did you able to look to the code?
>
> Regards.
>
> On Thu, Dec 8, 2016 at 10:05 AM, Alper Tekinalp  wrote:
>
>> Hi.
>>
>> Could you please share your reproducer example?
>>
>>
>> I added classes to repoduce the error. It also throws cache closed errors
>> I am ok with it. But others.
>>
>> --
>> Alper Tekinalp
>>
>> Software Developer
>> Evam Streaming Analytics
>>
>> Atatürk Mah. Turgut Özal Bulv.
>> Gardenya 5 Plaza K:6 Ataşehir
>> 34758 İSTANBUL
>>
>> Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
>> www.evam.com.tr
>> 
>>
>
>
>
> --
> Alper Tekinalp
>
> Software Developer
> Evam Streaming Analytics
>
> Atatürk Mah. Turgut Özal Bulv.
> Gardenya 5 Plaza K:6 Ataşehir
> 34758 İSTANBUL
>
> Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
> www.evam.com.tr
>

[GitHub] ignite pull request #1338: IGNITE-4410 .NET: Provide default-config-dotnet.x...

2016-12-12 Thread ptupitsyn 
Github user ptupitsyn closed the pull request at:

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


---
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-4412) .NET: NLogLoggerTest is not thread safe

2016-12-12 Thread Pavel Tupitsyn (JIRA) 
Pavel Tupitsyn created IGNITE-4412:
--

 Summary: .NET: NLogLoggerTest is not thread safe
 Key: IGNITE-4412
 URL: https://issues.apache.org/jira/browse/IGNITE-4412
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
 Fix For: 2.0






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

[GitHub] ignite pull request #1339: IGNITE-4386

2016-12-12 Thread devozerov 
Github user devozerov closed the pull request at:

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


---
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 #1327: Ignite 4386

2016-12-12 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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: NullPointerException on ScanQuery

2016-12-12 Thread Alper Tekinalp 
Hi Andrey.

Did you able to look to the code?

Regards.

On Thu, Dec 8, 2016 at 10:05 AM, Alper Tekinalp  wrote:

> Hi.
>
> Could you please share your reproducer example?
>
>
> I added classes to repoduce the error. It also throws cache closed errors
> I am ok with it. But others.
>
> --
> Alper Tekinalp
>
> Software Developer
> Evam Streaming Analytics
>
> Atatürk Mah. Turgut Özal Bulv.
> Gardenya 5 Plaza K:6 Ataşehir
> 34758 İSTANBUL
>
> Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
> www.evam.com.tr
> 
>



-- 
Alper Tekinalp

Software Developer
Evam Streaming Analytics

Atatürk Mah. Turgut Özal Bulv.
Gardenya 5 Plaza K:6 Ataşehir
34758 İSTANBUL

Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
www.evam.com.tr