Re: Regarding gsoc 2017

[Prakhar Pratyush]

Hello,


>>>On Tue, Jan 24, 2017 at 8:26 AM, Denis Magda  wrote

>>>Are you familiar with SWIG?
> >>>http://www.swig.org  
>

> >>> []
>

I have read about it (just out of curiosity). I have never actually
worked on it. Definitely, as a student,
it will be a great learning experience, and also I think getting to
know about C++ APIs will be great for
future contributions (gsoc or otherwise). I'd like to work on this with
initial guidance.

Thanks

>

Re: Regarding gsoc 2017

[Denis Magda]

BTW, Prakhar,

Are you familiar with SWIG?
http://www.swig.org 

It will be great if you can take Ignite's C++ API and SWIG to generate Python 
API that is missing in Ignite. How do you like this kind of task? It will allow 
you to learn all supported C++ API in details and do a priceless contribution 
to Ignite.

—
Denis

> On Jan 23, 2017, at 6:39 PM, Denis Magda  wrote:
> 
> Sure, the contribution is always welcomed. For instance, you can start with 
> one of the tickets listed here:
> https://ignite.apache.org/community/contribute.html#pick-ticket 
> 
> 
> Using this filter you can pick a C++ related ticket of interest:
> https://issues.apache.org/jira/issues/?jql=creator%20%3D%20isapego%20and%20status%20%3D%20Open
>  
> 
> 
> Igor Sapego, could you suggest any C++ tasks for the beginning?
> 
> Finally, as for machine learning, Nikita has just initiated a dedicated 
> discussion on the dev list. Please feel free to join it:
> http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-td13936.html
>  
> 
> 
> Let me know if you need more details on anything.
> 
> —
> Denis
> 
>> On Jan 23, 2017, at 6:10 PM, Prakhar Pratyush  wrote:
>> 
>> Hello,
>> 
>> Thanks for replying
>> 
> On Tue, Jan 24, 2017 at 1:17 AM, Denis Magda  wrote:
>> 
>> Yes, we will submit several projects to GSOC. [...]
>>> 
>> 
>> Is it possible to get involved in the pre-gsoc contribution, as I think it
>> will help in understanding the
>> project better .
>> 
>> 
>> As for machine learning this is [2] the first task related to this
>>> activity. Most likely Nikita will send some proposal to the dev list
>> soon and some part of the functionality will go to GSOC.
>> 
>> [1] http://apache-ignite-developers.2346864.n4.nabble.com/
>>> Google-Summer-Of-Code-2017-td13180.html
>> [2] https://issues.apache.org/jira/browse/IGNITE-4572
>>> 
>>> 
>> I am a 4th year student in Electronics & Computer department at IIT
>> Roorkee. I am good at mathematics, and relatively a
>> beginner/moderate in machine learning. If possible, I'd like to contribute
>> to [2]. I'm good at C++/Python programming language.
>> What programming languages will be used in the machine learning project?
>> 
>> Thanks
>> Prakhar
> 

Re: Ignite ASF Confluence edit rights

[Denis Magda]

Well, I don’t see any kind of admin panel on the Wiki. Cos, could you grant me 
admin rights there (dmagda)?

Alexander, what’s the account name you use to login on the Wiki?

—
Denis

> On Jan 23, 2017, at 2:54 PM, Konstantin Boudnik  wrote:
> 
> Yup, this is a contribution all right. Anyone with admin creds for the Ignite
> space should be able to go and add permissions to a person with Wiki account. 
> 
> Cos
> 
> On Mon, Jan 23, 2017 at 11:43AM, Denis Magda wrote:
>> Dmitriy, Cos,
>> 
>> Does contributors (not committers) have write permissions on Ignite wiki?
>> Looks like they don’t.
>> 
>> Alexander, as a temporal solution, please ask the committer that reviewed
>> and merged your changes to update this page as well.
>> 
>> —
>> Denis
>> 
>>> On Jan 23, 2017, at 2:22 AM, Alexander Fedotov 
>>>  wrote:
>>> 
>>> Hi folks,
>>> 
>>> In scope of the IGNITE-3207
>>>  Ignite 2.0 Migration
>>> Guide needs to be updated
>>> Apache+Ignite+2.0+Migration+Guide
>>> 
>>> .
>>> Unfortunately, currently I don't have rights to edit the page.
>>> Who can grant me ones?
>>> 
>>> -- 
>>> Kind regards,
>>> Alexander.
>> 

Re: Regarding gsoc 2017

[Prakhar Pratyush]

Hello,

Thanks for replying

>>>On Tue, Jan 24, 2017 at 1:17 AM, Denis Magda  wrote:

> >>>Yes, we will submit several projects to GSOC. [...]
>

Is it possible to get involved in the pre-gsoc contribution, as I think it
will help in understanding the
project better .


> >>>As for machine learning this is [2] the first task related to this
> activity. Most likely Nikita will send some proposal to the dev list
> >>>soon and some part of the functionality will go to GSOC.
> >>>
> >>>[1] http://apache-ignite-developers.2346864.n4.nabble.com/
> Google-Summer-Of-Code-2017-td13180.html
> >>>[2] https://issues.apache.org/jira/browse/IGNITE-4572
>
>
 I am a 4th year student in Electronics & Computer department at IIT
Roorkee. I am good at mathematics, and relatively a
 beginner/moderate in machine learning. If possible, I'd like to contribute
to [2]. I'm good at C++/Python programming language.
 What programming languages will be used in the machine learning project?

Thanks
Prakhar

Re: Timeout for ordered message

[Valentin Kulichenko]

Makes sense. I created a ticket:
https://issues.apache.org/jira/browse/IGNITE-4595

-Val

On Mon, Jan 23, 2017 at 3:05 AM, Yakov Zhdanov  wrote:

