Webinar: Building Consistent and Highly Available Distributed Systems with Apache Ignite

[Valentin Kulichenko]

Igniters,

This Wednesday (August 2nd at 11am PT), I will host a webinar where I will
go through different Apache Ignite features and capabilities that allow to
build consistent and highly available distributed systems. More information
here:
https://ignite.apache.org/events.html#building-consistent-and-highly-available-distributed-systems

Tough questions are welcome!

-Val

Re: Pentaho BI tool documentation for Ignite

[Prachi Garg]

Reviewed and made minor edits.

-Prachi

On Mon, Jul 31, 2017 at 1:58 PM, Denis Magda  wrote:

> Igniters,
>
> Slava Kopltilin contributed a new documentation that shows how to hook up
> Pentaho SQL tool with Ignite via the JDBC driver. Thanks, Slava!
> https://apacheignite-tools.readme.io/docs/pentaho
>
> Prachi, could you review the language and improve it whenever is needed?
>
> —
> Denis

Pentaho BI tool documentation for Ignite

[Denis Magda]

Igniters,

Slava Kopltilin contributed a new documentation that shows how to hook up 
Pentaho SQL tool with Ignite via the JDBC driver. Thanks, Slava!
https://apacheignite-tools.readme.io/docs/pentaho

Prachi, could you review the language and improve it whenever is needed?

—
Denis

Re: Updating Apache Camel Integration to the latest version

[Raul Kripalani]

Sure, I'll try to do it this week. Cheers!

On 31 Jul 2017 21:22, "Denis Magda"  wrote:

> Hello Raul,
>
> Would you mind updating the Apache Camel integration to the latest Ignite
> version (2.1)? The current one is pretty outdated - 1.9.
> https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations
>
> —
> Denis
>
>

Zeppelin, MyBatis and Vert.x update to AI 2.1

[Denis Magda]

Andrey, Roman,

As maintainers of the projects in the subject, could you please go ahead and 
update Ignite version to 2.1 there?
https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations 


—
Denis

[GitHub] ignite pull request #2369: IGNITE-3935 test

[xtern]

Github user xtern closed the pull request at:

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


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

Updating Apache Camel Integration to the latest version

[Denis Magda]

Hello Raul,

Would you mind updating the Apache Camel integration to the latest Ignite 
version (2.1)? The current one is pretty outdated - 1.9. 
https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations 


—
Denis

[GitHub] ignite pull request #2369: IGNITE-3935 test

[xtern]

GitHub user xtern opened a pull request:

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

IGNITE-3935 test



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

$ git pull https://github.com/xtern/ignite test/ignite-3935

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

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


commit 9aa2f6dcc6ee478c284b8b48d3a828bb9e473b85
Author: Pereslegin Pavel 
Date:   2017-07-31T20:14:21Z

IGNITE-3935 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 #2368: Ignite 425

[nizhikov]

Github user nizhikov closed the pull request at:

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


---
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: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

[Anton Vinogradov]

Cos,

1) RC3 and RC4 files are the same because source was not changed from RC3
to RC4.
RC4 was upload to dev at revision 20551, but RC3 was upload earlier. These
are the two different commits, not a clone.
Also, RC4 was signed by me, but RC3 by Semen.

2)
> what was the point of posting rc3 to the dist, instead of rc4

We *NEVER* upload RC3 to the release.

Svn log:
> Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-*rc4*,
Revision, 20650)

On Mon, Jul 31, 2017 at 10:44 PM, Konstantin Boudnik  wrote:

> thanks for checking!
> Technically, speaking we were voting on a different zip-file, that has
> been signed by the release manager. So, I am not sure what was the
> point of posting rc3 to the dist, instead of rc4. Unless of course the
> following statement
> > The artifacts has been upload for RC3 and due to no code changes for RC4
> they not updated
> was groundless.
>
> You see where I am going with this?
> --
>   With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Mon, Jul 31, 2017 at 12:21 PM, Anton Vinogradov  wrote:
> > Cos,
> >
> > I see that artifacts and checksums are the same:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/?p=20551
> >
> > RC3:
> > md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip
> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-
> rc3/apache-ignite-2.1.0-src.zip.md5?p=20551)
> > sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23
> apache-ignite-2.1.0-src.zip
> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-
> rc3/apache-ignite-2.1.0-src.zip.sha1?p=20551)
> >
> > RC4:
> > md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip
> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-
> rc4/apache-ignite-2.1.0-src.zip.md5?p=20551)
> > sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23
> apache-ignite-2.1.0-src.zip
> > (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-
> rc4/apache-ignite-2.1.0-src.zip.sha1?p=20551)
> >
> >
> > Svn log for RC4 -> 2.1.0:
> >
> > Revision: 20651
> > Author: av
> > Date: 27 июля 2017 г. 18:15:43
> > Message:
> > Release 2.1.0-rc4
> > 
> > Deleted : /dev/ignite/2.1.0-rc4
> > Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-rc4,
> > Revision, 20650)
> >
> > On Mon, Jul 31, 2017 at 8:37 PM, Konstantin Boudnik 
> wrote:
> >>
> >> Wait, the artifacts for RC3 were signed differently and had different
> >> checksums than those of RC4. Why the former is now are the official
> >> release artifact if that [VOTE] has been cancelled?
> >> --
> >>   With regards,
> >> Konstantin (Cos) Boudnik
> >> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> >>
> >> Disclaimer: Opinions expressed in this email are those of the author,
> >> and do not necessarily represent the views of any company the author
> >> might be affiliated with at the moment of writing.
> >>
> >>
> >> On Sat, Jul 29, 2017 at 9:17 AM, Sergey Kozlov 
> >> wrote:
> >> > Denis, that's true.
> >> >
> >> > The artifacts has been upload for RC3 and due to no code changes for
> RC4
> >> > they not updated
> >> >
> >> > On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda 
> >> > wrote:
> >> >
> >> >> I guess that's the JAR's creation time by the build procedure and not
> >> >> the
> >> >> uploading time. Looks valid to me.
> >> >>
> >> >> Denis
> >> >>
> >> >> On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote:
> >> >>
> >> >> > Anton,
> >> >> >
> >> >> >
> >> >> > http://repo.maven.apache.org/maven2/org/apache/ignite/
> ignite-core/2.1.0/
> >> >> >
> >> >> > The timestamp for uploading the artifact is 2017-07-20 17:35, Is
> that
> >> >> > correct?
> >> >> >
> >> >> >
> >> >> > 在 2017/7/28 上午2:06, Anton Vinogradov 写道:
> >> >> >
> >> >> >> Done.
> >> >> >>
> >> >> >> - Maven artifacts released
> >> >> >> - Sources released
> >> >> >> - Site updated
> >> >> >> - Git tag added
> >> >> >>
> >> >> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov 
> >> >> wrote:
> >> >> >>
> >> >> >> Igniters,
> >> >> >>>
> >> >> >>> Apache Ignite 2.1.0 release (RC4) has been accepted.
> >> >> >>>
> >> >> >>> 7 "+1" votes received:
> >> >> >>>
> >> >> >>> - Valentin Kulichenko (binding)
> >> >> >>> - Nikolai Tikhonov (binding)
> >> >> >>> - Alexey Kuznetsov (binding)
> >> >> >>> - Yakov Zhdanov (binding)
> >> >> >>> - Konstantin Boudnik (binding)
> >> >> >>> - Andrey Gura (binding)
> >> >> >>> - Denis Magda (binding)
> >> >> >>>
> >> >> >>> Vote thread:
> >> >> >>>
> >> >> >>> http://apache-ignite-developers.2346864.n4.nabble.
> >> >> >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html
> >> >> >>>
> >> >> >>> Ignite 2.1.0 will be released soon. Woohoo!
> >> >> >>>
> >> >> >>>
> 

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

