[jira] [Created] (IGNITE-6816) Investigate/integrate Webpack dll-plugin

2017-11-01 Thread Ilya Borisov (JIRA)
Ilya Borisov created IGNITE-6816:


 Summary: Investigate/integrate Webpack dll-plugin
 Key: IGNITE-6816
 URL: https://issues.apache.org/jira/browse/IGNITE-6816
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: wizards
Reporter: Ilya Borisov
Assignee: Alexander Kalinin


As the webconsole frontend app size grows, it takes more and more time to 
incrementally rebuild after each source code change in development environment. 
Let's investigate this plugin https://webpack.js.org/plugins/dll-plugin/ and 
integrate it into webpack build pipeline if it offers measureable performance 
improvements.



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


Re: GA Grid: Request to contribute GA library to Apache Ignite

2017-11-01 Thread Dmitriy Setrakyan
Hi Turik,

Is my understanding correct that GA Grid is a vertical component for
genetic algorithms? So far Ignite has been a horizontal product without any
vertical functionality. I personally would like to keep it this way (other
community members should chime in here).

I personally think it is great that GA Grid gets a lot of mention on Apache
Ignite website and has been a valuable integration for the Ignite community.

If you would like to join Apache, have you considered a separate Apache
project? This may help you build a community around your work and benefit
from the established Apache processes during incubation.

D.


On Wed, Nov 1, 2017 at 5:26 PM, techbysample  wrote:

> Igniters,
>
> GA Grid (Beta) is an in memory Genetic Algorithm (GA) for Apache Ignite
> used
> to solve complex problems by simulating biological evolution.
> GA's are a form of Machine Learning (ML), excellent for finding an optimal
> solution, among possibly thousands (or more) candidate solutions for a
> given
> domain.
>
> GA Grid was developed by NetMillennium Inc, Inc outside of Apache Ignite
> platform as a proof of concept to determine feasibility in the GA space.
> In GA Grid, all genetic operations: Fitness Calculation, Crossover, and
> Mutation  are modeled as a ComputeTask for distributive behavior.  Also,
> these ComputeTasks leverage Apache Ignite's Affinity Colocation to route
> ComputeJobs to respective nodes where Chromosomes are stored in cache.
>
> After it's initial release, Denis Magda inquired about the possibility of
> donating GA Grid to Apache Ignite. Per discussions with Denis, he believed
> GA Grid would be well suited as an extension to Apache Ignite's ML library.
> Currently, NetMillennium, Inc. has agreed to begin the process of donating
> GA Grid to Apache Ignite.
>
> With it's latest release, GA Grid enhances knowledge discovery by providing
> custom SQL functions to 'pivot' genetic optimization results. This enables
> improved visualizations inside Apache Zeppelin.
>
> To learn more about GA Grid please visit:
>
> https://github.com/techbysample/gagrid
>
> Check out my recent post on how GA Grid for Ignite integrates with
> Zeppelin:
>
> https://www.linkedin.com/post/edit/apache-ignite-visualize-
> ga-grid-solutions-deep-turik-campbell
>
> Please advise.
>
> Best Regards,
> Turik Campbell
> NetMillennium, Inc.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>


[jira] [Created] (IGNITE-6815) "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy

2017-11-01 Thread Reed Sandberg (JIRA)
Reed Sandberg created IGNITE-6815:
-

 Summary: "Unexpected exception during cache update" via 
NullPointerException thrown using TouchedExpiryPolicy
 Key: IGNITE-6815
 URL: https://issues.apache.org/jira/browse/IGNITE-6815
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: cache, streaming
Affects Versions: 2.3, 2.2
 Environment: 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 
14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: LinuxMint
Description:Linux Mint 18.2 Sonya
Release:18.2
Codename:   sonya


Reporter: Reed Sandberg
Priority: Major


This is triggered when I apply an expiry on the cache during an import with 
StreamLoader, with no expiry on the cache, the import runs fine.

Somehow the following line of code is hit with val == null:
org/apache/ignite/internal/processors/cache/IgniteCacheOffheapManagerImpl.java:1253

Stack trace:

{noformat}
16:04:25.259 ERROR o.a.i.i.p.c.d.d.a.GridDhtAtomicCache -  
Unexpected exception during cache update
org.apache.ignite.IgniteException: Runtime failure on search row: 
org.apache.ignite.internal.processors.cache.tree.SearchRow@68a4e885
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2419)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1882)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1735)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1627)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1116)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:825)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:783)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1338)
at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1320)
at 
org.apache.ignite.stream.StreamTransformer.receive(StreamTransformer.java:45)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:137)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6631)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException: null
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:1253)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.initResultOnCancelUpdate(GridCacheMapEntry.java:4267)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4154)
at 

GA Grid: Request to contribute GA library to Apache Ignite

2017-11-01 Thread techbysample
Igniters,

GA Grid (Beta) is an in memory Genetic Algorithm (GA) for Apache Ignite used
to solve complex problems by simulating biological evolution.
GA's are a form of Machine Learning (ML), excellent for finding an optimal
solution, among possibly thousands (or more) candidate solutions for a given
domain.

GA Grid was developed by NetMillennium Inc, Inc outside of Apache Ignite
platform as a proof of concept to determine feasibility in the GA space.
In GA Grid, all genetic operations: Fitness Calculation, Crossover, and
Mutation  are modeled as a ComputeTask for distributive behavior.  Also,
these ComputeTasks leverage Apache Ignite's Affinity Colocation to route
ComputeJobs to respective nodes where Chromosomes are stored in cache.

After it's initial release, Denis Magda inquired about the possibility of
donating GA Grid to Apache Ignite. Per discussions with Denis, he believed
GA Grid would be well suited as an extension to Apache Ignite's ML library. 
Currently, NetMillennium, Inc. has agreed to begin the process of donating
GA Grid to Apache Ignite. 

With it's latest release, GA Grid enhances knowledge discovery by providing
custom SQL functions to 'pivot' genetic optimization results. This enables
improved visualizations inside Apache Zeppelin.

To learn more about GA Grid please visit:

https://github.com/techbysample/gagrid

Check out my recent post on how GA Grid for Ignite integrates with Zeppelin:

https://www.linkedin.com/post/edit/apache-ignite-visualize-ga-grid-solutions-deep-turik-campbell

Please advise.

Best Regards,
Turik Campbell
NetMillennium, Inc.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/


Re: [DISCUSS] Ignite Update Checker

2017-11-01 Thread Denis Magda
Cos,

I’m not sure the redirect will suit us. Remember the update notifier should do 
2 things:

1. get the most recent version of Ignite stored in the file on the site [1].
2. Trigger GA.

The redirect does 2. but skips 1. Any technical tricks we can apply here?

[1] https://ignite.apache.org/latest

—
Denis