> Val, let's do the following.
>
> 1. We need to state in javadocs that we expect unordered msg handler to be
> added in advance, otherwise message get ignored. This may require user
> should have an ability to add listeners before start (same as in case with
> event listeners) - or can this be done in lifecycle listener? I think no.
> 2. You can add overload for ordered msg sending without timeout and explain
> in javadoc that this will work similar to endless timeout.
>
> Makes sense?
>
>
> --Yakov
>
> 2017-01-13 0:54 GMT+03:00 Valentin Kulichenko <
> valentin.kuliche...@gmail.com
> >:
>
> > Yakov,
> >
> > I'm talking only about user messages and public API. What is the purpose
> of
> > the timeout in this case?
> >
> > I'm just trying to properly understand the semantics and at least fix the
> > JavaDoc as it seems to be completely wrong now.
> >
> > -Val
> >
> > On Thu, Jan 12, 2017 at 2:41 AM, Yakov Zhdanov 
> > wrote:
> >
> > > Not sure what we are trying to achieve here. Unordered messages are
> > simply
> > > ignored if there is no listener. We always expect unordered listeners
> to
> > be
> > > installed before at least for internal messages, but this is not the
> case
> > > for some ordered messages, i.e. task session requests.
> > >
> > > --Yakov
> > >
> > > 2017-01-12 0:03 GMT+03:00 Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com
> > > >:
> > >
> > > > Yakov,
> > > >
> > > > So you confirm that my understanding is correct and JavaDoc is wrong,
> > > > right?
> > > >
> > > > As for 'no listener' scenario, that's a good point, but it should be
> > > > applicable to unordered messages as well then. The most confusing
> part
> > > here
> > > > is that we have timeout only for unordered messages while there is
> > > nothing
> > > > specific about them in terms of delivery.
> > > >
> > > > How about we two methods, with and without timeout, for both ordered
> > and
> > > > unordered messages? Like this:
> > > >
> > > > void send(@Nullable Object topic, Object msg);
> > > > void send(@Nullable Object topic, Object msg, long timeout); // New
> > > method.
> > > > void sendOrdered(@Nullable Object topic, Object msg); // New method.
> > > > void sendOrdered(@Nullable Object topic, Object msg, long timeout);
> > > >
> > > > This change will make API consistent and will not break
> compatibility.
> > > > Thoughts?
> > > >
> > > > -Val
> > > >
> > > > On Wed, Jan 11, 2017 at 12:20 AM, Yakov Zhdanov  >
> > > > wrote:
> > > >
> > > > > If you send ordered messages to a node and listener on receiving
> side
> > > has
> > > > > not yet been added then timeout is still sufficient to clean up
> > > buffered
> > > > > messages.
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2017-01-10 23:36 GMT+03:00 Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com>:
> > > > >
> > > > > > Yakov,
> > > > > >
> > > > > > I was actually asking about the public API for messaging
> > > > > > (IgniteMessaging#sendOrdered
> > > > > > method). Here is the JavaDoc:
> > > > > >
> > > > > >  * The {@code timeout} parameter specifies how long an
> out-of-order
> > > > > message
> > > > > > will stay in a queue,
> > > > > >  * waiting for messages that are ordered ahead of it to arrive.
> If
> > > > > timeout
> > > > > > expires, then all ordered
> > > > > >  * messages that have not arrived before this message will be
> > > skipped.
> > > > > When
> > > > > > (and if) expired messages
> > > > > >  * actually do arrive, they will be ignored.
> > > > > >
> > > > > > I remember that we indeed had this scenario possible a while ago,
> > but
> > > > > then
> > > > > > implementation of ordered messaging was reworked and
> 'out-of-order
> > > > > message'
> > > > > > can't happen anymore. Is this correct? If so, I think the timeout
> > > > should
> > > > > be
> > > > > > removed from the API.
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Tue, Jan 10, 2017 at 2:34 AM, Yakov Zhdanov <
> > > yzhda...@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Val, timeout still makes sense for task sessions. It is
> possible
> > > that
> > > > > all
> > > > > > > jobs mapped to node have been completed, but node still
> receives
> > > > > > > attributes. Attributes are sent in ordered messages. It may
> > happen
> > > so
> > > > > > that
> > > > > > > node may start processing jobs for that task again and this way
> > all
> > > > the
> > > > > > > attributes will be available. If task timeout elapses then
> > messages
> > > > get
> > > > > > > cleared. Please let me know if you still have questions.
> > > > > > >
> > > > > > > Thanks!
> > > > > > > --
> > > > > > > Yakov Zhdanov, Director R
> > > > > > > *GridGain Systems*
> > > > > > > www.gridgain.com
> > > > > > >
> > > > > > > 2017-01-06 1:02 GMT+03:00 

Re: Apache Ignite SEO Audit

[Prachi Garg]

Dmitriy,

I don't have admin rights; you do. You can follow the instructions here -
https://support.google.com/webmasters/answer/2453966

-Prachi

On Mon, Jan 23, 2017 at 3:45 PM, Dmitriy Setrakyan 
wrote:

> Prachi, would you be the one to help Mauricio here?
>
> On Mon, Jan 23, 2017 at 3:23 PM, Mauricio Stekl 
> wrote:
>
> > No, I’m afraid I can’t use the same file. However it seems there was
> > already a GWT account setup for this domain then. So I could be granted
> > access to that account instead. Would that be possible?
> >
> > Thanks.
> > Mauricio
> >
> >
> > > On Jan 23, 2017, at 18:24, Dmitriy Setrakyan 
> > wrote:
> > >
> > > Mauricio, we already have similar file added for google site
> > verification:
> > > google9276fe2a42313afd.html
> > >
> > > Can you reuse this one?
> > >
> > > D.
> > >
> > > On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl <
> mauri...@gridgain.com>
> > > wrote:
> > >
> > >> Hi,
> > >> In order to setup the Google Webmaster Tools account on
> > ignite.apache.org,
> > >> I would need to upload the attached .html file to the root of the
> > website.
> > >>
> > >> Could someone with commit privileges help me with this?
> > >>
> > >> Thanks in advance.
> > >>
> > >> Mauricio
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan 
> > >> wrote:
> > >>
> > >> Hi Terry, this should not be a problem. I have sent you the
> credentials
> > >> privately. Let me know if you need more help.
> > >>
> > >> D.
> > >>
> > >> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman <
> teris...@gridgain.com>
> > >> wrote:
> > >>
> > >> Hi All,
> > >>
> > >>
> > >>
> > >> In order to proceed effectively with the SEO audit of the Apache
> Ignite
> > >> website, we need admin access to the Google Analytics account for the
> > >> website. Once we have the Google Analytics account access, we will
> setup
> > >> Google Webmaster Tools for the website (it isn't setup currently)
> which
> > >> will
> > >> give us insights into a variety of characteristics of the website.
> > >>
> > >>
> > >>
> > >> If anyone has any concerns about this, please let me know. I look
> > forward
> > >> to
> > >> getting started on this audit.
> > >>
> > >>
> > >>
> > >> Thanks,
> > >>
> > >>
> > >>
> > >> Terry
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> >
> >
>

Re: Apache Ignite SEO Audit

[Dmitriy Setrakyan]

Prachi, would you be the one to help Mauricio here?

On Mon, Jan 23, 2017 at 3:23 PM, Mauricio Stekl 
wrote:

> No, I’m afraid I can’t use the same file. However it seems there was
> already a GWT account setup for this domain then. So I could be granted
> access to that account instead. Would that be possible?
>
> Thanks.
> Mauricio
>
>
> > On Jan 23, 2017, at 18:24, Dmitriy Setrakyan 
> wrote:
> >
> > Mauricio, we already have similar file added for google site
> verification:
> > google9276fe2a42313afd.html
> >
> > Can you reuse this one?
> >
> > D.
> >
> > On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl 
> > wrote:
> >
> >> Hi,
> >> In order to setup the Google Webmaster Tools account on
> ignite.apache.org,
> >> I would need to upload the attached .html file to the root of the
> website.
> >>
> >> Could someone with commit privileges help me with this?
> >>
> >> Thanks in advance.
> >>
> >> Mauricio
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan 
> >> wrote:
> >>
> >> Hi Terry, this should not be a problem. I have sent you the credentials
> >> privately. Let me know if you need more help.
> >>
> >> D.
> >>
> >> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman 
> >> wrote:
> >>
> >> Hi All,
> >>
> >>
> >>
> >> In order to proceed effectively with the SEO audit of the Apache Ignite
> >> website, we need admin access to the Google Analytics account for the
> >> website. Once we have the Google Analytics account access, we will setup
> >> Google Webmaster Tools for the website (it isn't setup currently) which
> >> will
> >> give us insights into a variety of characteristics of the website.
> >>
> >>
> >>
> >> If anyone has any concerns about this, please let me know. I look
> forward
> >> to
> >> getting started on this audit.
> >>
> >>
> >>
> >> Thanks,
> >>
> >>
> >>
> >> Terry
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

No, I’m afraid I can’t use the same file. However it seems there was already a 
GWT account setup for this domain then. So I could be granted access to that 
account instead. Would that be possible?

Thanks.
Mauricio 


> On Jan 23, 2017, at 18:24, Dmitriy Setrakyan  wrote:
> 
> Mauricio, we already have similar file added for google site verification:
> google9276fe2a42313afd.html
> 
> Can you reuse this one?
> 
> D.
> 
> On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl 
> wrote:
> 
>> Hi,
>> In order to setup the Google Webmaster Tools account on ignite.apache.org,
>> I would need to upload the attached .html file to the root of the website.
>> 
>> Could someone with commit privileges help me with this?
>> 
>> Thanks in advance.
>> 
>> Mauricio
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan 
>> wrote:
>> 
>> Hi Terry, this should not be a problem. I have sent you the credentials
>> privately. Let me know if you need more help.
>> 
>> D.
>> 
>> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman 
>> wrote:
>> 
>> Hi All,
>> 
>> 
>> 
>> In order to proceed effectively with the SEO audit of the Apache Ignite
>> website, we need admin access to the Google Analytics account for the
>> website. Once we have the Google Analytics account access, we will setup
>> Google Webmaster Tools for the website (it isn't setup currently) which
>> will
>> give us insights into a variety of characteristics of the website.
>> 
>> 
>> 
>> If anyone has any concerns about this, please let me know. I look forward
>> to
>> getting started on this audit.
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> Terry
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 

Re: Ignite ASF Confluence edit rights

[Konstantin Boudnik]

Yup, this is a contribution all right. Anyone with admin creds for the Ignite
space should be able to go and add permissions to a person with Wiki account. 

Cos

On Mon, Jan 23, 2017 at 11:43AM, Denis Magda wrote:
> Dmitriy, Cos,
> 
> Does contributors (not committers) have write permissions on Ignite wiki?
> Looks like they don’t.
> 
> Alexander, as a temporal solution, please ask the committer that reviewed
> and merged your changes to update this page as well.
> 
> —
> Denis
> 
> > On Jan 23, 2017, at 2:22 AM, Alexander Fedotov 
> >  wrote:
> > 
> > Hi folks,
> > 
> > In scope of the IGNITE-3207
> >  Ignite 2.0 Migration
> > Guide needs to be updated
> > Apache+Ignite+2.0+Migration+Guide
> > 
> > .
> > Unfortunately, currently I don't have rights to edit the page.
> > Who can grant me ones?
> > 
> > -- 
> > Kind regards,
> > Alexander.
> 

Re: Allow distributed SQL query execution over explicit set of partitions

[Dmitriy Setrakyan]

On Mon, Jan 23, 2017 at 11:16 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:

> Dmitriy,
>
> This still can make sense for some scenarios, because we could limit number
> of initial map requests reducing overall query overhead.
>
> Are you still sure we need to throw an exception ?
>

The outcome and the resulting behavior needs to be absolutely clear to our
users. If we can't provide any sort of guarantee here, I would disallow it
altogether.


>
> 2017-01-23 1:49 GMT+03:00 Dmitriy Setrakyan :
>
> > On Sun, Jan 22, 2017 at 5:06 AM, Alexei Scherbakov <
> > alexey.scherbak...@gmail.com> wrote:
> >
> > > Yes, it will be possible because distributed joins are executed using
> > > broadcast queries.
> > >
> > >
> > In this case why even bother supporting non-collocated joins? We need to
> > throw an exception in this case.
> >
> > 2017-01-22 15:49 GMT+03:00 Dmitriy Setrakyan :
> > >
> > > > On Sun, Jan 22, 2017 at 4:46 AM, Alexei Scherbakov <
> > > > alexey.scherbak...@gmail.com> wrote:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > ScanQueries currently support only one partition. I will extend it
> to
> > > > > support multiple partitions.
> > > > >
> > > > > For distributed joins partitions will only be applied on "map"
> query
> > > > step.
> > > > >
> > > >
> > > > Will it still be possible to get data from the partitions that were
> not
> > > > specified?
> > > >
> > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> > >
> >
>
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>

Re: Ignite ASF Confluence edit rights

[Dmitriy Setrakyan]

I actually don't remember what needs to happen in order to have edit
permissions. I thought that being added as a contributor in Jira should be
enough.

Alex, have you registered on Apache Wiki?

D.

On Mon, Jan 23, 2017 at 1:29 PM, Alexander Fedotov <
alexander.fedot...@gmail.com> wrote:

> Thanks. I'll do.
>
> On Mon, Jan 23, 2017 at 10:43 PM, Denis Magda  wrote:
>
>> Dmitriy, Cos,
>>
>> Does contributors (not committers) have write permissions on Ignite wiki?
>> Looks like they don’t.
>>
>> Alexander, as a temporal solution, please ask the committer that reviewed
>> and merged your changes to update this page as well.
>>
>> —
>> Denis
>>
>> > On Jan 23, 2017, at 2:22 AM, Alexander Fedotov <
>> alexander.fedot...@gmail.com> wrote:
>> >
>> > Hi folks,
>> >
>> > In scope of the IGNITE-3207
>> >  Ignite 2.0
>> Migration
>> > Guide needs to be updated
>> > Apache+Ignite+2.0+Migration+Guide
>> > > Ignite+2.0+Migration+Guide>
>> > .
>> > Unfortunately, currently I don't have rights to edit the page.
>> > Who can grant me ones?
>> >
>> > --
>> > Kind regards,
>> > Alexander.
>>
>>
>
>
> --
> Kind regards,
> Alexander.
>

Re: Ignite ASF Confluence edit rights

[Alexander Fedotov]

Thanks. I'll do.

On Mon, Jan 23, 2017 at 10:43 PM, Denis Magda  wrote:

> Dmitriy, Cos,
>
> Does contributors (not committers) have write permissions on Ignite wiki?
> Looks like they don’t.
>
> Alexander, as a temporal solution, please ask the committer that reviewed
> and merged your changes to update this page as well.
>
> —
> Denis
>
> > On Jan 23, 2017, at 2:22 AM, Alexander Fedotov <
> alexander.fedot...@gmail.com> wrote:
> >
> > Hi folks,
> >
> > In scope of the IGNITE-3207
> >  Ignite 2.0 Migration
> > Guide needs to be updated
> > Apache+Ignite+2.0+Migration+Guide
> >  Apache+Ignite+2.0+Migration+Guide>
> > .
> > Unfortunately, currently I don't have rights to edit the page.
> > Who can grant me ones?
> >
> > --
> > Kind regards,
> > Alexander.
>
>


-- 
Kind regards,
Alexander.

Re: Apache Ignite SEO Audit

[Dmitriy Setrakyan]

Mauricio, we already have similar file added for google site verification:
google9276fe2a42313afd.html

Can you reuse this one?

D.

On Mon, Jan 23, 2017 at 12:20 PM, Mauricio Stekl 
wrote:

> Hi,
> In order to setup the Google Webmaster Tools account on ignite.apache.org,
> I would need to upload the attached .html file to the root of the website.
>
> Could someone with commit privileges help me with this?
>
> Thanks in advance.
>
> Mauricio
>
>
>
>
>
>
>
> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan 
> wrote:
>
> Hi Terry, this should not be a problem. I have sent you the credentials
> privately. Let me know if you need more help.
>
> D.
>
> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman 
> wrote:
>
> Hi All,
>
>
>
> In order to proceed effectively with the SEO audit of the Apache Ignite
> website, we need admin access to the Google Analytics account for the
> website. Once we have the Google Analytics account access, we will setup
> Google Webmaster Tools for the website (it isn't setup currently) which
> will
> give us insights into a variety of characteristics of the website.
>
>
>
> If anyone has any concerns about this, please let me know. I look forward
> to
> getting started on this audit.
>
>
>
> Thanks,
>
>
>
> Terry
>
>
>
>
>
>
>
>
>
>
>

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

Hi Denis, 
Yes, in the docroot of the site so that the file could be access by visiting 
http://ignite.apache.org/googlea0d19c18a89c8306.html 


Thanks again.

Mauricio


> On Jan 23, 2017, at 17:23, Denis Magda  wrote:
> 
> Hi Mauricio,
> 
> Do I need to put it under the root folder of the site?
> 
> —
> Denis
> 
>> On Jan 23, 2017, at 12:20 PM, Mauricio Stekl  wrote:
>> 
>> Hi, 
>> In order to setup the Google Webmaster Tools account on ignite.apache.org 
>> , I would need to upload the attached .html file 
>> to the root of the website. 
>> 
>> Could someone with commit privileges help me with this? 
>> 
>> Thanks in advance. 
>> 
>> Mauricio
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> On Jan 19, 2017, at 19:29, Dmitriy Setrakyan >> > wrote:
>>> 
>>> Hi Terry, this should not be a problem. I have sent you the credentials
>>> privately. Let me know if you need more help.
>>> 
>>> D.
>>> 
>>> On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman >> >
>>> wrote:
>>> 
 Hi All,
 
 
 
 In order to proceed effectively with the SEO audit of the Apache Ignite
 website, we need admin access to the Google Analytics account for the
 website. Once we have the Google Analytics account access, we will setup
 Google Webmaster Tools for the website (it isn't setup currently) which
 will
 give us insights into a variety of characteristics of the website.
 
 
 
 If anyone has any concerns about this, please let me know. I look forward
 to
 getting started on this audit.
 
 
 
 Thanks,
 
 
 
 Terry
 
 
 
 
 
 
 
 
>> 
> 

Adding ML to Ignite, IGNITE-4572

[Nikita Ivanov]

Igniters,
I'd like to kick off the conversation on adding ML capabilities to Ignite
as it relates to IGNITE-4572.

I started off some preliminary steps on this ticket and would like to
invite anyone interesting in implementing distributed core algebra on top
of Ignite to join me in this work. There's plenty to contribute from ideas
and math, to implementation, tests, and documentation.

Background on IGNITE-4572.

Throughout many conferences last year I have heard the sentiment that one
of the functional areas that is badly missing in Ignite is a library of
distributed Machine Learning algorithms. In fact, it was frequently noted
as the only reason not to finally migrate from Spark to Ignite...

ML, in general, is a pretty large undertaking and there are more than a few
ways to approach this in the context of Ignite.  One idea I'd like to chew
on and prototype is to look close at Apache Mahout (
http://mahout.apache.org/). After a deep look at Mahout codebase I don't
believe the outright code-level integration is feasible at this points -
but we can certainly borrow as many ideas from it as possible.

Thanks!
--
Nikita Ivanov

Re: Abandon of the non-throwing version of C++ client API

[Denis Magda]

Guys,

I found the initial discussion from the early times of our C++ client:
http://apache-ignite-developers.2346864.n4.nabble.com/C-exception-handling-strategy-td778.html
 


Vovan, that time you were on the side of error-code methods. Why have you 
changed you mind proposing to make the throwing version default one? Any new 
tendency in C++ community? 

—
Denis

> On Jan 23, 2017, at 2:56 AM, Vladimir Ozerov  wrote:
> 
> +1 to Igor's idea. Ignite is relatively high-level product and we do not 
> expect ultra-optimized users who cannot allow exceptions to be enabled. 
> Macros should be a good workaround for them, though.
> 
> On Sat, Jan 21, 2017 at 6:47 PM, Denis Magda  > wrote:
> Hi Igor,
> 
> My C++ experience is based only on error code methods. This is why I thought 
> that exceptions based approach is unrelated to C++ at all.
> 
> I do remember we discussed all the pros and cons of these ways before. Could 
> you find that old discussion and share it here? I'm on a mobile now, not easy 
> to do on my own.
> 
> Denis
> 
> 
> On Friday, January 20, 2017, Igor Sapego  > wrote:
> Hi Igniters,
> 
> I'm the guy who mostly contribute in C++ Ignite client and I 
> need your advice. Mostly I'd like to hear from our users and 
> those who are experienced in C++. Currently we have two 
> versions of most API methods - the throwing one and the 
> one that returns error through output argument. This was initially
> done because we were not sure which way of error-reporting 
> is going to be preferred by our users.
> 
> Now this approach bloats C++ API a lot and makes it harder to
> maintain and optimize code. I propose like to abandon and deprecate
> non-throwing version of API and only leave throwing version,
> but first I want to hear from you guys - what do you think? Does
> anyone use non-throwing version of the API? Maybe your toolchain
> does not support exceptions or are you disabling them on purpose?
> 
> For those who prefer disabling exceptions I propose to introduce
> some macros like IGNITE_DISABLE_EXCEPTIONS and add
> some thread-local error-storing mechanism like ignite::GetLastError().
> 
> What do you guys think?
> 
> Best Regards,
> Igor
> 

Re: Apache Ignite SEO Audit

[Mauricio Stekl]

Hi, In order to setup the Google Webmaster Tools account on ignite.apache.org, I would need to upload the attached .html file to the root of the website. Could someone with commit privileges help me with this? Thanks in advance. Mauriciogoogle-site-verification: googlea0d19c18a89c8306.htmlOn Jan 19, 2017, at 19:29, Dmitriy Setrakyan  wrote:Hi Terry, this should not be a problem. I have sent you the credentialsprivately. Let me know if you need more help.D.On Thu, Jan 19, 2017 at 11:35 AM, Terry Erisman wrote:Hi All,In order to proceed effectively with the SEO audit of the Apache Ignitewebsite, we need admin access to the Google Analytics account for thewebsite. Once we have the Google Analytics account access, we will setupGoogle Webmaster Tools for the website (it isn't setup currently) whichwillgive us insights into a variety of characteristics of the website.If anyone has any concerns about this, please let me know. I look forwardtogetting started on this audit.Thanks,Terry

Re: SQL: Index hints

[Denis Magda]

Created a ticket so that we don’t forget about this new H2 capability.
https://issues.apache.org/jira/browse/IGNITE-4594 


Alexander P. feel free to assign it on yourself.

—
Denis

> On Jan 23, 2017, at 10:05 AM, Dmitriy Setrakyan  wrote:
> 
> Very cool! Would be nice to add it to Ignite.
> 
> On Mon, Jan 23, 2017 at 3:17 AM, Sergi Vladykin 
> wrote:
> 
>> Guys,
>> 
>> Recently in H2 we've merged a very important feature: index hints. It is an
>> additional MySQL-like syntax:
>> 
>> SELECT * FROM  my_table USE INDEX (index_a) WHERE A = 1
>> 
>> It will be very easy to support this in Ignite.
>> 
>> Alex,
>> 
>> Since you are working on better SQL Enum support and it will require H2
>> upgrade anyways, you can add this stuff to Ignite as well.
>> 
>> Sergi
>> 

Re: Regarding gsoc 2017

[Denis Magda]

Hello Prakhar,

Yes, we will submit several projects to GSOC. I planned to do it this week. 
Please keep an eye on this discussion [1] that will be updated going forward.

As for machine learning this is [2] the first task related to this activity. 
Most likely Nikita will send some proposal to the dev list soon and some part 
of the functionality will go to GSOC.

[1] 
http://apache-ignite-developers.2346864.n4.nabble.com/Google-Summer-Of-Code-2017-td13180.html
[2] https://issues.apache.org/jira/browse/IGNITE-4572

—
Denis

> On Jan 23, 2017, at 5:11 AM, Prakhar Pratyush  wrote:
> 
> Hello,
> 
> My name is Prakhar Pratyush. I am a 4th year student at IIT Roorkee. My
> primary areas of interests are Machine Learning, and web development. I am
> willing to participate in gsoc during this summer.
> 
> While searching for open source projects in machine learning, I stumbled
> upon this discussion page (
> http://apache-ignite-developers.2346864.n4.nabble.com/Google-Summer-Of-Code-2017-td13180.html).
> 
> 
> Is Apache-Ignite applying for gsoc 2017 ?
> 
> Also, there was a mention of "Machine Learning Grid implementation or
> integration with Spark MLib" on that discussion page. I'd like to know more
> about this machine learning project, or other ML related projects, if any.
> 
> Thanks
> Prakhar

Re: Ignite ASF Confluence edit rights

[Denis Magda]

Dmitriy, Cos,

Does contributors (not committers) have write permissions on Ignite wiki? Looks 
like they don’t.

Alexander, as a temporal solution, please ask the committer that reviewed and 
merged your changes to update this page as well.

—
Denis

> On Jan 23, 2017, at 2:22 AM, Alexander Fedotov  
> wrote:
> 
> Hi folks,
> 
> In scope of the IGNITE-3207
>  Ignite 2.0 Migration
> Guide needs to be updated
> Apache+Ignite+2.0+Migration+Guide
> 
> .
> Unfortunately, currently I don't have rights to edit the page.
> Who can grant me ones?
> 
> -- 
> Kind regards,
> Alexander.

Re: We are live on OpenHub!

[Denis Magda]

Thanks Raul,

Have you reported to OpenHub guys? If you haven’t I will go ahead with this.

—
Denis

> On Jan 22, 2017, at 1:01 PM, Raúl Kripalani  wrote:
> 
> That's strange. Ordinarily it should update every 48h, have a look here and
> maybe consider reporting an incident to the OpenHub guys:
> http://blog.openhub.net/status/
> 
> Cheers!
> 
> On 21 Jan 2017 00:36, "Denis Magda"  wrote:
> 
>> Just came across OpenHub statistics in regards to Apache Ignite. More than
>> a
>> year has already passed since Raul set the things up and now we can see our
>> ups and downs in a colorful way:
>> https://www.openhub.net/p/apache-ignite
>> 
>> My observations:
>> - code almost doubled in a number of lines.
>> - Vladimir Ozerov tool leadership in top contributors chart
>> (https://www.openhub.net/p/apache-ignite/contributors/summary).
>> - number of contributors grows but slowly.
>> 
>> BTW, *Raul*, is there any way to force the update OpenHub side? The info is
>> 3 month old.
>> 
>> 
>> 
>> --
>> View this message in context: http://apache-ignite-
>> developers.2346864.n4.nabble.com/We-are-live-on-OpenHub-tp6277p13893.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>> 

Re: Allow distributed SQL query execution over explicit set of partitions

[Alexei Scherbakov]

Dmitriy,

This still can make sense for some scenarios, because we could limit number
of initial map requests reducing overall query overhead.

Are you still sure we need to throw an exception ?

2017-01-23 1:49 GMT+03:00 Dmitriy Setrakyan :

> On Sun, Jan 22, 2017 at 5:06 AM, Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > Yes, it will be possible because distributed joins are executed using
> > broadcast queries.
> >
> >
> In this case why even bother supporting non-collocated joins? We need to
> throw an exception in this case.
>
> 2017-01-22 15:49 GMT+03:00 Dmitriy Setrakyan :
> >
> > > On Sun, Jan 22, 2017 at 4:46 AM, Alexei Scherbakov <
> > > alexey.scherbak...@gmail.com> wrote:
> > >
> > > > Dmitriy,
> > > >
> > > > ScanQueries currently support only one partition. I will extend it to
> > > > support multiple partitions.
> > > >
> > > > For distributed joins partitions will only be applied on "map" query
> > > step.
> > > >
> > >
> > > Will it still be possible to get data from the partitions that were not
> > > specified?
> > >
> >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
> >
>



-- 

Best regards,
Alexei Scherbakov

Re: SQL: Index hints

[Dmitriy Setrakyan]

Very cool! Would be nice to add it to Ignite.

On Mon, Jan 23, 2017 at 3:17 AM, Sergi Vladykin 
wrote:

> Guys,
>
> Recently in H2 we've merged a very important feature: index hints. It is an
> additional MySQL-like syntax:
>
> SELECT * FROM  my_table USE INDEX (index_a) WHERE A = 1
>
> It will be very easy to support this in Ignite.
>
> Alex,
>
> Since you are working on better SQL Enum support and it will require H2
> upgrade anyways, you can add this stuff to Ignite as well.
>
> Sergi
>

[jira] [Created] (IGNITE-4592) .NET: Binary enums are handled incorrectly

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4592:
--

 Summary: .NET: Binary enums are handled incorrectly
 Key: IGNITE-4592
 URL: https://issues.apache.org/jira/browse/IGNITE-4592
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


* BinaryEnum is represented as {{int typeId}} + {{int value}}
* BinaryEnumArray is represented as {{int typeId}} + {{int[] value}}

In most cases we handle this incorrectly, using only {{int value}}:
* {{BinaryObjectBuilder.WriteAsPredefined}} 
* {{BinarySystemHandlers.*EnumArray}}
etc

Add tests thich verify that .NET binary enum handling is consistent with Java.



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

[GitHub] ignite pull request #1455: IGNITE-2216: Added support for query fields disam...

[skalashnikov]

GitHub user skalashnikov opened a pull request:

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

IGNITE-2216: Added support for query fields disambiguation



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

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

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

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


commit 3dc30669b0e2e644ddf2aba3e80a2d2aab175db2
Author: skalashnikov 
Date:   2017-01-18T16:45:51Z

IGNITE-2216: Added reproducer sample code

commit be2ef9d9057d1ec4bd62cd475f2752109dee4f72
Author: skalashnikov 
Date:   2017-01-19T17:15:05Z

IGNITE-2216: draft fix which barely pass the test

commit 771e1730e6e913b91119b5af7ac309708cc88c52
Author: skalashnikov 
Date:   2017-01-23T15:27:20Z

IGNITE-2216: adding prefix only for field of superclass




---
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: Make async API great again

[Taras Ledkov]

Each compute method produces task. For 'run', 'call' etc. methods the 
classes of tasks are internal.
There are tests checking the task session by ComputeTaskFuture for these 
methods.
I think we have to leave real class of future is 
ComputeTaskInternalFuture#ComputeFuture to compatibility.


The class of the future at the public API may be changed.


On 20.01.2017 17:54, Vladimir Ozerov wrote:

IgniteCompute was designed this way initially. See IgniteCompute.future()
override. May be it makes sense to leave this type only for execute(...)
methods.

On Fri, Jan 20, 2017 at 5:45 PM, Semyon Boikov  wrote:


Hi Taras,

Why 'async' methods return ComputeTaskFuture, not just IgniteFuture? It
seems that ComputeTaskFuture is needed only for tasks?




On Fri, Jan 20, 2017 at 5:18 PM, Taras Ledkov 
wrote:


Gents

I've done changes of the IgniteCompute as a subtask of the whole async

API

refactoring (https://issues.apache.org/jira/browse/IGNITE-4580).
Please check the new version of the public API (
https://github.com/gridgain/apache-ignite/blob/b81621bf2e8a
35b20989f95ff52c0f6d91dd75d6/modules/core/src/main/java/
org/apache/ignite/IgniteCompute.java)

Please look through the new API and let me know any comments.

--
Taras Ledkov
Mail-To: tled...@gridgain.com




--
Taras Ledkov
Mail-To: tled...@gridgain.com

[GitHub] ignite pull request #1454: Ignite 4003 1.7 no drop

[agura]

GitHub user agura opened a pull request:

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

Ignite 4003 1.7 no drop



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

$ git pull https://github.com/agura/incubator-ignite ignite-4003-1.7-no-drop

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

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






---
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 #555: IGNITE-2703 .NET: Dynamic class registration for n...

[ptupitsyn]

Github user ptupitsyn closed the pull request at:

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


---
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-4591) File interop_target.h is missing from source-release

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-4591:
---

 Summary: File interop_target.h is missing from source-release
 Key: IGNITE-4591
 URL: https://issues.apache.org/jira/browse/IGNITE-4591
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Igor Sapego


File 
{{modules\platforms\cpp\core\include\ignite\impl\interop\interop_target.h}} 
missing from source releases of versions 1.7.0 and 1.8.0. It is present, 
however, in repository and binary releases.



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

Re: Sort nodes in the ring in order to minimize the number of reconnections

[Александр Меньшиков]

Igor, I have thought about approach what you are talking about. It need add
new field named like "sortedNodes" with custom ordering, which will have
the same items as "nodes" field, because "nodes" has being used with
default ordering in other methods. It have this advantages:

1. Method "nextNode" will look simpler.
2. Method "nextNode" will work faster, because using of method
TreeSet#higher() will be available. But that possibility had not been used
in original code. And I don't why.


But also have some disadvantages because new field "sortedNodes" will be
strongly connected with "nodes":
1. It need copy-paste all code, which modifies "nodes" in 4 other methods.
It will decrease maintainability.
2. Field "nodes" is being used with "copy-on-write" algorithm. So state of
"nodes" and "sortedNodes" can be inconsistent. Maybe it's okay, in fact I
just don't know. But any way in future it may become a problem.

So my opinion is that "presorted" approach can work a little bit faster
(number of nodes never can't be so big that O(log n) became more faster
than O(n)), but code complexity will been increased, because it will add
one logic connection inside the whole class "TcpDiscoveryNodesRing".

Yakov, can you settle our argument?

2017-01-20 16:30 GMT+03:00 Игорь Г :

> Alexander, maybe you should use presorted collection in
> TcpDiscoveryNodesRing.nextNode instead of iterating through unsorted one
> every time?
>

[GitHub] ignite pull request #1453: IGNITE-4511: Set QueryIndexType.SORTED by default...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-4511: Set QueryIndexType.SORTED by default for an index 

Fixed

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

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

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

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


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

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

commit 55f7594fd0595a4269c3972446ba4ebe30c12442
Author: Alexandr Kuramshin 
Date:   2017-01-13T09:26:39Z

ignite-4293 Do not need store deserialized value for BinaryMarshaller

(cherry picked from commit d10946b)

commit 1665a615030201a7c9a51fd479868c3533b103b5
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 80f7325211f6adb8a9f3cc0bd1192ded28aeff77
Author: Anton Vinogradov 
Date:   2017-01-16T09:15:17Z

Merge branch 'ignite-1.7.5-p1' into ignite-1.7.6

commit 496fb173d55a8ea0702fcb70a4e807f61d8fc53e
Author: nikolay_tikhonov 
Date:   2017-01-16T10:19:51Z

IGNITE-4513 Improve debug logging.

commit c3eae9fecff5ad01390170c034dca39c216a097c
Author: Andrey Novikov 
Date:   2017-01-16T03:33:16Z

IGNITE-4518 Fixed parallel load of cache. - Fixes #1426.

Signed-off-by: Andrey Novikov 

(cherry picked from commit 79401b2)

commit 71176473f9fd0aa2088ba4e611ba4b7fc45e76b8
Author: Andrey Novikov 
Date:   2017-01-16T04:22:34Z

IGNITE-4545 Added cache for router hostnames. - Fixes #1428.

Signed-off-by: Andrey Novikov 

(cherry picked from commit 27ba69b)

commit 22b7e76c00a77a06388bcef869f29d1a572a306a
Author: sboikov 
Date:   2017-01-17T09:33:32Z

ignite-4465 Prevent cache entry eviction while it is loaded from store 
(otherwise loaded value can be not stored in cache).

commit 67225b24dbc77ed70f5aa6bac6d750623c67045d
Author: sboikov 
Date:   2017-01-17T09:46:28Z

Merge remote-tracking branch 'remotes/community/ignite-1.7.5-p1' into 
ignite-1.7.6

commit 74d0dcc6c56118f9e4fdaa4aa70d25d1abe7b80e
Author: Andrey V. Mashenkov 
Date:   2017-01-17T12:00:08Z

IGNITE-3964: SQL: add support for custom table name. This closes #1301.

commit 8e622e41de4acf365da7f933a08b6d31bae11124
Author: Andrey V. Mashenkov 
Date:   2017-01-17T12:18:33Z

IGNITE-4247: Sql queries supports table alias. This closes #1297.

commit a922ac9d17f91f25aaa2bac9f0a2622dbd04c9bb
Author: Andrey V. Mashenkov 
Date:   2017-01-17T12:31:04Z

IGNITE-4540: IndexingSPI can be used without have default H2 Indexing 
enabled. This closes #1423.

commit d0c0bcece7d8e9d373aaf13a210f6d890e5ad48b
Author: Andrey V. Mashenkov 
Date:   2017-01-17T13:19:02Z

IGNITE-3867: Fixed ScanQuery ignores pageSize property. This closes #1406.

commit b54a481315a45c7a6c8f70534f655e14b25cc439
Author: dkarachentsev 
Date:   2017-01-18T09:05:22Z

ignite-4525 - Near reader is created when value is loaded from store.

commit 2eb24cad277e14322cf42155697cae78e0f80e13
Author: dkarachentsev 
Date:   2017-01-18T10:00:25Z

ignite-4147 - Fail if joining node has different of cluster SSL 
configuration.

commit 2305e38345d8a7ca812d265d00eaca5bb7d6adb1
Author: Andrey V. Mashenkov 
Date:   2017-01-18T11:57:53Z

Minor fixes in tests.

commit ecf4b8b5bd05a5c1120e08d9951cddd26d0e924c
Author: Andrey V. Mashenkov 
Date:   2017-01-18T14:22:14Z

Minor fix test for Ignite-4247.

commit f9aaf0353cea54afefea4caac74b1583eb17969b
Author: agura 
Date:   2017-01-18T15:04:45Z

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

commit d396398c1b4660b3bca24d2650a10f6c0677b4df
Author: sboikov 
Date:   2016-12-02T07:36:41Z

ignite-4314 cache.clear should not destroy offheap map

(cherry picked from commit 88c06ec)

commit 51e1f874624c428cc93e9c16407ec5a8b4cf8420
Author: sboikov 
Date:   2017-01-19T07:52:42Z

Throw CacheException from queries API.

commit 9c9175d4a84194a224a4020e6185d1e2aee0a5aa
Author: dkarachentsev 
Date:   2017-01-19T08:19:18Z

ignite-4147 - Rollback due to test failing on many 

Regarding gsoc 2017

[Prakhar Pratyush]

Hello,

My name is Prakhar Pratyush. I am a 4th year student at IIT Roorkee. My
primary areas of interests are Machine Learning, and web development. I am
willing to participate in gsoc during this summer.

While searching for open source projects in machine learning, I stumbled
upon this discussion page (
http://apache-ignite-developers.2346864.n4.nabble.com/Google-Summer-Of-Code-2017-td13180.html).


Is Apache-Ignite applying for gsoc 2017 ?

Also, there was a mention of "Machine Learning Grid implementation or
integration with Spark MLib" on that discussion page. I'd like to know more
about this machine learning project, or other ML related projects, if any.

Thanks
Prakhar

[jira] [Created] (IGNITE-4590) Lock/unlock operations are hanging when topology changed

[Nikolay Tikhonov (JIRA)]

Nikolay Tikhonov created IGNITE-4590:


 Summary: Lock/unlock operations are hanging when topology changed
 Key: IGNITE-4590
 URL: https://issues.apache.org/jira/browse/IGNITE-4590
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Nikolay Tikhonov


Lock/unlock operations are hanging when topology changed. See attached test.



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

[GitHub] ignite pull request #1452: IGNITE-4581: Async API: IgniteCache refactoring

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-4581: Async API: IgniteCache refactoring 



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

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

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

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


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 6090ebdfcd0ea3840b0d32cb10197b43615e1e89
Author: devozerov 
Date:   2017-01-05T09:23:06Z

Merge branch 'master' into ignite-2.0

commit 77ca2e636c73e464f833f227c4894df0785ae9e2
Author: devozerov 
Date:   2017-01-16T13:07:49Z

Merge branch 'master' into ignite-2.0

commit d14e0727b3dd61ab5ec2957133d77dbc25e9ba68
Author: tledkov-gridgain 
Date:   2017-01-16T13:36:25Z

IGNITE-4428: Hadoop: moved HadoopMapReducePlanner and dependent classes to 
public space. This closes #1389. This closes #1394.

commit f1365421c299b754a10edf8b6f156aeeb5ff0ce1
Author: tledkov-gridgain 
Date:   2017-01-16T13:57:27Z

IGNITE-4503: Hadoop: added boundary checks to HadoopDirectDataInput. This 
closes # 1416.

commit e08b6ff48916edfab2dbd5d62092be5a1f819a2f
Author: Pavel Tupitsyn 
Date:   2017-01-19T10:34:59Z

Merge branch 'master' into ignite-2.0

commit 43adf8a3f09c6b29fe3e70f62dbc58251d8d7cb9
Author: Ivan Veselovskiy 
Date:   2017-01-19T11:34:23Z

IGNITE-4219: Hadoop: fixed serialization of long strings. This closes #1409.

commit 454b9769e72775c5f6b44a36f0eef84bcce13bd7
Author: devozerov 
Date:   2017-01-19T11:34:43Z

Merge remote-tracking branch 'origin/ignite-2.0' into ignite-2.0

commit 4cd332b781cf700b99402eed2363f988f6403602
Author: Sergey Chugunov 
Date:   2017-01-19T12:05:09Z

IGNITE-4157 Use  discovery custom messages instead of marshaller cache - 
Fixes #1271.

Signed-off-by: Alexey Goncharuk 

commit d0a6c57aa26bca64ef68370c0ebdb5ce45bcc765
Author: Pavel Tupitsyn 
Date:   2017-01-19T14:10:41Z

IGNITE-4441 Define plugin API in .NET

This closes #1362

commit 34a97833905a33bdb31b8e4580a576c2142313a7
Author: Alexey Goncharuk 
Date:   2017-01-19T15:04:23Z

IGNITE-4157 - Added mapping update listener stub

commit e8377167b7b8dd020a93d92c743e4541dcd000ed
Author: Pavel Tupitsyn 
Date:   2017-01-20T10:00:40Z

Merge branch 'master' into ignite-2.0

commit 38cb67d45eb91e20ad4b92a490747534f5e8febb
Author: Pavel Tupitsyn 
Date:   2017-01-20T13:09:57Z

Merge branch 'master' into ignite-2.0

commit b1918f0bb776e7e0ae8c544df0c5f653e5193b96
Author: tledkov-gridgain 

[jira] [Created] (IGNITE-4589) Possible starvation during rebalancing for marshaller cache

[Nikolay Tikhonov (JIRA)]

Nikolay Tikhonov created IGNITE-4589:


 Summary: Possible starvation during rebalancing for marshaller 
cache
 Key: IGNITE-4589
 URL: https://issues.apache.org/jira/browse/IGNITE-4589
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.8
Reporter: Nikolay Tikhonov


When Ignite processing supply messages (rebalancing) in marshaller threads and 
calling marshaller cache from them, but responses also should be proccessed in 
marshaller threadpool. It leads to starvation.

{noformat}
marshaller-cache-#26%test-node%" #117 prio=5 os_prio=0 tid=0x7f89e40c6000 
nid=0x1dc waiting on condition [0x7f8a3fffc000]
   java.lang.Thread.State: WAITING (parking)
 at sun.misc.Unsafe.park(Native Method)
 - parking to wait for <0xc206d318> (a 
org.apache.ignite.internal.processors.cache.distributed.dht.GridPartitionedGetFuture)
 at java.util.concurrent.locks.LockSupport.park(Unknown Source)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown
 Source)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown
 Source)
 at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown
 Source)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:159)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:117)
 at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getTopologySafe(GridCacheAdapter.java:1340)
 at 
org.apache.ignite.internal.MarshallerContextImpl.className(MarshallerContextImpl.java:195)
 at 
org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
 at 
org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
 at java.io.ObjectInputStream.readObject(Unknown Source)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readFields(OptimizedObjectInputStream.java:491)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readSerializable(OptimizedObjectInputStream.java:579)
 at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:927)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:324)
 at java.io.ObjectInputStream.readObject(Unknown Source)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readFields(OptimizedObjectInputStream.java:491)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readSerializable(OptimizedObjectInputStream.java:579)
 at 
org.apache.ignite.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:927)
 at 
org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:324)
 at java.io.ObjectInputStream.readObject(Unknown Source)
 at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:218)
 at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
 at 
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1614)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1680)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
 at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
 at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
 at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
 at org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9722)
 at org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
 at 