[Konstantin Boudnik]

thanks for checking!
Technically, speaking we were voting on a different zip-file, that has
been signed by the release manager. So, I am not sure what was the
point of posting rc3 to the dist, instead of rc4. Unless of course the
following statement
> The artifacts has been upload for RC3 and due to no code changes for RC4 they 
> not updated
was groundless.

You see where I am going with this?
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Mon, Jul 31, 2017 at 12:21 PM, Anton Vinogradov  wrote:
> Cos,
>
> I see that artifacts and checksums are the same:
>
> https://dist.apache.org/repos/dist/dev/ignite/?p=20551
>
> RC3:
> md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip
> (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/apache-ignite-2.1.0-src.zip.md5?p=20551)
> sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23  apache-ignite-2.1.0-src.zip
> (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/apache-ignite-2.1.0-src.zip.sha1?p=20551)
>
> RC4:
> md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip
> (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/apache-ignite-2.1.0-src.zip.md5?p=20551)
> sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23  apache-ignite-2.1.0-src.zip
> (https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/apache-ignite-2.1.0-src.zip.sha1?p=20551)
>
>
> Svn log for RC4 -> 2.1.0:
>
> Revision: 20651
> Author: av
> Date: 27 июля 2017 г. 18:15:43
> Message:
> Release 2.1.0-rc4
> 
> Deleted : /dev/ignite/2.1.0-rc4
> Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-rc4,
> Revision, 20650)
>
> On Mon, Jul 31, 2017 at 8:37 PM, Konstantin Boudnik  wrote:
>>
>> Wait, the artifacts for RC3 were signed differently and had different
>> checksums than those of RC4. Why the former is now are the official
>> release artifact if that [VOTE] has been cancelled?
>> --
>>   With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Sat, Jul 29, 2017 at 9:17 AM, Sergey Kozlov 
>> wrote:
>> > Denis, that's true.
>> >
>> > The artifacts has been upload for RC3 and due to no code changes for RC4
>> > they not updated
>> >
>> > On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda 
>> > wrote:
>> >
>> >> I guess that's the JAR's creation time by the build procedure and not
>> >> the
>> >> uploading time. Looks valid to me.
>> >>
>> >> Denis
>> >>
>> >> On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote:
>> >>
>> >> > Anton,
>> >> >
>> >> >
>> >> > http://repo.maven.apache.org/maven2/org/apache/ignite/ignite-core/2.1.0/
>> >> >
>> >> > The timestamp for uploading the artifact is 2017-07-20 17:35, Is that
>> >> > correct?
>> >> >
>> >> >
>> >> > 在 2017/7/28 上午2:06, Anton Vinogradov 写道:
>> >> >
>> >> >> Done.
>> >> >>
>> >> >> - Maven artifacts released
>> >> >> - Sources released
>> >> >> - Site updated
>> >> >> - Git tag added
>> >> >>
>> >> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov 
>> >> wrote:
>> >> >>
>> >> >> Igniters,
>> >> >>>
>> >> >>> Apache Ignite 2.1.0 release (RC4) has been accepted.
>> >> >>>
>> >> >>> 7 "+1" votes received:
>> >> >>>
>> >> >>> - Valentin Kulichenko (binding)
>> >> >>> - Nikolai Tikhonov (binding)
>> >> >>> - Alexey Kuznetsov (binding)
>> >> >>> - Yakov Zhdanov (binding)
>> >> >>> - Konstantin Boudnik (binding)
>> >> >>> - Andrey Gura (binding)
>> >> >>> - Denis Magda (binding)
>> >> >>>
>> >> >>> Vote thread:
>> >> >>>
>> >> >>> http://apache-ignite-developers.2346864.n4.nabble.
>> >> >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html
>> >> >>>
>> >> >>> Ignite 2.1.0 will be released soon. Woohoo!
>> >> >>>
>> >> >>>
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > Sergey Kozlov
>> > GridGain Systems
>> > www.gridgain.com
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

[Anton Vinogradov]

Cos,

I see that artifacts and checksums are the same:

https://dist.apache.org/repos/dist/dev/ignite/?p=20551

RC3:
md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip (
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/apache-ignite-2.1.0-src.zip.md5?p=20551
)
sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23
 apache-ignite-2.1.0-src.zip (
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc3/apache-ignite-2.1.0-src.zip.sha1?p=20551
)

RC4:
md5 -> 3cd75e1f4e402d8c93b155386afe675c  apache-ignite-2.1.0-src.zip (
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/apache-ignite-2.1.0-src.zip.md5?p=20551
)
sha -> b60e95130a6ba758fdf48b8261ac2cd028278f23
 apache-ignite-2.1.0-src.zip (
https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/apache-ignite-2.1.0-src.zip.sha1?p=20551
)


Svn log for RC4 -> 2.1.0:

Revision: 20651
Author: av
Date: 27 июля 2017 г. 18:15:43
Message:
Release 2.1.0-rc4

Deleted : /dev/ignite/2.1.0-rc4
Added : /release/ignite/2.1.0 (Copy from path: /dev/ignite/2.1.0-rc4,
Revision, 20650)