> On Oct 31, 2017, at 1:23 PM, Konstantin Boudnik  wrote:
> 
> Yes, that what I meant. It might not work per website (depends on how
> the server is configured), but server-wide redirects could be
> arranged.
> Also, there's a new discussion on the topic going on legal-discuss@
> right now [1]
> 
> 
> [1] https://is.gd/RPaWQt
> --
>  With regards,
> Konstantin (Cos) Boudnik
> 
> 
> On Tue, Oct 31, 2017 at 1:21 PM, Dmitriy Setrakyan
>  wrote:
>> Cos, thanks for helping out! By redirect, do you mean changing the
>> .htaccess file to point a certain URL containing Ignite version to a GA
>> URL? In that case, do you know if it will be possible to still send the
>> latest Ignite version back as a response?
>> 
>> D.
>> 
>> On Tue, Oct 31, 2017 at 11:30 AM, Konstantin Boudnik  wrote:
>> 
>>> Looks like we are getting somewhere with this. Please check [1] for
>>> the latest comment from the Infra team. I guess we can start with
>>> asking for a server-side redirect to GA as the immediate step. And
>>> explore it further possibilities as per Greg's recommendations.
>>> 
>>> 
>>> [1] https://is.gd/CL88O6
>>> --
>>>  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 Wed, Oct 25, 2017 at 8:21 AM, Denis Magda  wrote:
 Hi Cos,
 
 Sure, will see you around there.
 
 Anyway, a short summary is the following.
 
 Starting Ignite 2.3 the nodes will be connecting to a *static* file [1]
>>> deployed on Ignite site to obtain the most recent version. If the file has
>>> a later version than the nodes will print out a message encouraging a user
>>> to do an upgrade.
 
 On top of that, some community members proposed to trigger GA once the
>>> file [1] is loaded. But to achieve this the file has to become dynamic
>>> being able to execute simple CGI scripts. The INFRA turned this request
>>> down.
 
 [1] https://ignite.apache.org/latest
 [2] https://issues.apache.org/jira/browse/INFRA-15182
 
 —
 Denis
 
> On Oct 24, 2017, at 11:57 PM, Konstantin Boudnik 
>>> wrote:
> 
> Guys,
> 
> I had a quick chat with Nikita earlier today and it seems that we have
>>> came across of a blocker of some kind. With my member's hat on I would love
>>> to help to find a resolution that let us (and potentially other
>>> communities) to move forward.
> 
> Let's craft the message and circulate it with Infra and Greg. Denis,
>>> could you find me tomorrow at the IMCS and give me an insight into the
>>> technical side of it? I feel a bit at loss after going through this
>>> thread...
> --
> Regards,
> Cos
> 
> On October 2, 2017 7:31:48 AM PDT, Denis Magda 
>>> wrote:
>> Dmitriy,
>> 
>> That’s the rule.  See replies in the ticket [1]
>> 
>> *Background: the TLP server is already pretty darned busy just serving
>> *static* sites. Dynamic operation for near-200 PMCs would bury the
>> machine. Our policy of "static-only websites" has been in place since
>> the Foundation started*
>> 
>> Download scripts seem to be the only exception and we as PMC don’t even
>> have access to them.
>> 
>> If you want to keep pushing this direction let’s craft a message to
>> Greg and Daniel directly. I don’t know what else to ask for here rather
>> than a virtual machine that’s conceivably to much for a single script
>> like that.
>> 
>> [1] https://issues.apache.org/jira/browse/INFRA-15182
>> 
>> 
>> —
>> Denis
>> 
>>> On Oct 2, 2017, at 2:48 AM, Dmitriy Setrakyan 
>> wrote:
>>> 
>>> On Mon, Oct 2, 2017 at 12:46 PM, Vladimir Ozerov
>> 
>>> wrote:
>>> 
 I am not sure it is good idea to send requests to 3rd-party
>> addresses from
 Ignite node. Let's do not make the same mistakes again.
 
>>> 
>>> Agree with Vladimir.
>>> 
>>> We obviously have CGI support on the website. Can someone explain why
>> CGI
>>> is not possible to use?
>>> 
>>> 
 
 On Mon, Oct 2, 2017 at 12:42 PM, Andrey Novikov
>> 
 wrote:
 
> We may directly send request to GA from 

[GitHub] ignite pull request #2970: IGNITE-6745: Java 9: rework usages of URLClassLoa...

2017-11-01 Thread elcergey
GitHub user elcergey opened a pull request:

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

IGNITE-6745: Java 9: rework usages of URLClassLoader.getURLs()

Regarding the https://issues.apache.org/jira/browse/IGNITE-6745

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

$ git pull https://github.com/elcergey/ignite master

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

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


commit 31aae683b37c4feeddaba3100e46526e3d1f019d
Author: cossa...@mail.ru 
Date:   2017-11-01T23:51:04Z

IGNITE-6745: Java 9: rework usages of URLClassLoader.getURLs()




---


Re: Let's keep Apache Ignite docs up-to-date

2017-11-01 Thread Dmitriy Setrakyan
I am going to repeat my previous comment, since it somehow got lost in the
discussion:

The main value of readme is that I can edit a document and it is visible to
the whole world once I click a save button, without any git commands or
builds. If anyone in the community can suggest a tool that will work the
same way with Apache git repository directly, please send it here.

D.

On Wed, Nov 1, 2017 at 4:26 AM, Anton Vinogradov 
wrote:

> +1 to Pavel's proposal,
>
> > Markdown can also be visualized by many IDEs, so it is easy to edit
> locally.
> IDEA shows Markdown out of the box.
>
> Yakov,
>
> > having docs under separate git repository
> We should not use separate git repo, Apache Ignite repo should be used.
> Documentation should be a part of pull request.
>
> On Wed, Nov 1, 2017 at 10:08 AM, Pavel Tupitsyn 
> wrote:
>
> > Denis,
> >
> > > Could you show me any example of such a documentation where docs are
> > stored in git and can be visualized by GitHub (dev stage) and 3rd party
> > engine (release on the site)?
> >
> > 1) Apache Spark
> > Source: https://github.com/apache/spark/tree/master/docs
> > Docs: https://spark.apache.org/documentation.html
> > (uses Jekyll)
> >
> > 2) Microsoft .NET
> > Source: https://github.com/dotnet/docs
> > Docs: https://docs.microsoft.com/en-us/dotnet/
> > (uses DocFX)
> >
> >
> > Both of these engines (Jekyll and DocFX) use markdown, which can be
> > visualized by github, and converted to HTML for the web site.
> > Markdown can also be visualized by many IDEs, so it is easy to edit
> > locally.
> >
> > Ideally, API docs (javadoc) should be integrated with the rest of the
> docs,
> > so users can navigate to the corresponding APIs.
> > This can't be achieved nicely with readme.io.
> >
> >
> > > having docs under separate git repository
> > I don't think we need a separate repo, we can just create branches in our
> > main repo for that.
> > It is nice to have everything in one place.
> >
> > On Wed, Nov 1, 2017 at 6:30 AM, Dmitriy Setrakyan  >
> > wrote:
> >
> > > On Tue, Oct 31, 2017 at 8:15 PM, Yakov Zhdanov 
> > > wrote:
> > >
> > > > I would also consider having docs under separate git repository.
> > Separate
> > > > since we need to have an opportunity to revisit documentation for
> > already
> > > > released versions.
> > > >
> > >
> > > This should not be a problem.
> > >
> >
>


[DISUCSS] Ticket filing process

2017-11-01 Thread Dmitriy Setrakyan
Igniters,

Currently, most new Jira tickets do not get reviewed and often get lost
unless some user complains about it.

In my view, the community must review all recently filed ticket and make
sure that we address most critical or most useful ones. Often an issue is
not critical from correctness standpoint, but is very useful from usability
stand point.