org.apache.ignite.internal.processors.cacheobject.IgniteCacheObjectProcessorImpl.unmarshal(IgniteCacheObjectProcessorImpl.java:111)
 at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.unmarshal(CacheObjectBinaryProcessorImpl.java:811)
 at 
org.apache.ignite.internal.processors.cache.CacheObjectImpl.finishUnmarshal(CacheObjectImpl.java:109)
 at 
org.apache.ignite.internal.processors.cache.GridCacheEntryInfo.unmarshal(GridCacheEntryInfo.java:416)
 at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplyMessageV2.finishUnmarshal(GridDhtPartitionSupplyMessageV2.java:245)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1229)
 at 

SQL: Index hints

[Sergi Vladykin]

Guys,

Recently in H2 we've merged a very important feature: index hints. It is an
additional MySQL-like syntax:

SELECT * FROM  my_table USE INDEX (index_a) WHERE A = 1

It will be very easy to support this in Ignite.

Alex,

Since you are working on better SQL Enum support and it will require H2
upgrade anyways, you can add this stuff to Ignite as well.

Sergi

Re: Timeout for ordered message

[Yakov Zhdanov]

Val, let's do the following.

1. We need to state in javadocs that we expect unordered msg handler to be
added in advance, otherwise message get ignored. This may require user
should have an ability to add listeners before start (same as in case with
event listeners) - or can this be done in lifecycle listener? I think no.
2. You can add overload for ordered msg sending without timeout and explain
in javadoc that this will work similar to endless timeout.