On Mon, Jul 31, 2017 at 8:37 PM, Konstantin Boudnik  wrote:

> Wait, the artifacts for RC3 were signed differently and had different
> checksums than those of RC4. Why the former is now are the official
> release artifact if that [VOTE] has been cancelled?
> --
>   With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Sat, Jul 29, 2017 at 9:17 AM, Sergey Kozlov 
> wrote:
> > Denis, that's true.
> >
> > The artifacts has been upload for RC3 and due to no code changes for RC4
> > they not updated
> >
> > On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda 
> wrote:
> >
> >> I guess that's the JAR's creation time by the build procedure and not
> the
> >> uploading time. Looks valid to me.
> >>
> >> Denis
> >>
> >> On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote:
> >>
> >> > Anton,
> >> >
> >> > http://repo.maven.apache.org/maven2/org/apache/ignite/
> ignite-core/2.1.0/
> >> >
> >> > The timestamp for uploading the artifact is 2017-07-20 17:35, Is that
> >> > correct?
> >> >
> >> >
> >> > 在 2017/7/28 上午2:06, Anton Vinogradov 写道:
> >> >
> >> >> Done.
> >> >>
> >> >> - Maven artifacts released
> >> >> - Sources released
> >> >> - Site updated
> >> >> - Git tag added
> >> >>
> >> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov 
> >> wrote:
> >> >>
> >> >> Igniters,
> >> >>>
> >> >>> Apache Ignite 2.1.0 release (RC4) has been accepted.
> >> >>>
> >> >>> 7 "+1" votes received:
> >> >>>
> >> >>> - Valentin Kulichenko (binding)
> >> >>> - Nikolai Tikhonov (binding)
> >> >>> - Alexey Kuznetsov (binding)
> >> >>> - Yakov Zhdanov (binding)
> >> >>> - Konstantin Boudnik (binding)
> >> >>> - Andrey Gura (binding)
> >> >>> - Denis Magda (binding)
> >> >>>
> >> >>> Vote thread:
> >> >>>
> >> >>> http://apache-ignite-developers.2346864.n4.nabble.
> >> >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html
> >> >>>
> >> >>> Ignite 2.1.0 will be released soon. Woohoo!
> >> >>>
> >> >>>
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
>

Re: Apache Ignite Site Changed its Face

[Denis Magda]

Cos,

Got your point. Let’s put out this activity to dedicated discussions so that 
nobody interested missed any significant change to the site. Here is the first 
topic and nearest task to work on:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-Site-Design-and-UX-Improvements-td20242.html

—
Denis

> On Jul 31, 2017, at 10:35 AM, Konstantin Boudnik  wrote:
> 
> Arguably, the website and its theme represents the projects' message.
> And should be reflecting that of the community, and not just the
> people who happen to be working on the changes in the website code.
> 
> Fixing existing or adding new content is different story: have a JIRA,
> fix and commit it. Changing the style, content and the overall message
> (in this case: "Ignite is now an in-memory DB") looks like a perfect
> candidate to reach out for the consensus first. Consensus building
> isn't an "extra noise", really.
> --
>  With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> 
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
> 
> 
> On Fri, Jul 28, 2017 at 5:42 PM, Denis Magda  wrote:
>> The site and documentation is improved almost in per day basis. I spot the
>> changes happened to the project on @dev and @user and adjust the materials
>> and site to reflect them with the help of contributirs and committers who
>> worked on a specific functionality. Don't see much sense to generate extra
>> noise while that work is in progress.
>> 
>> That's exactly what happened to the front page. The new memory architecture
>> and the persistent store was discussed on @dev before many times and the
>> site was updated accordingly.
>> 
>> --
>> Denis
>> 
>> 
>> On Friday, July 28, 2017, Konstantin Boudnik  wrote:
>>> 
>>> Was there any discussion here on dev@ about this change? Just curious
>>> if my search-foo is failing me...
>>> 
>>> Thanks!
>>> --
>>>  With regards,
>>> Konstantin (Cos) Boudnik
>>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>> 
>>> Disclaimer: Opinions expressed in this email are those of the author,
>>> and do not necessarily represent the views of any company the author
>>> might be affiliated with at the moment of writing.
>>> 
>>> 
>>> On Thu, Jul 27, 2017 at 2:32 PM, Denis Magda  wrote:
 Igniters,
 
 In favor of the 2.1 release we’ve reworked and renewed the front page
 and some of the existing pages of the site:
 https://ignite.apache.org
 
 The front page reflects the main additions of 2.1, durable memory +
 persistent store, that opened new opportunities for Ignite. Please welcome
 new Ignite that “provides in-memory performance with the durability of
 disk”:
 https://twitter.com/denismagda/status/890683287852601345
 
 —
 Denis

Apache Ignite Site Design and UX Improvements

[Denis Magda]

Igniters,

Prachi, Viktoria, Dmitriy S. and I are going to improve the site’s design and 
UX in August. Here is a high-level syllabus 
(https://issues.apache.org/jira/browse/IGNITE-5887 
):

• The layout has to be optimized for all kind of screen resolutions 
(high-resolution, mobile, tablet, desktop).
• The header should be optimized for mobile and tablets screens - there 
has to be only one header menu and redundant items should be removed from it 
(like the download button).
• The front page design is different from the design of the rest of the 
pages. The UI of the rest of the pages has to be improved (background, fonts, 
etc.)
• Make sure everything looks and behaves similarly in all the 
mainstream browsers (Safari, Chrome, Edge, Firefox).


You’re always welcomed to share your thoughts or participate in this activity. 
In the meanwhile, we’re planning to share all the major milestones with all of 
you here on @dev.

—
Denis

[jira] [Created] (IGNITE-5887) Apache Ignite Site Redesign

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5887:
---

 Summary: Apache Ignite Site Redesign
 Key: IGNITE-5887
 URL: https://issues.apache.org/jira/browse/IGNITE-5887
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Prachi Garg


Apache Ignite site designed has to be revisited and reworked in the following 
way:
* The layout has to be optimized for all kind of screen resolutions 
(high-resolution, mobile, tablet, desktop).
* The header should be optimized for mobile and tablets screens - there has to 
be only one header menu and redundant items should be removed from it (like the 
download button).
*  The front page design is different from the design of the rest of the pages. 
The UI of the rest of the pages has to be improved (background, fonts, etc.)
* Make sure everything looks and behaves similarly in all the mainstream 
browsers (Safari, Chrome, Edge, Firefox).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

SQL Getting Started Guide