What if we always assigned the next release version to all the newly filed
tickets. This will force someone to look at the tickets before every
release and move some of them to the next release.

Thoughts?

D.


[GitHub] ignite pull request #2969: IGNITE-5246: Fuzzy c-means (FCM)

2017-11-01 Thread ilya-nozhkin
GitHub user ilya-nozhkin opened a pull request:

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

IGNITE-5246: Fuzzy c-means (FCM)

Implemented local and distributed versions of FCM algorithm

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

$ git pull https://github.com/ilya-nozhkin/ignite ignite-5246

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

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


commit 177427ff6a5024af3a61fb34584847370b46afae
Author: Ilya Nozhkin 
Date:   2017-10-03T20:38:38Z

started to work on fuzzy c-means clustering, partially implemented base 
abstract entities

commit 9f005b897fc797a27abfa19e19ac2ce01370a3b3
Author: Ilya Nozhkin 
Date:   2017-10-17T21:04:41Z

implemented the local version of FCM

commit 2481e6fb85203af6b49c398ae538683ea467a5e3
Author: Ilya Nozhkin 
Date:   2017-10-21T14:08:24Z

finished to implement FCM local clusterer, wrote some tests

commit 144e9284fb2a3fcfad54ef6a8ae6c4fcedfef33f
Author: Ilya Nozhkin 
Date:   2017-10-27T17:04:32Z

partially implemented centers selection

commit 126019354e88db249c13897205ea57a61001fff6
Author: Ilya Nozhkin 
Date:   2017-10-27T17:11:08Z

Merge branch 'master' into ignite-5247

commit fa2efcae5806feb6264f51255b59973a1998676b
Author: Ilya Nozhkin 
Date:   2017-10-27T17:43:46Z

implemented centers selection

commit fdc9ac3987c46d5c6db155f3b17aa30d9eeed12c
Author: Ilya Nozhkin 
Date:   2017-10-27T21:56:17Z

implemented distributed version of FCM and some test for it too

commit d0f200f987af87d6e34305bc8554305becd58e39
Author: Ilya Nozhkin 
Date:   2017-10-31T21:06:03Z

wrote comments for distributed version

commit 8582832143cecb49e49f404b4cd39ddd52b60151
Author: Ilya Nozhkin 
Date:   2017-10-31T21:47:32Z

commented local clusterer, changed the location of some methods, added stop 
condition for distributed clusterer, added exceptions throwing

commit 6f7114a3355c6468bd5112fb8b82c9fb0b8ef1ff
Author: Ilya Nozhkin 
Date:   2017-10-31T22:26:22Z

implemented new test for local clusterer, fixed bug with argument checking

commit 12eb052d9420f54eeb0b9f04b057beedabd97b33
Author: Ilya Nozhkin 
Date:   2017-11-01T22:57:15Z

updated and commented tests, changed access levels of methods in 
distributed clusterer




---


[jira] [Created] (IGNITE-6814) Detailed memory consumption on start and OOM reporting

2017-11-01 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-6814:
---

 Summary: Detailed memory consumption on start and OOM reporting
 Key: IGNITE-6814
 URL: https://issues.apache.org/jira/browse/IGNITE-6814
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.0
Reporter: Denis Magda
Priority: Critical
 Fix For: 2.4


Presently Ignite allocates 20% of RAM on a node startup, however, the user 
doesn't see automatically chosen memory settings. Also, if there a node runs 
out of RAM and throws an OOM error there are no hints on why this happened and 
how to fix it.

Suggestions: 
* Print out memory settings on startup for every data region set up (maximum 
size, initial size, etc.)
* Provide guidelines on how to overcome OOM when it happens. Specify a data 
region name with all its current parameters and suggest three possible things - 
tweak maximum memory, setup eviction policies or enable Ignite persistence. All 
this is covered in official docs: 
https://apacheignite.readme.io/docs#section-data-regions



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


[jira] [Created] (IGNITE-6813) Update diagrams on readme.io documentation

2017-11-01 Thread Denis Magda (JIRA)
Denis Magda created IGNITE-6813:
---

 Summary: Update diagrams on readme.io documentation
 Key: IGNITE-6813
 URL: https://issues.apache.org/jira/browse/IGNITE-6813
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: documentation
Reporter: Denis Magda
Assignee: Prachi Garg
Priority: Minor
 Fix For: 2.4


The last page on Apache Ignite site were updated with new version of diagrams:
https://ignite.apache.org/ features/deploy.html
https://ignite.apache.org/ features/igfs.html
https://ignite.apache.org/ features/mapreduce.html
https://ignite.apache.org/ features/streaming.html

https://ignite.apache.org/use- cases/caching/database- caching.html
https://ignite.apache.org/use- cases/caching/hibernate-l2- cache.html
https://ignite.apache.org/use- cases/caching/web-session- clustering.html
https://ignite.apache.org/use- cases/hadoop/hdfs-cache
https://ignite.apache.org/use- cases/hadoop/mapreduce

Please go through all the readme.io pages replacing the old diagrams with new 
ones. Make this for every "overview" page of every documentation section we 
have.



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


[ANNOUNCE] Apache Ignite 2.3.0 Released

2017-11-01 Thread Denis Magda
The Apache Ignite Community is pleased to announce the release of Apache Ignite 
2.3.0.

Apache Ignite [1] is the in-memory computing platform that is durable, strongly 
consistent and highly available 
with powerful SQL, key-value and processing APIs.

This release adds more SQL capabilities and Ignite persistence improvements to 
the projects. The major changes are covered
in our regular blog post: 
https://blogs.apache.org/ignite/entry/apache-ignite-2-3-more

As a short summary of the article:
- now we support ALTER TABLE command for columns addition.
- include SQLLine tool in every Ignite release.
- released new SQL documentation [2].
- prepared a screencast for you that shows how to interact with Ignite as with 
an SQL database [3].
  
The full list of the changes can be found here [4].

Here is where you can grab the latest Ignite version:
https://ignite.apache.org/download.cgi

Please let us know [5] if you encounter any problems.

Regards,
The Apache Ignite Community

[1] https://ignite.apache.org
[2] https://apacheignite-sql.readme.io/docs
[3] https://www.youtube.com/watch?v=FKS8A86h-VY=youtu.be
[4] https://ignite.apache.org/releases/2.3.0/release_notes.html
[5] https://ignite.apache.org/community/resources.html#ask



[GitHub] ignite pull request #2968: IGNITE-6640: Introduction of models import/export

2017-11-01 Thread ybabak
GitHub user ybabak opened a pull request:

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

IGNITE-6640: Introduction of models import/export

added missed licence.

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

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

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

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


commit dfb9a657c7c07070a2620cdfc08af6970e6b7ea3
Author: Yury Babak 
Date:   2017-10-25T16:28:43Z

IGNITE-6640: Introduction of models import/export.
 added test for cluster model

commit 090e0ed9c5a14f0e8366941ebff6e1afe0aefa7b
Author: Yury Babak 
Date:   2017-10-30T22:46:21Z

IGNITE-6640: Introduction of models import/export.
Initial kmeans test passed.

commit 548ae4da1d65f1a70484fb228bc69f10d60d2340
Author: Yury Babak 
Date:   2017-10-31T15:45:15Z