Makes sense?


--Yakov

2017-01-13 0:54 GMT+03:00 Valentin Kulichenko :

> Yakov,
>
> I'm talking only about user messages and public API. What is the purpose of
> the timeout in this case?
>
> I'm just trying to properly understand the semantics and at least fix the
> JavaDoc as it seems to be completely wrong now.
>
> -Val
>
> On Thu, Jan 12, 2017 at 2:41 AM, Yakov Zhdanov 
> wrote:
>
> > Not sure what we are trying to achieve here. Unordered messages are
> simply
> > ignored if there is no listener. We always expect unordered listeners to
> be
> > installed before at least for internal messages, but this is not the case
> > for some ordered messages, i.e. task session requests.
> >
> > --Yakov
> >
> > 2017-01-12 0:03 GMT+03:00 Valentin Kulichenko <
> > valentin.kuliche...@gmail.com
> > >:
> >
> > > Yakov,
> > >
> > > So you confirm that my understanding is correct and JavaDoc is wrong,
> > > right?
> > >
> > > As for 'no listener' scenario, that's a good point, but it should be
> > > applicable to unordered messages as well then. The most confusing part
> > here
> > > is that we have timeout only for unordered messages while there is
> > nothing
> > > specific about them in terms of delivery.
> > >
> > > How about we two methods, with and without timeout, for both ordered
> and
> > > unordered messages? Like this:
> > >
> > > void send(@Nullable Object topic, Object msg);
> > > void send(@Nullable Object topic, Object msg, long timeout); // New
> > method.
> > > void sendOrdered(@Nullable Object topic, Object msg); // New method.
> > > void sendOrdered(@Nullable Object topic, Object msg, long timeout);
> > >
> > > This change will make API consistent and will not break compatibility.
> > > Thoughts?
> > >
> > > -Val
> > >
> > > On Wed, Jan 11, 2017 at 12:20 AM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > If you send ordered messages to a node and listener on receiving side
> > has
> > > > not yet been added then timeout is still sufficient to clean up
> > buffered
> > > > messages.
> > > >
> > > > --Yakov
> > > >
> > > > 2017-01-10 23:36 GMT+03:00 Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com>:
> > > >
> > > > > Yakov,
> > > > >
> > > > > I was actually asking about the public API for messaging
> > > > > (IgniteMessaging#sendOrdered
> > > > > method). Here is the JavaDoc:
> > > > >
> > > > >  * The {@code timeout} parameter specifies how long an out-of-order
> > > > message
> > > > > will stay in a queue,
> > > > >  * waiting for messages that are ordered ahead of it to arrive. If
> > > > timeout
> > > > > expires, then all ordered
> > > > >  * messages that have not arrived before this message will be
> > skipped.
> > > > When
> > > > > (and if) expired messages
> > > > >  * actually do arrive, they will be ignored.
> > > > >
> > > > > I remember that we indeed had this scenario possible a while ago,
> but
> > > > then
> > > > > implementation of ordered messaging was reworked and 'out-of-order
> > > > message'
> > > > > can't happen anymore. Is this correct? If so, I think the timeout
> > > should
> > > > be
> > > > > removed from the API.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Tue, Jan 10, 2017 at 2:34 AM, Yakov Zhdanov <
> > yzhda...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Val, timeout still makes sense for task sessions. It is possible
> > that
> > > > all
> > > > > > jobs mapped to node have been completed, but node still receives
> > > > > > attributes. Attributes are sent in ordered messages. It may
> happen
> > so
> > > > > that
> > > > > > node may start processing jobs for that task again and this way
> all
> > > the
> > > > > > attributes will be available. If task timeout elapses then
> messages
> > > get
> > > > > > cleared. Please let me know if you still have questions.
> > > > > >
> > > > > > Thanks!
> > > > > > --
> > > > > > Yakov Zhdanov, Director R
> > > > > > *GridGain Systems*
> > > > > > www.gridgain.com
> > > > > >
> > > > > > 2017-01-06 1:02 GMT+03:00 Valentin Kulichenko <
> > > > > > valentin.kuliche...@gmail.com
> > > > > > >:
> > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > Anyone knows what is the purpose of the timeout for
> > > > > > > IgniteMessaging#sendOrdered method?
> > > > > > >
> > > > > > > void sendOrdered(@Nullable Object topic, Object msg, long
> > timeout);
> > > > > > >
> > > > > > > It seems to me that in current implementation messages are
> always
> > > > > ordered
> > > > > > > on 