[Denis Magda]

Igniters,

There is a lot of SQL related documentation available for Ignite. However, the 
one can get lost in it when he/she does her first steps on a learning path. 
It’s time to simplify these are first steps with a clear and straightforward 
getting started guide. I’ve put the requirements into this JIRA ticket:
https://issues.apache.org/jira/browse/IGNITE-5886 


Please share your thoughts in JIRA or in this discussion.

Akmal, who perfected his technical writer skills working for IBM, volunteered 
to take over this task. Akmal, please create an account in Ignite JIRA and 
share it with us. You’ll be able to assign the task on yourself afterwards.
https://issues.apache.org/jira/projects/IGNITE 


Moreover, once the guide is ready Prachi will use it as a basis for the new SQL 
screencast we need to produce.

—
Denis

[jira] [Created] (IGNITE-5886) Ignite SQL Getting Started

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5886:
---

 Summary: Ignite SQL Getting Started 
 Key: IGNITE-5886
 URL: https://issues.apache.org/jira/browse/IGNITE-5886
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Priority: Critical
 Fix For: 2.2


The goal of the task is to create an Ignite SQL Getting Started with the 
following sections:
* Connection to the cluster using JDBC and ODBC drivers. The 
content/description for both drivers will be the same. The only difference will 
be in the source code that can be shown in different tabs of "Code Sample" 
readme.io element. Take a look at the DDL doc [1] that incorporates the source 
code for Java API and JDBC.
* SQL tables and indexes creation using DDL statements [1]. There should be at 
least two tables. Use the affinity collocation for them. {{CREATE TABLE}} 
command support {{AFFINITYKEY}} parameter that can be passed to {{WITH}} block.
* Preload data using {{INSERT}} statements.
* Show how to query data with {{SELECT}} statements including joins.
* Show to update the data sets with {{UPDATE}} and {{DELETE}} statements.

Here is the page to document (presently it's hidden and visible only for 
documentation contributors):
https://apacheignite.readme.io/v2.1/docs/getting-started-sql

Use JDBC thin driver [2] for the JDBC connectivity. The ODBC is well documented 
here [3] and we have a lot of examples for it in Ignite deliverables.  

[1] https://apacheignite.readme.io/v2.1/docs/distributed-ddl
[2] https://apacheignite.readme.io/v2.1/docs/jdbc-driver#jdbc-thin-driver
[3] https://apacheignite.readme.io/v2.1/docs/odbc-driver



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

[Konstantin Boudnik]

Wait, the artifacts for RC3 were signed differently and had different
checksums than those of RC4. Why the former is now are the official
release artifact if that [VOTE] has been cancelled?
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Sat, Jul 29, 2017 at 9:17 AM, Sergey Kozlov  wrote:
> Denis, that's true.
>
> The artifacts has been upload for RC3 and due to no code changes for RC4
> they not updated
>
> On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda  wrote:
>
>> I guess that's the JAR's creation time by the build procedure and not the
>> uploading time. Looks valid to me.
>>
>> Denis
>>
>> On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote:
>>
>> > Anton,
>> >
>> > http://repo.maven.apache.org/maven2/org/apache/ignite/ignite-core/2.1.0/
>> >
>> > The timestamp for uploading the artifact is 2017-07-20 17:35, Is that
>> > correct?
>> >
>> >
>> > 在 2017/7/28 上午2:06, Anton Vinogradov 写道:
>> >
>> >> Done.
>> >>
>> >> - Maven artifacts released
>> >> - Sources released
>> >> - Site updated
>> >> - Git tag added
>> >>
>> >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov 
>> wrote:
>> >>
>> >> Igniters,
>> >>>
>> >>> Apache Ignite 2.1.0 release (RC4) has been accepted.
>> >>>
>> >>> 7 "+1" votes received:
>> >>>
>> >>> - Valentin Kulichenko (binding)
>> >>> - Nikolai Tikhonov (binding)
>> >>> - Alexey Kuznetsov (binding)
>> >>> - Yakov Zhdanov (binding)
>> >>> - Konstantin Boudnik (binding)
>> >>> - Andrey Gura (binding)
>> >>> - Denis Magda (binding)
>> >>>
>> >>> Vote thread:
>> >>>
>> >>> http://apache-ignite-developers.2346864.n4.nabble.
>> >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html
>> >>>
>> >>> Ignite 2.1.0 will be released soon. Woohoo!
>> >>>
>> >>>
>> >
>> >
>>
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com

Re: Apache Ignite Site Changed its Face

[Konstantin Boudnik]

Arguably, the website and its theme represents the projects' message.
And should be reflecting that of the community, and not just the
people who happen to be working on the changes in the website code.

Fixing existing or adding new content is different story: have a JIRA,
fix and commit it. Changing the style, content and the overall message
(in this case: "Ignite is now an in-memory DB") looks like a perfect
candidate to reach out for the consensus first. Consensus building
isn't an "extra noise", really.
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Fri, Jul 28, 2017 at 5:42 PM, Denis Magda  wrote:
> The site and documentation is improved almost in per day basis. I spot the
> changes happened to the project on @dev and @user and adjust the materials
> and site to reflect them with the help of contributirs and committers who
> worked on a specific functionality. Don't see much sense to generate extra
> noise while that work is in progress.
>
> That's exactly what happened to the front page. The new memory architecture
> and the persistent store was discussed on @dev before many times and the
> site was updated accordingly.
>
> --
> Denis
>
>
> On Friday, July 28, 2017, Konstantin Boudnik  wrote:
>>
>> Was there any discussion here on dev@ about this change? Just curious
>> if my search-foo is failing me...
>>
>> Thanks!
>> --
>>   With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Thu, Jul 27, 2017 at 2:32 PM, Denis Magda  wrote:
>> > Igniters,
>> >
>> > In favor of the 2.1 release we’ve reworked and renewed the front page
>> > and some of the existing pages of the site:
>> > https://ignite.apache.org
>> >
>> > The front page reflects the main additions of 2.1, durable memory +
>> > persistent store, that opened new opportunities for Ignite. Please welcome
>> > new Ignite that “provides in-memory performance with the durability of
>> > disk”:
>> > https://twitter.com/denismagda/status/890683287852601345
>> >
>> > —
>> > Denis

Re: Apache Ignite Site Changed its Face

[Konstantin Boudnik]

Arguably, the website and its theme represents the projects' message.
And should be reflecting that of the community, and not just the
people who happen to be working on the changes in the website code.