IGNITE-6640: Introduction of models import/export.
 refactored model import/export functionality.

commit 883f99bed1ac76fe01a0ecb46d14e18d846cabff
Author: Yury Babak 
Date:   2017-10-31T15:48:55Z

Merge branch 'apacheMaster' into ignite-6640

# Conflicts:
#   
modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/matrix/BlockMatrixStorage.java

commit 349d696a59e616773277e9ec738e3f37a3580eed
Author: Yury Babak 
Date:   2017-11-01T09:09:42Z

IGNITE-6640: Introduction of models import/export.
review fixes

commit 312c4805bececf0949ce79a0819c85d58d62da05
Author: Yury Babak 
Date:   2017-11-01T20:51:41Z

IGNITE-6640: Introduction of models import/export.
added missed licence.

commit 049ad865108129ec9f8f55b053f43c3372d90230
Author: Yury Babak 
Date:   2017-11-01T20:54:49Z

Merge branch 'master' into ignite-6640

# Conflicts:
#   modules/ml/src/main/java/org/apache/ignite/ml/Exportable.java
#   
modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/matrix/BlockMatrixStorage.java




---


[GitHub] ignite pull request #2967: IGNITE-6812: Readme.md: Update link to TC build a...

2017-11-01 Thread dspavlov
GitHub user dspavlov opened a pull request:

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

IGNITE-6812: Readme.md: Update link to TC build and remove glitter



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

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

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

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


commit 91448a9ee7a22fb9ced7104f09952ff989c9cf24
Author: dpavlov 
Date:   2017-11-01T18:15:55Z

IGNITE-6812: Readme.md: Update link to TC build and remove glitter

commit 748e6c4f139c91bacb6079e6cf4a2330a6169bf8
Author: dpavlov 
Date:   2017-11-01T18:19:19Z

IGNITE-6812: Readme.md: Update link to TC build and remove glitter




---


[jira] [Created] (IGNITE-6812) Readme.md: Update link to TC build and remove glitter

2017-11-01 Thread Dmitriy Pavlov (JIRA)
Dmitriy Pavlov created IGNITE-6812:
--

 Summary: Readme.md: Update link to TC build and remove glitter
 Key: IGNITE-6812
 URL: https://issues.apache.org/jira/browse/IGNITE-6812
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Priority: Minor






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


[GitHub] ignite pull request #2966: IGNITE-1025

2017-11-01 Thread 1vanan
GitHub user 1vanan opened a pull request:

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

IGNITE-1025



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

$ git pull https://github.com/1vanan/ignite ignite-1025

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

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


commit 5a44af1199a654f4737438193a5c8d061a6ef5e4
Author: ivanan 
Date:   2017-10-05T07:10:44Z

wrong ip addresses worning was added in TCPDiscoveryVmIpFinder

commit de407e2a16f22536186f7b3e4de8adbb03308a04
Author: ivanan 
Date:   2017-10-05T21:41:10Z

change some var names

commit 99b6ca29bfc953904148004518cdc7baf14c844e
Author: ivanan 
Date:   2017-10-09T21:36:48Z

remarks were taken into account

commit a55dcc1c329459a612aaf60e2877367c867caa66
Author: ivanan 
Date:   2017-10-10T21:42:39Z

fix changes 11.10.17

commit adaf649409db53cc025de7bd8d484886847f784a
Author: ivanan 
Date:   2017-10-18T22:56:49Z

added TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit 17465c952f96e11584147a6828d082c867f7838b
Author: Ivan 
Date:   2017-10-24T14:32:43Z

isUnresolved instead of TcpTimeout

commit d7be15ecc8fbce57996e234573129d00912e66a2
Author: Ivan 
Date:   2017-10-24T14:38:29Z

test with single and multiports

commit 458377e35bb9f10b5a02f77645e61f98f5e749dd
Author: Ivan 
Date:   2017-10-27T14:01:54Z

27.10.17

commit 020ca8ca9f07636bc3288f6018a3d1a94c025839
Author: Ivan 
Date:   2017-10-31T13:52:46Z

isLoggingOfWrongAddressFirst method was added, minor changes in 
TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit 8f3faed2db05fbc75a958ca99c8d2befe688718c
Author: Ivan 
Date:   2017-10-31T15:58:54Z

fix some comments in TcpDiscoveryVmIpFinderSetAddressesWarningTest

commit b8f3effa0bff5fd6e696d5c22abb64cea17f76a3
Author: Ivan 
Date:   2017-11-01T12:06:49Z

delete obvious comment

commit cb4519dc37ec0b96b6bcde7e6a3ceba875fde374
Author: Ivan 
Date:   2017-11-01T13:50:18Z

fix style remarks

commit fb6a02fcd58619ffedbd67cc3ec609db9f34d447
Author: Ivan 
Date:   2017-11-01T14:56:26Z

rename logIfInvalidAddressAppearedFirst to logFirstInvalidAddress




---


[GitHub] ignite pull request #2965: IGNITE-6805: Tests are red for another MAX_BLOCK_...

2017-11-01 Thread zaleslaw
GitHub user zaleslaw opened a pull request:

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

IGNITE-6805: Tests are red for another MAX_BLOCK_SIZE value (4 or 8 instead 
32)

Added two test cases and fix in BlockMatrixStorage

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

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

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

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


commit 919c3f23622785afefe59e1d7642838e27163c86
Author: zaleslaw 
Date:   2017-11-01T15:23:08Z

Fixed bugs in BlockMatrixStorage

commit ddf4548daa4729bc6b0ce010bdf5d60c16393663
Author: zaleslaw 
Date:   2017-11-01T15:40:13Z

IGNITE-6805: Added missed JavaDocs




---


[GitHub] ignite pull request #2945: IGNITE-6788: Ignite WAL reader fails on Tx marker

2017-11-01 Thread dspavlov
Github user dspavlov closed the pull request at:

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


---


[GitHub] ignite pull request #2953: IGNITE-6640: Introduction of models import/export

2017-11-01 Thread ybabak
Github user ybabak closed the pull request at:

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


---


[GitHub] ignite pull request #2964: ignite-pitr-rc1

2017-11-01 Thread DmitriyGovorukhin
GitHub user DmitriyGovorukhin opened a pull request:

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

ignite-pitr-rc1



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

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

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

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


commit bb66f21dfbaeec42bd107968b873d7c2d9d47e24
Author: Dmitriy Govorukhin 
Date:   2017-11-01T13:15:18Z

merge ignite-blt-2 -> ignite-pitr-rc1

commit d9ef94f5108071deef0404ea56c1dfcdd8f40c12
Author: Dmitriy Govorukhin 
Date:   2017-11-01T13:43:07Z

merge ignite-pitr-beta -> ignite-pitr-rc1




---


[GitHub] ignite pull request #2963: Ignite-1.6-master

2017-11-01 Thread AMashenkov
GitHub user AMashenkov opened a pull request:

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

Ignite-1.6-master



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

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

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

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


commit d399db92ab4e147a3933a42dd5635b225665ac63
Author: Alexey Kuznetsov 
Date:   2016-08-22T08:00:06Z

 IGNITE-3708 Fixed multithreaded loading entries for MySql.