Re: Abandon of the non-throwing version of C++ client API

[Vladimir Ozerov]

+1 to Igor's idea. Ignite is relatively high-level product and we do not
expect ultra-optimized users who cannot allow exceptions to be enabled.
Macros should be a good workaround for them, though.

On Sat, Jan 21, 2017 at 6:47 PM, Denis Magda  wrote:

> Hi Igor,
>
> My C++ experience is based only on error code methods. This is why I
> thought that exceptions based approach is unrelated to C++ at all.
>
> I do remember we discussed all the pros and cons of these ways before.
> Could you find that old discussion and share it here? I'm on a mobile now,
> not easy to do on my own.
>
> Denis
>
>
> On Friday, January 20, 2017, Igor Sapego  wrote:
>
>> Hi Igniters,
>>
>> I'm the guy who mostly contribute in C++ Ignite client and I
>> need your advice. Mostly I'd like to hear from our users and
>> those who are experienced in C++. Currently we have two
>> versions of most API methods - the throwing one and the
>> one that returns error through output argument. This was initially
>> done because we were not sure which way of error-reporting
>> is going to be preferred by our users.
>>
>> Now this approach bloats C++ API a lot and makes it harder to
>> maintain and optimize code. I propose like to abandon and deprecate
>> non-throwing version of API and only leave throwing version,
>> but first I want to hear from you guys - what do you think? Does
>> anyone use non-throwing version of the API? Maybe your toolchain
>> does not support exceptions or are you disabling them on purpose?
>>
>> For those who prefer disabling exceptions I propose to introduce
>> some macros like IGNITE_DISABLE_EXCEPTIONS and add
>> some thread-local error-storing mechanism like ignite::GetLastError().
>>
>> What do you guys think?
>>
>> Best Regards,
>> Igor
>>
>