Fixing existing or adding new content is different story: have a JIRA,
fix and commit it. Changing the style, content and the overall message
(in this case: "Ignite is now an in-memory DB") looks like a perfect
candidate to reach out for the consensus first.

--
  With regards,
Konstantin (Cos) Boudnik


On Fri, Jul 28, 2017 at 5:42 PM, Denis Magda  wrote:
> The site and documentation is improved almost in per day basis. I spot the
> changes happened to the project on @dev and @user and adjust the materials
> and site to reflect them with the help of contributirs and committers who
> worked on a specific functionality. Don't see much sense to generate extra
> noise while that work is in progress.
>
> That's exactly what happened to the front page. The new memory architecture
> and the persistent store was discussed on @dev before many times and the
> site was updated accordingly.
>
> --
> Denis
>
>
> On Friday, July 28, 2017, Konstantin Boudnik  wrote:
>>
>> Was there any discussion here on dev@ about this change? Just curious
>> if my search-foo is failing me...
>>
>> Thanks!
>> --
>>   With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Thu, Jul 27, 2017 at 2:32 PM, Denis Magda  wrote:
>> > Igniters,
>> >
>> > In favor of the 2.1 release we’ve reworked and renewed the front page
>> > and some of the existing pages of the site:
>> > https://ignite.apache.org
>> >
>> > The front page reflects the main additions of 2.1, durable memory +
>> > persistent store, that opened new opportunities for Ignite. Please welcome
>> > new Ignite that “provides in-memory performance with the durability of
>> > disk”:
>> > https://twitter.com/denismagda/status/890683287852601345
>> >
>> > —
>> > Denis

Re: сhecksum algorythm

[Konstantin Boudnik]

That won't guarantee the right choice, unfortunately. Some of the
popular projects are still using md5 ;(
Why not going with sha-512? This is release checksum'ing - we don't
care about computational difficulties nor efficiencies. It is done one
every few months. And we care in this case is the correctness and
robustness.
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Thu, Jul 27, 2017 at 6:28 AM, Anton Vinogradov
 wrote:
> Oleg,
>
> Let's check what's used at another popular Apache Projects.
>
> On Wed, Jul 26, 2017 at 11:10 PM, Dmitry Pavlov 
> wrote:
>
>> Hi Oleg,
>>
>> Both MD5 and SHA1 are deprecated and can't be considered as trustfull.
>>
>> I think at-least-256 bit member of the SHA-2 family (e. g. sha512) should
>> be used.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> ср, 26 июл. 2017 г. в 22:27, Oleg Ostanin :
>>
>> > Hi,
>> >
>> > We need to decide what сhecksum algorythm we should use for signing
>> release
>> > artifacts. Currently we use md5 and sha-1. sha-1 will be replaced by
>> > sha-256 soon. Should we keep md5 or use only sha-256?
>> >
>>

[jira] [Created] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5885:
--

 Summary: .NET: Add x86 tests on TeamCity
 Key: IGNITE-5885
 URL: https://issues.apache.org/jira/browse/IGNITE-5885
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.2


Just copy a configuration and change NUnit bitness.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5884) Change default pageSize of page memory to 4KB

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5884:
--

 Summary: Change default pageSize of page memory to 4KB
 Key: IGNITE-5884
 URL: https://issues.apache.org/jira/browse/IGNITE-5884
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Ivan Rakov
 Fix For: 2.2


Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2368: Ignite 425

[nizhikov]

GitHub user nizhikov opened a pull request:

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

Ignite 425

pull request to discuss changes

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

$ git pull https://github.com/nizhikov/ignite IGNITE-425

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

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


commit 7260b63a5c93080e09e0147eac735ca2b597058a
Author: Nikolay Izhikov 
Date:   2017-07-24T09:13:35Z

IGNITE-425: Implementation of ContinuousQueryWithTransformer

commit 50ef69043fd14d49bdcaf5f295a3b095dbe96151
Author: Nikolay Izhikov 
Date:   2017-07-24T15:12:01Z

IGNITE-425: Working on tests

commit 264e4e4d05a8525e55b1eb63b080711ff0deb32a
Author: Nikolay Izhikov 
Date:   2017-07-25T09:59:28Z

IGNITE-425: Working on tests

commit bc51690b15a262d2fd24c0573723cd3d45ba80a0
Author: Nikolay Izhikov 
Date:   2017-07-26T14:01:11Z

IGNITE-425: Working on tests




---
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-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5883:
--

 Summary: Ignite Start Nodes test suite is flaky
 Key: IGNITE-5883
 URL: https://issues.apache.org/jira/browse/IGNITE-5883
 Project: Ignite
  Issue Type: Bug
Reporter: Ivan Rakov


Ignite Start Nodes suite contains several flaky tests: 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes
Example runs with flaky fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2367: IGNITE-5866: Fix MetadataJob filter to exclude an...

[nizhikov]

GitHub user nizhikov opened a pull request:

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

IGNITE-5866: Fix MetadataJob filter to exclude any of system caches



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

$ git pull https://github.com/nizhikov/ignite IGNITE-5866

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

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


commit 46683787e6cb913c981a42041380adeb077ff5f7
Author: Nikolay Izhikov 
Date:   2017-07-31T13:28:32Z

IGNITE-5866: Fix MetadataJob filter to exclude any of system caches




---
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 #2366: IGNITE-5882 Duplicated dependency in pom.xml of c...

[daradurvs]

GitHub user daradurvs opened a pull request:

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

IGNITE-5882 Duplicated dependency in pom.xml of core module



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

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

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

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


commit e53e26aa5e0ce0fb2bcea6b7963ac1e1907635d7
Author: daradurvs 
Date:   2017-07-31T13:19:50Z

ignite-5882: duplicated property was removed




---
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-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5882:
--

 Summary: Duplicated dependency in pom.xml of core module
 Key: IGNITE-5882
 URL: https://issues.apache.org/jira/browse/IGNITE-5882
 Project: Ignite
  Issue Type: Bug
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur


{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
line 215, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING]
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2365: Ignite 5813 1.7

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 5813 1.7



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

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

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

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


commit d7dee5248332c6c6276c9e21aed4afb3abdd4340
Author: Pavel Tupitsyn 
Date:   2016-07-29T12:40:42Z

IGNITE-3604 .NET: Fix inconsistent namespace imports in examples

Conflicts:
modules/platforms/dotnet/Apache.Ignite.sln.DotSettings