commit 5b57fc04866677fbf1221a253fe28905dbfc2d7d
Author: vozerov-gridgain 
Date:   2016-08-22T14:16:45Z

IGNITE-3694: IGFS: Remove invalid assertion in IgfsImpl.newBatch() method.

commit fa13832132ad71cd3b3ad259784e2e7ec5366c28
Author: tledkov-gridgain 
Date:   2016-08-22T14:37:14Z

IGNITE-3693: IGFS: Fixed sporadical failures in 
IgfsLocalSecondaryFileSystemDualAsyncSelfTest.testFormat. This closes #960.

commit a0c7c44fc864aa965fd4d14e5362a4f6356c01ab
Author: AndreVel 
Date:   2016-08-23T03:50:57Z

IGNITE-3197 - OverlappingFileLockException in marshaller context

commit eea42827738301168d66562a05d3360150e6fb89
Author: sboikov 
Date:   2016-08-23T07:47:15Z

Fix for IgniteDynamicCacheStartNoExchangeTimeoutTest.

commit f9258736c5cfa157e138d879aa0dbacc5a7cb4b2
Author: Alexey Kuznetsov 
Date:   2016-08-23T07:59:45Z

Fixed tests.

commit d6033712425cd0157fa640a7d46ec6579fd7e74b
Author: Pavel Tupitsyn 
Date:   2016-08-23T11:10:55Z

IGNITE-3325 .NET: Improve CompiledQuery in LINQ provider

commit 207e8cb3b939670655da14082ac9e1cf1d822fd0
Author: Pavel Tupitsyn 
Date:   2016-08-23T17:01:48Z

IGNITE-3325 .NET: Improve CompiledQuery in LINQ provider - minor fixes

commit 417b269fe844c2a0b2c18aff8f58a2b38bc27531
Author: Vasiliy Sisko 
Date:   2016-08-24T02:44:04Z

IGNITE-3005 Implemented showing of node ID8 , IP and checked values on 
alert.

commit 8c370c6927848b66782ecc18df499460c0bfdd11
Author: Vasiliy Sisko 
Date:   2016-08-24T03:03:33Z

IGNITE-2726 Added per-nodes cache information about off-heap.

commit 25b59d7c6ea7bd23d5a8366fb5618e11990327c8
Author: Pavel Tupitsyn 
Date:   2016-08-24T08:07:17Z

IGNITE-3325 .NET: Rename CompiledQueryDelegate -> CompiledQueryFunc to 
conform to design guidelines

commit 4e9e7b8ee1c990bacdc2d081b706ca315927fdce
Author: vozerov-gridgain 
Date:   2016-08-24T09:12:00Z

IGNITE-3716: ODBC: Added SQL escape sequence parsing.

commit 118db2fcffe3534aa1e5f4b97b8fbe23891752c4
Author: vozerov-gridgain 
Date:   2016-08-24T09:12:24Z

Merge remote-tracking branch 'upstream/ignite-1.6.6' into ignite-1.6.6

commit c02ad87f863bd730e60fb7052547fa0848e7eb77
Author: isapego 
Date:   2016-08-24T14:21:48Z

IGNITE-3736: ODBC: Added support for string scalar functions. This closes 
#979.

commit 13dfcbe03aca137ee70698f6083df27c10ecdaf9
Author: vozerov-gridgain 
Date:   2016-08-24T14:31:38Z

IGNITE-3736: ODBC: Reverted back removed "supported" futures.

commit d6449ffbc65acda6a2cf4484608188367837dd17
Author: sboikov 
Date:   2016-08-24T15:34:02Z

Fixed issues on node stop:
- in service processor need guard depExe access with busyLock
- do not error log IO errors in ClientImpl on stop

commit 12fd4976f482ebc43831754645e34042c9073b2d
Author: sboikov 
Date:   2016-08-25T09:29:04Z

Fixed GridQueryParsingTest.

commit 5a3b3e2c6ecb5d6c96513b79f21828526b4a98a0
Author: isapego 
Date:   2016-08-25T09:35:07Z

IGNITE-3749: ODBC: Added support for numeric scalar functions. This closes 
#981.

commit 0e3a6e2df8b42f255a5a4688d5827dccaabfd3a4
Author: isapego 
Date:   2016-08-25T11:34:31Z

IGNITE-3757: ODBC: Added aggregate functions support. This closes #983.

commit e2f287039011bc9437c94fb574e61e2ac226
Author: Andrey V. Mashenkov 
Date:   2016-08-25T13:26:02Z

IGNITE-3738: ODBC: Fixed escape sequence whitespaces handling. This closes 
#982.

commit 8aabd6ea65d883d3bbcf37c05c146105dff8a6e2
Author: isapego 
Date:   2016-08-25T13:30:20Z

IGNITE-3751: ODBC: Added system functions support. This closes #985.

commit ae0b5ebf02f3eb70d24dd3b0eb63dde9843c82b0
Author: Andrey V. Mashenkov 
Date:   2016-08-26T08:12:31Z

IGNITE-3739: ODBC: Added GUID escape sequence support. This closes #988.

commit 6fd53ea5b50148e5a1156d83ea28acb8faf84035

[GitHub] ignite pull request #2958: ignite-pitr-rc1

2017-11-01 Thread DmitriyGovorukhin
Github user DmitriyGovorukhin closed the pull request at:

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


---


[GitHub] ignite pull request #2962: IGNITE-6679

2017-11-01 Thread NSAmelchev
GitHub user NSAmelchev opened a pull request:

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

IGNITE-6679

Clean up some deprecated cache metrics:

- TxCommitQueueSize
- TxPrepareQueueSize
- TxStartVersionCountsSize
- TxDhtCommitQueueSize
- TxDhtPrepareQueueSize
- TxDhtStartVersionCountsSize
- DhtEvictQueueCurrentSize 

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

$ git pull https://github.com/NSAmelchev/ignite ignite-6679

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

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


commit 60fc4eaed7491a757f006ca26c88e234159a9000
Author: NSAmelchev 
Date:   2017-11-01T12:47:47Z

remove unnecessary metrics

commit 5c125200555098f0de06bee94b72301646445a46
Author: NSAmelchev 
Date:   2017-11-01T12:49:16Z

clean up




---


[jira] [Created] (IGNITE-6811) JDBC Thin: SQLException("Batch is empty.") when batch list is empty

2017-11-01 Thread Vasily Bukharev (JIRA)
Vasily Bukharev created IGNITE-6811:
---

 Summary: JDBC Thin: SQLException("Batch is empty.") when batch 
list is empty
 Key: IGNITE-6811
 URL: https://issues.apache.org/jira/browse/IGNITE-6811
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: jdbc
Affects Versions: 2.3
Reporter: Vasily Bukharev


The method executeBatch() throws SQLException("Batch is empty.") when batch 
list is empty.
The api doc of java.sql.Statement.executeBatch() 
does not require an exception to be thrown in such situation.
I guess it is more convinient for client code if the exception is not thrown.



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


[jira] [Created] (IGNITE-6810) ODBC: Add secure connection support

2017-11-01 Thread Igor Sapego (JIRA)
Igor Sapego created IGNITE-6810:
---

 Summary: ODBC: Add secure connection support
 Key: IGNITE-6810
 URL: https://issues.apache.org/jira/browse/IGNITE-6810
 Project: Ignite
  Issue Type: New Feature
  Security Level: Public (Viewable by anyone)
  Components: odbc