[GitHub] ignite pull request #1450: Ignite 4036 1 Fix. Near cache is not expired toge...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite 4036 1 Fix. Near cache is not expired together with corresponding 
server cache



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

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

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

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


commit de50287d493acc73186926d34431733bc76c549b
Author: vozerov-gridgain 
Date:   2016-10-03T07:07:33Z

Revert "IGNITE-3191 - Fixed ordering of fields in binary objects"

This reverts commit d1e3a78ae569fa5d5692816db44f2c677e1b8283.

commit 5e7ef8644ad824b87d4797e59133eb783ff8b098
Author: vozerov-gridgain 
Date:   2016-10-03T07:37:25Z

Merge branch 'ignite-1.6.9' into ignite-1.6.10

commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f
Author: vozerov-gridgain 
Date:   2016-10-03T07:40:04Z

IGNITE-2881: Fixed SPI queries.

commit b5902336ba7a2c313b61050e38d7e033d310d55f
Author: vozerov-gridgain 
Date:   2016-10-03T07:47:13Z

Merge branch 'ignite-1.7.2' into ignite-1.7.3

commit 36087cfa6867d29e7db56cf47e7a87b5aa9b63dc
Author: vozerov-gridgain 
Date:   2016-10-03T07:48:50Z

Merge branch 'ignite-1.6.9' into ignite-1.7.3