commit 390c8d59cf8d44d9703e5fbf8d9c0f8028a4a172
Author: Pavel Tupitsyn 
Date:   2016-08-11T13:18:14Z

IGNITE-3675 .NET: Use separate caches for different entities in 
QueryExample.

commit 861c1736facdf76c71e93ddada0d8e15b5b2950c
Author: Pavel Tupitsyn 
Date:   2016-08-11T14:32:13Z

IGNITE-3673 .NET: Add examples for distributed joins.

commit 3a9cbed4e692e76ad884e60a4f5edc670e6b3c8f
Author: Pavel Tupitsyn 
Date:   2016-08-08T14:00:04Z

IGNITE-3630 .NET: Add pure binary mode example with put-get and queries.

commit d5e15af76044cf65385672f8528d48ecdeca3cb6
Author: Pavel Tupitsyn 
Date:   2016-11-02T09:02:00Z

IGNITE-4121 .NET: add ScanQuery example

commit 74f8308d10fc011c00e52efcdb315b35cc79e60a
Author: Pavel Tupitsyn 
Date:   2016-11-02T12:59:15Z

IGNITE-4123 .NET: Remove [Serializable] from Employee in examples

commit 92fff630fbf36c82f93bbd9ddd53d11bed44e772
Author: devozerov 
Date:   2016-11-02T14:50:51Z

Restored services compatibility.

commit a62a0136d295486d95c6e2ab5bba88270d831753
Author: dkarachentsev 
Date:   2016-11-02T16:07:45Z

GG-11655 - Fix merge

commit 348593986b56ddfcec4a4455e49d9b279eae4dc8
Author: devozerov 
Date:   2016-11-05T10:28:03Z

Merge branch 'ignite-1.7.3' into ignite-1.7.4

commit 175da6b7e394dd76c27d5155ff98a5b2ef03bb9d
Author: tledkov-gridgain 
Date:   2016-11-07T06:16:58Z

IGNITE-3432:  check data/meta cache names are different for different IGFS 
instances. This closes #1201

commit ead15193899d08f41491166003cabed0560f0c59
Author: Pavel Tupitsyn 
Date:   2016-11-07T07:49:03Z

IGNITE-4028 Get rid of OP_META in PlatformAbstractTarget

This closes #1192

commit 40ef2f5ae42826fe8fd077e3013e8f55c8512bdd
Author: Dmitriy Govorukhin 
Date:   2016-11-07T09:09:41Z

ignite-4178 support permission builder

commit df670c7d64046d282c053f296c47a4743c58c8b1
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:40:00Z

IGNITE-4118 .NET: Optimistic transaction example

This closes #1200

commit 474f22fda4c7cf4d7b2623c451cd7c10f0d8c636
Author: Pavel Tupitsyn 
Date:   2016-11-07T09:55:20Z

IGNITE-4119 .NET: add TransactionDeadlockException

commit fc7ce5a4d72145f2e8a86debeda264ef0a5b37e3
Author: isapego 
Date:   2016-11-07T10:26:05Z

IGNITE-4090: Added flags so stdint and limits can be used in C++.

commit a98804a249496ba9bafbc96daa7aaf25b3d36724
Author: Igor Sapego 
Date:   2016-11-07T11:00:00Z

IGNITE-4113: Added tests. Added Statement::Set/GetAttribute.

commit b1c7c9bb95c900083702d0ba0362edf3aea5a7b4
Author: sboikov 
Date:   2016-11-07T12:40:36Z

GG-11360 - Implement SQL queries cancellation
Fix for commit 80abd1b: for distributed joins need always send cancel 
request.

commit 319014de075c80fb15e58172cc24e35ce16b56cf
Author: Pavel Tupitsyn 
Date:   2016-11-07T14:53:40Z

IGNITE-4132 .NET: Improve BinaryConfiguration documentation

commit 950bad474ef29f9b808e74034c49a69d57eb2740
Author: dkarachentsev 
Date:   2016-11-08T11:03:34Z

GG-11655 - Restore service compatibility with releases before 1.5.30.

commit 3d19bfc2b66574e3945ce17c7a4dfe77d0070b8d
Author: dkarachentsev 
Date:   2016-11-08T11:04:36Z

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

commit 1612b6d66fed032182a41e90da71e6b986ae087b
Author: Pavel Tupitsyn 
Date:   2016-11-08T11:07:54Z

.NET: Fix minor analysis warnings

commit e821dc0083003bc81058b1cb223d8a8a2ee44daf
Author: Dmitriy Govorukhin 
Date:   2016-11-08T12:09:21Z

IGNITE-2079 (revert commit) GridCacheIoManager eats exception trail if it 
falls into the directed case

commit c2c82ca44befe4570325dd6cf2ba885e0d90596c
Author: Dmitriy Govorukhin 

Re: [ANNOUNCE] Apache Ignite 2.1.0 Released

[Pavel Tupitsyn]

Blog post on new .NET features:
https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.1/

On Fri, Jul 28, 2017 at 12:58 AM, Denis Magda  wrote:

> The Apache Ignite Community is pleased to announce the release of Apache
> Ignite 2.1.0 [1].
> https://blogs.apache.org/ignite/entry/apache-ignite-2-1-a
>
> This release incorporates a tremendous feature that was donated to the
> project - Ignite Persistent Store that altogether with the Durable Memory
> architecture empowers your applications with in-memory performance and
> durability of the disk.
>
> The Ignite Persistent Store is a distributed ACID and SQL-compliant disk
> store that transparently integrates with Ignite as an optional disk tier
> (SSD, Flash, 3D XPoint). Having the store enabled, you no longer need to
> keep all the data in memory or warm RAM up after the whole cluster restart.
> The persistent store will keep the superset of data and all the SQL indexes
> on disk making Ignite fully operational from disk.
>
> Considering these and many other changes we redefined the definition of
> Ignite a bit that know sounds:
>
> Ignite is a memory-centric platform
> • combining a distributed SQL database
> • with a key-value data grid
> • that is ACID-compliant
> • and horizontally scalable
>
> Learn more about the transition from the in-memory to memory-centric
> architecture from 2.1 announcement blog post:
> https://blogs.apache.org/ignite/entry/apache-ignite-2-1-a
>
> Attend the meetup today in Bay Area, CA to get insights on the new
> additions: https://www.meetup.com/Bay-Area-In-Memory-Computing/
> events/241381155/
>
> In addition the release includes support for CREATE and DROP table
> commands, adds new Machine Learning algorithms such as K-means clustering
> and regressions, enables peer-class-loading for .NET and provides Compute
> Grid APIs for C++.
>
> The full list of the changes can be found here: https://ignite.apache.org/
> releases/2.1.0/release_notes.html
>
> Please visit this page and check the release out:
> https://ignite.apache.org/download.cgi
>
>
> Regards,
> Denis
>
> [1] https://ignite.apache.org
>
>