Affects Versions: 2.3
Reporter: Igor Sapego
Assignee: Igor Sapego
Priority: Major
 Fix For: 2.4


Need to add for ODBC support of SSL/TLS.



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


Re: Context switching for pessimistic transactions

2017-11-01 Thread ALEKSEY KUZNETSOV
Hi, Igntrs!

I’m working on a ticket "Context switching for pessimistic transactions"
[1].

Goal of the ticket is to support transaction suspend()\resume() operations
for pessimistic transactions. Resume can be called in another thread.



Imagine, we started a pessimistic transaction in thread T1 and then perform
put operation, which leads to sending GridDistributedLockRequest to another
node. Lock request contains thread id of the transaction. Then we call
suspend and resume in another thread and we also must send messages to
other nodes to change thread id.



It seems complicated task.It’s better to get rid of sending thread id to
the nodes.



So, there are 2 possible options :

   1.

   Remove threadId field from all requests\responses , but it would break
   compatibility
   2.

   Don’t remove the field, just put -1 (undefined) in it. But it will
   affect transaction logic on nodes.



I prefer 1 option.

Thoughts ?


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


пн, 23 окт. 2017 г. в 15:35, ALEKSEY KUZNETSOV :

> Hi, Igntrs!
>
> I would like to implement suspend\resume methods of a pessimistic
> transaction as following:
>
> if transaction holds lock on a key and suspend method has been called no
> keys would be unlocked. Therefore,
>
> if transaction holds lock on a key and suspend method has been called,
> topology changing (e.g. start new node in the same thread) would wait
> transaction to be resumed and finished.
>
> Do you think it’s an appropriate behavior?
>
>
> пт, 13 окт. 2017 г. в 5:06, Dmitriy Setrakyan :
>
>> On Wed, Oct 11, 2017 at 9:00 AM, ALEKSEY KUZNETSOV <
>> alkuznetsov...@gmail.com
>> > wrote:
>>
>> > Hi, Igntrs!
>> >
>> > For suspend\resume operations in pessimistic mode we want to write the
>> same
>> > tests as for optimistic mode.
>> >
>> > What additional tests should we create for the task?
>>
>>
>> Alexey, I think you should ask the reviewer in the ticket to pay attention
>> to the tests and perhaps suggest some new ones. Without an actual review
>> it
>> would be impossible to tell which tests need to be added.
>>
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*


Re: Let's keep Apache Ignite docs up-to-date

2017-11-01 Thread Anton Vinogradov
+1 to Pavel's proposal,

> Markdown can also be visualized by many IDEs, so it is easy to edit
locally.
IDEA shows Markdown out of the box.

Yakov,

> having docs under separate git repository
We should not use separate git repo, Apache Ignite repo should be used.
Documentation should be a part of pull request.

On Wed, Nov 1, 2017 at 10:08 AM, Pavel Tupitsyn 
wrote:

> Denis,
>
> > Could you show me any example of such a documentation where docs are
> stored in git and can be visualized by GitHub (dev stage) and 3rd party
> engine (release on the site)?
>
> 1) Apache Spark
> Source: https://github.com/apache/spark/tree/master/docs
> Docs: https://spark.apache.org/documentation.html
> (uses Jekyll)
>
> 2) Microsoft .NET
> Source: https://github.com/dotnet/docs
> Docs: https://docs.microsoft.com/en-us/dotnet/
> (uses DocFX)
>
>
> Both of these engines (Jekyll and DocFX) use markdown, which can be
> visualized by github, and converted to HTML for the web site.
> Markdown can also be visualized by many IDEs, so it is easy to edit
> locally.
>
> Ideally, API docs (javadoc) should be integrated with the rest of the docs,
> so users can navigate to the corresponding APIs.
> This can't be achieved nicely with readme.io.
>
>
> > having docs under separate git repository
> I don't think we need a separate repo, we can just create branches in our
> main repo for that.
> It is nice to have everything in one place.
>
> On Wed, Nov 1, 2017 at 6:30 AM, Dmitriy Setrakyan 
> wrote:
>
> > On Tue, Oct 31, 2017 at 8:15 PM, Yakov Zhdanov 
> > wrote:
> >
> > > I would also consider having docs under separate git repository.
> Separate
> > > since we need to have an opportunity to revisit documentation for
> already
> > > released versions.
> > >
> >
> > This should not be a problem.
> >
>


[GitHub] ignite pull request #2959: Flaky testFairReentrantLockConstantMultipleTopolo...

2017-11-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[GitHub] ignite pull request #2961: IGNITE-6324 Transactional cache data partially av...

2017-11-01 Thread DmitriyGovorukhin
GitHub user DmitriyGovorukhin opened a pull request:

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

IGNITE-6324 Transactional cache data partially available after crash.



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

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

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

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


commit e751a8c70cc49c138aed004f1b216b9b02b3b6e1
Author: Dmitriy Govorukhin 
Date:   2017-10-26T13:37:44Z

IGNITE-6324 add transaction recovery functionality + tests

commit 1d804fe47626d36afc6b70613180ded637451248
Author: Dmitriy Govorukhin 
Date:   2017-10-26T14:13:46Z

IGNITE-6324 small test rework

commit bb6d41d683caeb3a393798c671d194199fdf3625
Author: Dmitriy Govorukhin 
Date:   2017-11-01T10:41:13Z

IGNITE-6324 minor improvements, more debug on recovery, move wal log 
dataRec in txs




---


[GitHub] ignite pull request #2960: IGNITE-6809

2017-11-01 Thread gvvinblade
GitHub user gvvinblade opened a pull request:

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

IGNITE-6809



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

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

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

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


commit ee82cfec091d2cc5f92c5a894911a2fbea5d9f6e
Author: Igor Seliverstov 
Date:   2017-11-01T10:44:02Z

IGNITE-6809 Use MPSC queue in striped pool




---


[GitHub] ignite pull request #2959: Flaky testFairReentrantLockConstantMultipleTopolo...

2017-11-01 Thread zstan
GitHub user zstan opened a pull request:

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

Flaky testFairReentrantLockConstantMultipleTopologyChangeNonFailoverS…

…afe fail

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

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

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

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


commit fe6aac1faba32085e3eabb78548d7c026eefd975
Author: Evgeny Stanilovskiy 
Date:   2017-11-01T10:39:12Z

Flaky testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe 
fail




---


[GitHub] ignite pull request #2958: ignite-pitr-rc1

2017-11-01 Thread DmitriyGovorukhin
GitHub user DmitriyGovorukhin opened a pull request:

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

ignite-pitr-rc1



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

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

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

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


commit a7ecc8ff1866df3bca0dcd504f0258a99dcbe430
Author: Dmitriy Govorukhin 
Date:   2017-11-01T09:14:15Z

merge ignite-pitr-beta -> ignite-pitr-rc1




---


IGNITE-5798 is ready for review

2017-11-01 Thread Иван Федотов
Hi,

PR for ticket IGNITE-5798 <*https://issues.apache.org/jira/browse/IGNITE-5798
*> "Logging Ignite
configuration at startup" is ready for review.
Please find all information about this ticket in Jira.