commit 0b66d2d7b695cf370a4b8a717844ad67742c6090
Author: sboikov 
Date:   2016-10-03T09:04:03Z

ignite-3601 Do not check version on commit for read-only serializable 
transactions.

commit 3c9e254ee762dfef0b27b5b95a63502069904d70
Author: ptupitsyn 
Date:   2016-08-15T13:40:24Z

IGNITE-1629 .NET: Introduced native logging facility

commit ae4ae71f0481662a5fb13eb8ee63a17e6c4c3802
Author: Pavel Tupitsyn 
Date:   2016-10-03T09:16:34Z

IGNITE-1629 .NET: Introduced native logging facility - fix merge

commit 9f211e413332931f0fb1190744ddd7c7f38fd213
Author: tledkov-gridgain 
Date:   2016-10-03T09:26:12Z

IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This 
closes #1003.

commit fa698d6fcfde0006423ef009337dbef58ac62515
Author: vozerov-gridgain 
Date:   2016-10-03T10:33:12Z

Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by 
multicast IP finder.

commit 1c82cd04fadc61ab5da02e1d395aedfb28a039da
Author: Pavel Tupitsyn 
Date:   2016-08-23T10:28:40Z

IGNITE-3279 .NET: NLog logger

commit 48b293db4d443b4d8739f709ff12f19aad008b84
Author: Pavel Tupitsyn 
Date:   2016-10-03T11:08:07Z

IGNITE-3279 .NET: NLog logger

commit bba019fd5076412ca43c10a32fd300b6031ccd0b
Author: vozerov-gridgain 
Date:   2016-10-03T14:25:20Z

IGNITE-3980: Processed failing tests in query suites. This closes #1137.

commit 02f48d72364fb0c52e95aef8ed383a14ee531bf6
Author: ptupitsyn 
Date:   2016-10-04T08:17:54Z

IGNITE-3820: .NET: Added log4net integration. This closes #1138.

commit bfdb5c3b374fd3512481cf16779d227d7f96e569
Author: Saikat Maitra 
Date:   2016-10-04T09:40:35Z

IGNITE-3841 Web console added check for eviction policy max mem and max 
size consistency. Fixes #1136.

commit a92f20b5cc75e6b80b2731da0192723526b0c1dc
Author: vozerov-gridgain 
Date:   2016-10-04T11:10:26Z

IGNITE-3597: Removed static work directory.

commit d45383b69cc68c0ec967ebd673b197e437720214
Author: Pavel Tupitsyn 
Date:   2016-10-04T15:48:25Z

.NET: Fix code analysis warnings

commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1
Author: vozerov-gridgain 
Date:   2016-10-06T07:14:59Z

IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130.

commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497
Author: tledkov-gridgain 
Date:   2016-10-06T07:22:50Z

IGNITE-3163 IGFS: Added working directory support to 
IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This 
closes #1132.

commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701
Author: vozerov-gridgain 
Date:   2016-10-06T09:03:48Z

IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This 
closes #903. This closes #1145.

commit 952be8b995050b34379006dd6e739da3fe3b49e3
Author: Dmitriy Govorukhin 
Date:   2016-10-07T12:00:09Z

Squashed commit of the following:

commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1
Author: sboikov 
Date:   Fri Oct 7 13:08:38 2016 +0300

minor

commit 7fe88a1cb21f794ee55a176ab36d895cbf916528

Ignite ASF Confluence edit rights

[Alexander Fedotov]

Hi folks,

In scope of the IGNITE-3207
 Ignite 2.0 Migration
Guide needs to be updated
Apache+Ignite+2.0+Migration+Guide

.
Unfortunately, currently I don't have rights to edit the page.
Who can grant me ones?

-- 
Kind regards,
Alexander.

[jira] [Created] (IGNITE-4588) .NET: Optimize BinaryReader frame handling

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4588:
--

 Summary: .NET: Optimize BinaryReader frame handling
 Key: IGNITE-4588
 URL: https://issues.apache.org/jira/browse/IGNITE-4588
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.8
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


BinaryReader has a concept of {{frame}}, which is position, header, raw flag, 
etc. When reading nested objects we preserve previous frame in a bunch of 
variables and restore them afterwards.

This process can be improved by using a struct: backup/restore in one line, 
easier to grasp which parameters belong to a frame.



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