[jira] [Created] (IGNITE-5881) Web Console: Improve the Сluster active/inactive states control

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5881:
-

 Summary: Web Console: Improve the Сluster active/inactive states 
control
 Key: IGNITE-5881
 URL: https://issues.apache.org/jira/browse/IGNITE-5881
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Vica Abramova






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2359: IGNITE-5866: Fix tests

[nizhikov]

Github user nizhikov closed the pull request at:

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


---
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-5880) BLAS integration phase 2

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5880:
--

 Summary: BLAS integration phase 2
 Key: IGNITE-5880
 URL: https://issues.apache.org/jira/browse/IGNITE-5880
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Yury Babak
 Fix For: 2.2


The second phase of BLAS integration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2357: IGNITE-5856: BLAS integration phase 1

[ybabak]

Github user ybabak closed the pull request at:

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


---
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 #2364: IGNITE-5823 Removed unused exceptions

[StalkXT]

GitHub user StalkXT opened a pull request:

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

IGNITE-5823 Removed unused exceptions



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

$ git pull https://github.com/StalkXT/ignite IGNITE-5823

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

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


commit 6f2f5244b1ffbdc0dcd19a6239359c7665fbb4aa
Author: StalkXT 
Date:   2017-07-31T10:17:43Z

IGNITE-5823 Removed unused exceptions




---
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: Changing public IgniteCompute API to improve changes in 5037 ticket

[Anton Vinogradov]

> Is the final design documented in the ticket?
No, since discussion in progress.

> Each job should somehow know the partition it's running over, on example,
> for setting it for ScanQuery or SqlQuery over local partition.
Seems, partition reserve() is enough to guarantee that partition will not
be evicted while Job in progress.

On Sat, Jul 29, 2017 at 5:14 PM, Dmitriy Setrakyan 
wrote:

> Is the final design documented in the ticket?
>
> On Sat, Jul 29, 2017 at 5:04 AM, Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > Anton,
> >
> > I'm fine with proposed solution using AffinityComputeTask.
> >
> > Please take care of issues pointed by me while implementing.
> >
> > Each job should somehow know the partition it's running over, on example,
> > for setting it for ScanQuery or SqlQuery over local partition.
> >
> > affinityExecute must support nullable set of partitions for splitting
> over
> > all available partitions.
> >
> > Val, any task requiring map/reduce API and data collocation is eligible.
> >
> > On example, in banking, it would be task sorting all depositors by amount
> > of money on deposit or some other complex criteria, or calculation of
> > income for each deposit.
> >
> > My client(bank) has plenty of such tasks.
> >
> > 2017-07-26 20:57 GMT+03:00 Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>:
> >
> > > Anton,
> > >
> > > This seems to be a completely separate issue. I don't see how it can be
> > > fixed by adding new APIs.
> > >
> > > -Val
> > >
> > > On Wed, Jul 26, 2017 at 3:56 AM, Anton Vinogradov <
> > > avinogra...@gridgain.com>
> > > wrote:
> > >
> > > > Val,
> > > >
> > > > AFAIK, affinityRun/Call has guarantee to be successfully executed on
> > > > unstable topology in case partition was not losed, only relocated to
> > > > another node during rebalancing.
> > > >
> > > > On Tue, Jul 25, 2017 at 10:44 PM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > Alexey,
> > > > >
> > > > > Is there exact use case that is currently not supported? I really
> > would
> > > > > like to see one, because such a big API change should add clear
> > value.
> > > > > ComputeGrid is not used very often, and so far I've never seen any
> > > > > questions from users about using it in conjunction with affinity
> > > > > collocation.
> > > > >
> > > > > What if we solve this on job level instead by adding the following
> > > > > interface:
> > > > >
> > > > > interface AffinityComputeJob extends ComputeJob {
> > > > > String cacheName();
> > > > > Object affinityKey();
> > > > > }
> > > > >
> > > > > Whenever load balancer sees this job, it maps it based on affinity.
> > > Will
> > > > > this work?
> > > > >
> > > > > -Val
> > > > >
> > > > > On Tue, Jul 25, 2017 at 12:37 PM, Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com> wrote:
> > > > >
> > > > > > Anton,
> > > > > >
> > > > > > How does topology change break this functionality? Closures
> > executed
> > > > with
> > > > > > affinityRun/Call fail over in the same way as any ComputeJob.
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Tue, Jul 25, 2017 at 5:48 AM, Anton Vinogradov <
> > > > > > avinogra...@gridgain.com> wrote:
> > > > > >
> > > > > >> Alexei,
> > > > > >>
> > > > > >> > How would task know the partition it is running over ?
> > > > > >> Not sure it necessary.
> > > > > >> You'll create pair partition-job at task's map phase.
> > > > > >>
> > > > > >> > How can I assign task for each cache partition ?
> > > > > >> Just implement map method generates map with size equals to
> > > partition
> > > > > >> count.
> > > > > >>
> > > > > >> > How can I enforce partition reservation if task works with
> > > multiple
> > > > > >> caches at once ?
> > > > > >> This possible only in case caches use safe affinity function.
> > > > > >> And it useful only it this case.
> > > > > >>
> > > > > >> On Tue, Jul 25, 2017 at 3:22 PM, Alexei Scherbakov <
> > > > > >> alexey.scherbak...@gmail.com> wrote:
> > > > > >>
> > > > > >> > Please read job instead task
> > > > > >> >
> > > > > >> > 2017-07-25 15:20 GMT+03:00 Alexei Scherbakov <
> > > > > >> alexey.scherbak...@gmail.com
> > > > > >> > >:
> > > > > >> >
> > > > > >> > > Main point of the issue is to provide clean API for working
> > with
> > > > > >> > > computations requiring data collocation
> > > > > >> > >
> > > > > >> > > affinityCall/Run provide the ability to run closure near
> data,
> > > but
> > > > > >> > > map/reduce API is a way reacher: continuous mapping, task
> > > session,
> > > > > >> etc.
> > > > > >> > >
> > > > > >> > > As for proposed API, I do not understand fully how it solves
> > the
> > > > > >> problem.
> > > > > >> > >
> > > > > >> > > Maxim, please provide detailed javadoc for each method and
> > each
> > > > > >> argument
> > > > > >> > > for presented API, and the answers to the following
> questions:
> > > > > >> > >
> > > > > >> > > 1. How would task know 