-- 
Ivan Fedotov.

ivanan...@gmail.com


[GitHub] ignite pull request #2957: IGNITE-5798

2017-11-01 Thread 1vanan
GitHub user 1vanan opened a pull request:

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

IGNITE-5798

Logging of IgniteConfiguration was added at startup.

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

$ git pull https://github.com/1vanan/ignite IGNITE-5798

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

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


commit 9a7db6bff146eac658324661de5126969c73fcb7
Author: ivanan 
Date:   2017-09-14T21:05:48Z

Log IgniteConfiguration with reflection

commit 5826ec18bdfe3edca0d580b9d33198c42d14e32b
Author: ivanan 
Date:   2017-09-17T13:12:27Z

took into account the corrections

commit ce2d522ab8d451db23f691e1ebee425409740877
Author: ivanan 
Date:   2017-09-21T21:44:24Z

fix ackIgniteConfigurationInfo method in IgniteKernal

commit 78f9b5f0a95c0b221a6f4e3e29feed4e94d33b97
Author: ivanan 
Date:   2017-10-01T20:55:32Z

use recursive ackIgniteConfiguration

commit 868ecb3598f11856050da5f40fb3c7eb8f45d438
Author: ivanan 
Date:   2017-10-01T21:03:26Z

Revert "fix ackIgniteConfigurationInfo method in IgniteKernal"

This reverts commit ce2d522ab8d451db23f691e1ebee425409740877.

commit 3f6e10bc83a199436e1cb7e1ad7709f29956e71c
Author: ivanan 
Date:   2017-10-01T21:30:57Z

add recursive ackIgniteConfiguration

commit e4e0b2047ade273ad0f572a04fb094cd05880e3a
Author: ivanan 
Date:   2017-10-04T22:29:31Z

remove recursion

commit fab172ef257758828b736b151648d6e76697bd6e
Author: ivanan 
Date:   2017-10-06T07:13:18Z

06.10.17 fix changes

commit edff9457587ea42723677c88403e6bb83b42bfa9
Author: ivanan 
Date:   2017-10-12T06:14:15Z

remove deadlock case

commit 7fc4b8e3653dc125e6cb41b00ac370fa9bb914bf
Author: ivanan 
Date:   2017-10-12T06:26:44Z

return java.util imports instead of java.util.*

commit 2a5f7dc7ebf60899c094dabd4dd149fdc88230e6
Author: ivanan 
Date:   2017-10-13T05:27:24Z

minor code style changes

commit 3db6647d31d680467792eaaf06afe735a18ed4fa
Author: ivanan 
Date:   2017-10-17T21:34:31Z

remove Pair, fix changes

commit bfa66b0519173f5e8e1e13d108b5a19eb313ddd4
Author: Ivan 
Date:   2017-10-27T13:18:34Z

27.10.17

commit 6dd08c99edf85bed263626186ece8392eadd74f0
Author: Ivan 
Date:   2017-10-27T13:49:39Z

minor changes

commit d72e3637e214456694ebe67ce5af70d9edb35304
Author: Ivan 
Date:   2017-10-31T09:05:57Z

delete garbage methods.

commit 7d79be46e38c5488b294524786c266b43ffe1941
Author: Ivan 
Date:   2017-11-01T08:56:11Z

delete unused import

commit 6755a26a19c035686ed1e939a1c966489342e407
Author: Ivan 
Date:   2017-11-01T09:01:35Z

delete sout in test




---


[jira] [Created] (IGNITE-6809) Use MPSC queue in striped pool

2017-11-01 Thread Igor Seliverstov (JIRA)
Igor Seliverstov created IGNITE-6809:


 Summary: Use MPSC queue in striped pool
 Key: IGNITE-6809
 URL: https://issues.apache.org/jira/browse/IGNITE-6809
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov
Priority: Normal


Use MPSC queue in striped pool



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


Re: IGNITE-6692 Select query on a client with unused field throws an exception.

2017-11-01 Thread Nikita Amelchev
Thanks for the comments.

I have done check to the existing schema through the
BinaryUtils.FLAG_HAS_SCHEMA flag [1].

Also, I have checked other places where we can try to read not initialized
schema and found that BinaryObjectBuilderImpl.ensureReadCacheInit() method
can do it. If we try to get from the BinaryObject, which contains no
fields, any field through BinaryObjectBuilder, it will throw an exception.
I have fixed this bug and suggest to include it in this issue. Please,
review [2]. Tests look good [3].

1. https://issues.apache.org/jira/browse/IGNITE-6692
2. https://reviews.ignite.apache.org/ignite/review/IGNT-CR-381
3.
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2918%2Fhead


2017-10-28 18:29 GMT+03:00 Dmitriy Setrakyan :

> On Fri, Oct 27, 2017 at 11:11 AM, Vladimir Ozerov 
> wrote:
>
> > Nikita,
> >
> > I am afraid this is incorrect fix, since zero is valid hash for schema.
> We
> > control whether the schema is est through the flag
> > BinaryUtils.FLAG_HAS_SCHEMA. Please try using it instead.
> >
>
> Vladimir, in that case how come the tests passed? Do we need to add a new
> test to enforce this scenario?
>



-- 
Best wishes,
Amelchev Nikita


Re: IGNITE-6666 BinaryObjectImpl.writeFieldByOrder method does not support TIME

2017-11-01 Thread Nikita Amelchev
Vladimir Ozerov, thank you for taking your time for the review, I have
implemented read part symmetrical to the write-related part. Please, look
at it again [1,2]. Tests passed OK [2].

1. https://issues.apache.org/jira/browse/IGNITE-
2. https://github.com/apache/ignite/pull/2878/files
3.
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2878%2Fhead


2017-10-30 10:51 GMT+03:00 Vladimir Ozerov :

> Hi Nikita,
>
> See my comments in the ticket.
>
> On Fri, Oct 20, 2017 at 11:54 AM, Nikita Amelchev 
> wrote:
>
> > Hello, Igniters!
> >
> > I found that the BinaryObjectImpl.writeFieldByOrder method does not
> > support
> > the TIME type [1]. I wrote test and fixed it [2]. TC tests look good [3].
> >
> > Please, review.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-
> > [2] https://github.com/apache/ignite/pull/2878/files
> > [3]
> > https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=
> > projectOverview_Ignite20Tests=pull%2F2878%2Fhead
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>



-- 
Best wishes,
Amelchev Nikita


Re: Ignite 2.3: troubles with key-value APIs in the cluster configured with DDL

2017-11-01 Thread Vladimir Ozerov
Denis,

See my comment in the ticket. It is a problem with scripts, not with engine.

On Sat, Oct 28, 2017 at 12:25 AM, Denis Magda  wrote:

> Vladimir,
>
> With pleasure, here is a ticker with the reproducer:
> https://issues.apache.org/jira/browse/IGNITE-6785
>
> —
> Denis
>
> > On Oct 24, 2017, at 5:57 AM, Vladimir Ozerov 
> wrote:
> >
> > Denis,
> >
> > Is it possible to create a test with reproducer? I am a bit lost.
> >
> > On Tue, Oct 24, 2017 at 3:12 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> It looks like the case sensitivity for the affinity key is a bug.
> Vladimir,
> >> what do you think?
> >>
> >> On Mon, Oct 23, 2017 at 11:19 AM, Denis Magda 
> wrote:
> >>
> >>> Vladimir, thanks a lot for looking into this!
> >>>
>  On Oct 23, 2017, at 12:35 AM, Vladimir Ozerov 
> >>> wrote:
> 
>  Denis,
> 
>  Now more detailed answer:
> 
>  1) It is expected that "City" class is not be found. You should set
>  key/value type names to fully-qualified class name to make it work.
>  Improvements: docs
> >>>
> >>> To make the Class-based key-vakye access and deserialization workable
> did
> >>> the following:
> >>> - follow your piece of advice providing full-qualified names in CREATE
> >>> TABLE;
> >>> - comment out ‘simpleName’ binary names mapper [1].
> >>>
> >>> However, it means that now the heterogeneous scenarios where .NET or
> C++
> >>> key-value access is needed are not supported. Do you have an
> >> understanding
> >>> on how this can be done in the feature releases?
> >>>
>  2) There is no need to implement hash code. Why did you do this?
> >>>
> >>> That’s a big surprise that we calculate it automatically if a key is
> >>> serialized into the binary form. Will be documented:
> >>> https://issues.apache.org/jira/browse/IGNITE-6717
> >>>
>  3) We will not have case-insensitive policy, SQL databases doesn't
> work
>  this way. In order to preserve case you should define column name in
> >>> quotes.
> >>>
> >>> Seems that the issue pin points to the affinity key case only:
> >>> - a field is defined as ‘CountryCode’ in DDL [2].
> >>> - in DML it can be used with any letters case - ‘countryCode’,
> >>> ‘countrycode’, etc,
> >>> - BinaryObjectBuild allowed me to define the field as `countryCode` [3]
> >>> w/o any issue.
> >>> - However, once I defined the field in CityKey class as is in DDL
> >>> (`CountryCode`) the following exception was thrown:
> >>>
> >>> Exception in thread "main" class org.apache.ignite.binary.
> >> BinaryObjectException:
> >>> Binary type has different affinity key fields
> >> [typeName=demo.model.CityKey,
> >>> affKeyFieldName1=COUNTRYCODE, affKeyFieldName2=CountryCode]
> >>>
> >>> and I forced to rename the field to `COUNTRYCODE` in CityKey class.
> Seems
> >>> like a bug?
> >>>
> >>>
> >>> [1] https://github.com/dmagda/ignite_world_demo/blob/master/
> >>> config/ignite-config.xml#L43
> >>> [2] https://github.com/dmagda/ignite_world_demo/blob/master/
> >>> ignite_world.sql#L31
> >>> [3] https://github.com/dmagda/ignite_world_demo/blob/master/
> >>> src/main/java/demo/keyvalue/KeyValueDataProcessing.java#L75
> >>> [4] https://github.com/dmagda/ignite_world_demo/blob/master/
> >>> src/main/java/demo/model/CityKey.java#L15
> >>>
> >>> —
> >>> Denis
> >>>
> >>>
> 
>  On Sat, Oct 21, 2017 at 2:34 PM, Vladimir Ozerov <
> voze...@gridgain.com
> >>>
>  wrote:
> 
> > Denis,
> >
> > SQL <-> key-Val transparency is complex thing, especially if you work
> >>> with
> > real Java classes instead of binary objects.
> >
> > We will try to improve something in 2.4, but do not expect great
> >>> usability
> > here. There is always be some pain in such scenarios.
> >
> > сб, 21 окт. 2017 г. в 9:23, Denis Magda :
> >
> >>
> >>> On Oct 20, 2017, at 3:56 PM, Denis Magda 
> wrote:
> >>>
> >>> * failed to deserialize BinaryObject value to City type [7]. Just
> >> classical "class org.apache.ignite.binary.
> >> BinaryInvalidTypeException:
> >> City" caused by "Caused by: java.lang.ClassNotFoundException:
> City”.
> >>
> >>
> >> Recalled that this should be caused by the fact that all the data
> was
> >> inserted with DML (cache.put(key, BinaryObjects)) and there was no
> >>> single
> >> cache.put(key, new City()) that would register City class. Guess we
> >>> need to
> >> add an API that forces classes registration from the app side or
> >>> something
> >> more efficient.
> >>
> >> —
> >> Denis
> >
> >
> >>>
> >>>
> >>
>
>


[GitHub] ignite pull request #2956: IGNITE-6701

2017-11-01 Thread dolphin1414
GitHub user dolphin1414 opened a pull request:

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

IGNITE-6701



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

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

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

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


commit be3e00e14a3df0ce82c62026eadc6ab4aaa3f1e4
Author: rkondakov 
Date:   2017-10-31T13:12:26Z

IGNITE-6701: Unnecessary deserialization eliminated in GridH2Table.doUpdate

commit a35f025a9a44b18ca6e80f44b2756f3996481934
Author: rkondakov 
Date:   2017-10-31T19:45:06Z

Merge branch 'master' into ignite-6701

commit 2c4d0ba6b0be2b4d9d73c4f8bb22a8ccef94a704
Author: rkondakov 
Date:   2017-11-01T07:32:05Z

IGNITE-6701: Minor refactoring




---


[jira] [Created] (IGNITE-6808) Web console: display full text in tooltip for case if row content text takes more then 1 row

2017-11-01 Thread Pavel Konstantinov (JIRA)
Pavel Konstantinov created IGNITE-6808:
--

 Summary: Web console: display full text in tooltip for case if row 
content text takes more then 1 row
 Key: IGNITE-6808
 URL: https://issues.apache.org/jira/browse/IGNITE-6808
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Pavel Konstantinov


I noticed that sometimes event text doesn't fit in the visible part of the cell.
And I wasn't able to see what text is hidden.
So we need to show full text in the tooltip.



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


Re: Let's keep Apache Ignite docs up-to-date

2017-11-01 Thread Pavel Tupitsyn
Denis,

> Could you show me any example of such a documentation where docs are
stored in git and can be visualized by GitHub (dev stage) and 3rd party
engine (release on the site)?

1) Apache Spark
Source: https://github.com/apache/spark/tree/master/docs
Docs: https://spark.apache.org/documentation.html
(uses Jekyll)

2) Microsoft .NET
Source: https://github.com/dotnet/docs
Docs: https://docs.microsoft.com/en-us/dotnet/
(uses DocFX)


Both of these engines (Jekyll and DocFX) use markdown, which can be
visualized by github, and converted to HTML for the web site.
Markdown can also be visualized by many IDEs, so it is easy to edit locally.

Ideally, API docs (javadoc) should be integrated with the rest of the docs,
so users can navigate to the corresponding APIs.
This can't be achieved nicely with readme.io.


> having docs under separate git repository
I don't think we need a separate repo, we can just create branches in our
main repo for that.
It is nice to have everything in one place.

On Wed, Nov 1, 2017 at 6:30 AM, Dmitriy Setrakyan 
wrote:

> On Tue, Oct 31, 2017 at 8:15 PM, Yakov Zhdanov 
> wrote:
>
> > I would also consider having docs under separate git repository. Separate
> > since we need to have an opportunity to revisit documentation for already
> > released versions.
> >
>
> This should not be a problem.
>