Re: [RESULT] [VOTE] Apache Ignite 2.1.0 Release (RC4)

[Anton Vinogradov]

Can also confirm that "2017-07-20 17:35" is correct.

On Sat, Jul 29, 2017 at 7:17 PM, Sergey Kozlov  wrote:

> Denis, that's true.
>
> The artifacts has been upload for RC3 and due to no code changes for RC4
> they not updated
>
> On Sat, Jul 29, 2017 at 5:09 PM, Denis Magda  wrote:
>
> > I guess that's the JAR's creation time by the build procedure and not the
> > uploading time. Looks valid to me.
> >
> > Denis
> >
> > On Saturday, July 29, 2017, 李玉珏@163 <18624049...@163.com> wrote:
> >
> > > Anton,
> > >
> > > http://repo.maven.apache.org/maven2/org/apache/ignite/
> ignite-core/2.1.0/
> > >
> > > The timestamp for uploading the artifact is 2017-07-20 17:35, Is that
> > > correct?
> > >
> > >
> > > 在 2017/7/28 上午2:06, Anton Vinogradov 写道:
> > >
> > >> Done.
> > >>
> > >> - Maven artifacts released
> > >> - Sources released
> > >> - Site updated
> > >> - Git tag added
> > >>
> > >> On Thu, Jul 27, 2017 at 4:24 PM, Anton Vinogradov 
> > wrote:
> > >>
> > >> Igniters,
> > >>>
> > >>> Apache Ignite 2.1.0 release (RC4) has been accepted.
> > >>>
> > >>> 7 "+1" votes received:
> > >>>
> > >>> - Valentin Kulichenko (binding)
> > >>> - Nikolai Tikhonov (binding)
> > >>> - Alexey Kuznetsov (binding)
> > >>> - Yakov Zhdanov (binding)
> > >>> - Konstantin Boudnik (binding)
> > >>> - Andrey Gura (binding)
> > >>> - Denis Magda (binding)
> > >>>
> > >>> Vote thread:
> > >>>
> > >>> http://apache-ignite-developers.2346864.n4.nabble.
> > >>> com/VOTE-Apache-Ignite-2-1-0-RC4-td19969.html
> > >>>
> > >>> Ignite 2.1.0 will be released soon. Woohoo!
> > >>>
> > >>>
> > >
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Re: master doesn't compile on jdk7

[Pavel Tupitsyn]

Related ticket: https://issues.apache.org/jira/browse/IGNITE-5706
Roman said he'll have a look.

On Mon, Jul 31, 2017 at 12:14 PM, Николай Ижиков 
wrote:

> Hello, Igniters.
>
> I think current master broken for jdk7 by  commit
> 1be77384122e41ce69db828e4432e56824c76f79
> I can't compile it locally.
> And I see same error message in TC.
>
> /data/teamcity/work/820be461cd64b574/modules/core/
> src/main/java/org/apache/ignite/internal/processors/rest/handlers/cache/
> GridCacheCommandHandler.java:[555,58] incompatible types required:
> java.util.Set found: java.util.HashSet extends java.lang.Object>
>
> http://ci.ignite.apache.org/viewLog.html?buildId=747237;
> tab=buildResultsDiv=Ignite20Tests_IgniteCache5
>
> Attached simple patch to fix compile error.
>
> --
> Nikolay Izhikov
> nizhikov@gmail.com
>

master doesn't compile on jdk7

[Николай Ижиков]

Hello, Igniters.

I think current master broken for jdk7 by  commit
1be77384122e41ce69db828e4432e56824c76f79
I can't compile it locally.
And I see same error message in TC.

/data/teamcity/work/820be461cd64b574/modules/core/src/main/java/org/apache/ignite/internal/processors/rest/handlers/cache/GridCacheCommandHandler.java:[555,58]
incompatible types required: java.util.Set found:
java.util.HashSet

http://ci.ignite.apache.org/viewLog.html?buildId=747237=buildResultsDiv=Ignite20Tests_IgniteCache5

Attached simple patch to fix compile error.

--
Nikolay Izhikov
nizhikov@gmail.com

Re: Plugins in tests

[Pavel Tupitsyn]

Got it, ticket filed: https://issues.apache.org/jira/browse/IGNITE-5879

On Fri, Jul 28, 2017 at 5:58 PM, Yakov Zhdanov  wrote:

> Pavel, I would create a new module just like "modules/extdata/p2p".
>
> --Yakov
>

[jira] [Created] (IGNITE-5879) .NET: Move TestPlatformPlugin to a separate module

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5879:
--

 Summary: .NET: Move TestPlatformPlugin to a separate module
 Key: IGNITE-5879
 URL: https://issues.apache.org/jira/browse/IGNITE-5879
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Move test plugin to a separate module and load it only for .NET tests so we 
don't interfere with other tests.

Dev list discussion: 
http://apache-ignite-developers.2346864.n4.nabble.com/Plugins-in-tests-td20167.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5878:
--

 Summary: Add memory policy name into IgniteOOM exception
 Key: IGNITE-5878
 URL: https://issues.apache.org/jira/browse/IGNITE-5878
 Project: Ignite
  Issue Type: Wish
Reporter: Pavel Konstantinov
Priority: Minor


I got OOM exception but I was not able to understand what policy exactly I need 
to tune
It will be more informative to add memory policy name into exception text
{code}
[14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
 Runtime error caught during grid runnable execution: GridWorker 
[name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
hashCode=392861026, interrupted=false, runner=db-checkpoint-thread-#41%tester%]
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find 
a page for eviction [segmentCapacity=1580, loaded=622, maxDirtyPages=415, 
dirtyPages=622, cpPages=0, pinnedInSegment=0, failedToPrepare=623]
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
at 
org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
at 
org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
[14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
cache: c_partitioned
[14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
Data streamer will not overwrite existing cache entries for better performance 
(to change, set allowOverwrite to true)
[14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
execution (Query): c_partitioned
[14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query execution 
task error
class org.apache.ignite.IgniteException: Runtime failure on bounds: 
[lower=null, upper=null]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:965)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.cursor(IgniteCacheOffheapManagerImpl.java:1515)
at 

[GitHub] ignite pull request #2250: IGNITE-5706: Redis FLUSHDB command support.

[asfgit]

Github user asfgit closed the pull request at:

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


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