[jira] [Created] (IGNITE-7254) Add more ways to activate a cluster to the error message for an inactive cluster

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7254:


 Summary: Add more ways to activate a cluster to the error message 
for an inactive cluster
 Key: IGNITE-7254
 URL: https://issues.apache.org/jira/browse/IGNITE-7254
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Priority: Minor


Need to mention REST API and control.sh script (and Visorcmd, if activation is 
supported)



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

[jira] [Created] (IGNITE-7253) JDBC thin driver: introduce streaming mode

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7253:
---

 Summary: JDBC thin driver: introduce streaming mode
 Key: IGNITE-7253
 URL: https://issues.apache.org/jira/browse/IGNITE-7253
 Project: Ignite
  Issue Type: Task
  Components: jdbc, sql
Reporter: Vladimir Ozerov
Assignee: Roman Kondakov
 Fix For: 2.4


Should be done after IGNITE-6022. We should allow optional streaming mode for 
JDBC driver. In this mode only INSERTs without SELECT should be possible. All 
other DML operations should throw an exception. 

Design considerations:
1) Add command {{SET STREAMING=1|ON|0|OFF}} which will enable or disable 
streaming for connection.
2) Add command {{STREAMER FLUSH}} which will force data flush.
3) Only INSERT without SELECT works, all other DML statements should throw an 
exception
4) It should be possible to stream into several tables simultaneously (i.e. 
several streamers could be opened)
5) Any DDL statement should force flush of all currently opened streamers.



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

[jira] [Created] (IGNITE-7252) No need to initialize BinaryMetadata working directory for client mode.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-7252:
--

 Summary: No need to initialize BinaryMetadata working directory 
for client mode.
 Key: IGNITE-7252
 URL: https://issues.apache.org/jira/browse/IGNITE-7252
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.3
Reporter: Stanilovsky Evgeny
Assignee: Sergey Chugunov
Priority: Minor
 Fix For: 2.4


While node starts with client mode and pds enabled, it still tries to get 
access to lfs working directory in BinaryMetadataFileStore if no access granted 
it will fail with exception

{noformat}
Caused by: class org.apache.ignite.IgniteCheckedException: Cannot write to 
directory: /path/to/lfs/grid_name
 at 
org.apache.ignite.internal.util.IgniteUtils.resolveWorkDirectory(IgniteUtils.java:9128)
 at 
org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolvePersistentStoreBasePath(PdsConsistentIdProcessor.java:453)
 at 
org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.prepareNewSettings(PdsConsistentIdProcessor.java:157)
 at 
org.apache.ignite.internal.processors.cache.persistence.filename.PdsConsistentIdProcessor.resolveFolders(PdsConsistentIdProcessor.java:137)
 at 
org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.(BinaryMetadataFileStore.java:73)
 at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:160)
 at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1897)
{noformat}




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

default SQL timeout

[Dmitriy Setrakyan]

Igniters,

Is there any way to set a default SQL timeout for queries? If not, should
we have it?

D.

Re: Time and scope for Apache Ignite 2.4

[Nikolay Izhikov]

Hello, Denis

> - Nikolay Izhikov: Data Frames.

I'm waiting for Valentin Kulichenko review.
If and when further comments for DataFrame pull request appears I will
fix them immediately.

В Вт, 19/12/2017 в 12:07 -0800, Denis Magda пишет:
> Igniters,
> 
> It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#
> ApacheIgnite2.4-RequiredTickets  display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets>
> 
> How good are we if to assume 5th of Jan as a code freeze date? Please
> comment:
> - Nikolay Izhikov: Data Frames.
> - Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the
> list.
> - Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
> - Yuri: Machine Learning + neural networks
> - Vladimir Ozerov: Java 9 and Java 7
> - Sergey Kozlov: SQL scope testing
> - etc.: please check the link with the features.
> 
> —
> Denis
> > On Dec 4, 2017, at 1:11 PM, Denis Magda  wrote:
> > 
> > Igniters,
> > 
> > Basing on the amount of improvements, fixes and features stacked in
> > the master branch I think it’s a right time to negotiate the scope
> > and time of the next Apache Ignite 2.4 release. I’m ready to step
> > in as a release manager if none of the committers wants to try on
> > this role.
> > 
> > Here is a release page:
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.
> > 4  > +2.4>
> > 
> > Proposed time date: Jan 5 - code freeze -> stabilization and
> > testing -> Jan 24 - voting -> Jan 31 release.
> > 
> > In my view improvements such Java 9 support and Java 7
> > discontinuation, memory metrics in bytes [1], binary client
> > protocol, etc. needs to get into the release. All the features like
> > that are labeled “important” in JIRA. Use this label if you are
> > convinced a task has to be release in 2.4.
> > 
> > What’s about machine learning, bulk loading [2], internals problems
> > resolution [3], metrics [4] related tasks? What goes in 2.4 and
> > what’s shifted?
> > 
> > [1] https://issues.apache.org/jira/browse/IGNITE-6902  > es.apache.org/jira/browse/IGNITE-6902>
> > [2] https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bul
> > k+data+loading+performance+improvements  > onfluence/display/IGNITE/IEP-
> > 1:+Bulk+data+loading+performance+improvements>
> > [3] https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ign
> > ite+internal+problems+detection  > e/display/IGNITE/IEP-7:+Ignite+internal+problems+detection>
> > [4] https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Met
> > rics+improvements  > TE/IEP-6:+Metrics+improvements>
> > 
> > —
> > Denis
> 
> 

Re: Time and scope for Apache Ignite 2.4

[Denis Magda]

Igniters,

It’s time to sync up on the progress of IMPORTANT tasks for 2.4:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4#ApacheIgnite2.4-RequiredTickets
 


How good are we if to assume 5th of Jan as a code freeze date? Please comment:
- Nikolay Izhikov: Data Frames.
- Sergey Kalashnikov, Vladimir Ozerov: DDL and SQL features from the list.
- Andrey Kuznetsov, Alexandr Fedotov: memory metrics tasks.
- Yuri: Machine Learning + neural networks
- Vladimir Ozerov: Java 9 and Java 7
- Sergey Kozlov: SQL scope testing
- etc.: please check the link with the features.

—
Denis
> On Dec 4, 2017, at 1:11 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Basing on the amount of improvements, fixes and features stacked in the 
> master branch I think it’s a right time to negotiate the scope and time of 
> the next Apache Ignite 2.4 release. I’m ready to step in as a release manager 
> if none of the committers wants to try on this role.
> 
> Here is a release page:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.4 
> 
> 
> Proposed time date: Jan 5 - code freeze -> stabilization and testing -> Jan 
> 24 - voting -> Jan 31 release.
> 
> In my view improvements such Java 9 support and Java 7 discontinuation, 
> memory metrics in bytes [1], binary client protocol, etc. needs to get into 
> the release. All the features like that are labeled “important” in JIRA. Use 
> this label if you are convinced a task has to be release in 2.4.
> 
> What’s about machine learning, bulk loading [2], internals problems 
> resolution [3], metrics [4] related tasks? What goes in 2.4 and what’s 
> shifted?
> 
> [1] https://issues.apache.org/jira/browse/IGNITE-6902 
> 
> [2] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-1%3A+Bulk+data+loading+performance+improvements
>  
> 
> [3] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-7%3A+Ignite+internal+problems+detection
>  
> 
> [4] 
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-6%3A+Metrics+improvements
>  
> 
> 
> —
> Denis

Re: Removing "fabric" from Ignite binary package name

[Denis Magda]

All the bids were accepted and the verdict is executed:
https://issues.apache.org/jira/browse/IGNITE-7251 


Who is ready to pick this up?

—
Denis

> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov  
> wrote:
> 
> +1б фо шур
> 
> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov 
> wrote:
> 
>> +1б вуаштшеудн
>> 
>> On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>> 
>>> +1
>>> 
>>> On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org
 
>>> wrote:
>>> 
 +1 (completely agree)
 
 On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda 
>> wrote:
 
> Igniters,
> 
> Apache Ignite binary releases still include “fabric” word in their
>>> names:
> https://ignite.apache.org/download.cgi#binaries <
> https://ignite.apache.org/download.cgi#binaries>
> 
> For instance, this is a full name of the previous release -
> apache-ignite-fabric-2.3.0-bin.
> It’s a little oversight on our side because the project has not been
> positioned as a fabric for a while.
> 
> Proposal! Remove “fabric” from the name and have the binary releases
 named
> as - apache-ignite-{version}-bin.
> 
> If we’re in consensus then let’s make the change in 2.4.
> 
> —
> Denis
> 
 
>>> 
>> 

[jira] [Created] (IGNITE-7251) Remove term "fabric" from Ignite deliverables

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7251:
---

 Summary: Remove term "fabric" from Ignite deliverables
 Key: IGNITE-7251
 URL: https://issues.apache.org/jira/browse/IGNITE-7251
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Priority: Blocker
 Fix For: 2.4


Apache Ignite binary releases still include “fabric” word in their names:
https://ignite.apache.org/download.cgi#binaries

For instance, this is a full name of the previous release - 
apache-ignite-fabric-2.3.0-bin.
It’s a little oversight on our side because the project has not been positioned 
as a fabric for a while.

Remove “fabric” from the name and have the binary releases named as - 
apache-ignite-{version}-bin.



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

Re: Partition loss policy - how to use?

[Denis Magda]

Alex K., thanks for stepping in.

It will be vivid what to do on the tooling side once it’s clear how to use the 
feature in general.

Alex G., Sam, Yakov, could you comment on this point below?

>> And finally (most importantly), I'm a bit confused
>> by Ignite#resetLostPartitions method itself. What are the best practices
>> for using it? How a user should decide that partitions are actually
>> restored and how should he choose when to call this method? For example, if
>> we have persistence enabled, is it enough to just bring back the nodes or
>> something else is needed? Actually, why don't we detect this automatically
>> in this scenario?

—
Denis

> On Dec 19, 2017, at 2:01 AM, Alexey Kuznetsov  wrote:
> 
> Val,
> 
> I'm not an expert in how caches subsystem works internally,
> but  I think it is a good idea to add this info and tooling to Web Console
> / Visor.
> 
> Could you create issues with description on what part of Web Console /
> Visor it could be added.
> I guess for Visor CMD  it could be some mode for "cache"  command I think.
> 
> 
> On Fri, Dec 15, 2017 at 8:54 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> 
>> Folks,
>> 
>> Since 2.0 we have introduced PartitionLossPolicy which blocks access to
>> cache if data loss occurred. This is an awesome feature, however it is not
>> very clear how to use it properly.
>> 
>> First of all, there is no documentation. Ticket already exists though and
>> hopefully it will be completed soon:
>> https://issues.apache.org/jira/browse/IGNITE-6994
>> 
>> Second of all, looks like there is no required tooling. Visor and Web
>> Console should be able to show the status (i.e. which partitions are
>> available and which are not), fire alerts in case of partition loss,
>> provide an ability to restore partitions via Ignite#resetLostPartitions
>> method, etc.
>> 
>> And finally (most importantly), I'm a bit confused
>> by Ignite#resetLostPartitions method itself. What are the best practices
>> for using it? How a user should decide that partitions are actually
>> restored and how should he choose when to call this method? For example, if
>> we have persistence enabled, is it enough to just bring back the nodes or
>> something else is needed? Actually, why don't we detect this automatically
>> in this scenario?
>> 
>> I would appreciate any inputs and thoughts on this topic.
>> 
>> -val
>> 
> 
> 
> 
> -- 
> Alexey Kuznetsov

[jira] [Created] (IGNITE-7250) Apache Ignite Transactional Subsystem Architecture

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7250:
---

 Summary: Apache Ignite Transactional Subsystem Architecture
 Key: IGNITE-7250
 URL: https://issues.apache.org/jira/browse/IGNITE-7250
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.4


A couple of community members prepared a well-defined document about Ignite 
transactions architecture. See the PDF version attached. 

Use this document to enrich the existing page on Ignite transactions. Even 
more, it makes sense to define a unique category for transactions and create 
several pages.



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

[GitHub] ignite pull request #3253: Ignite-1553

[voipp]

GitHub user voipp opened a pull request:

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

Ignite-1553



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

$ git pull https://github.com/voipp/ignite IGNITE-1553

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

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


commit 4051afc7ec89d48971c127cb4426175defe4fb37
Author: voipp 
Date:   2017-12-15T16:39:51Z

batchStoreCommit split into prepare and commit methods. Still prepares and 
commits on final phase

commit d22822ac2f580f9667d8cf3de0bf16234d111eb9
Author: voipp 
Date:   2017-12-19T15:11:03Z

draft




---

[jira] [Created] (IGNITE-7249) SQL TX: Commit/rollback active TX before processing DDL statement

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-7249:


 Summary: SQL TX: Commit/rollback active TX before processing DDL 
statement
 Key: IGNITE-7249
 URL: https://issues.apache.org/jira/browse/IGNITE-7249
 Project: Ignite
  Issue Type: Test
  Components: sql
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov






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

[jira] [Created] (IGNITE-7248) "Schema not found" error when setting streaming mode for JDBC driver

[Alexey Kukushkin (JIRA)]

Alexey Kukushkin created IGNITE-7248:


 Summary: "Schema not found" error when setting streaming mode for 
JDBC driver
 Key: IGNITE-7248
 URL: https://issues.apache.org/jira/browse/IGNITE-7248
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Alexey Kukushkin


Using JDBC "thick" driver in streaming mode fails with a "Schema not found" 
erorr:

Connection connection = 
DriverManager.getConnection("jdbc:ignite:cfg://streaming=true:cache=CACHE@file:/path-to-ignite-config.xml");

// using connection to create a table works fine but this exception is 
generated when using the connection to execute INSER INTO...

class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
to set schema for DB connection for thread [schema=]

org.h2.jdbc.JdbcSQLException: Schema  not found; SQL statement:
SET SCHEMA "" [90079-195]

See [link 
UserList|https://mail.google.com/mail/u/0/#label/Apache+Ignite+Users/15f25f4d70ade793]
 for more details




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

Re: Removing "fabric" from Ignite binary package name

[Anton Vinogradov]

+1б фо шур

On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov 
wrote:

> +1б вуаштшеудн
>
> On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > +1
> >
> > On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > +1 (completely agree)
> > >
> > > On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda 
> wrote:
> > >
> > > > Igniters,
> > > >
> > > > Apache Ignite binary releases still include “fabric” word in their
> > names:
> > > > https://ignite.apache.org/download.cgi#binaries <
> > > > https://ignite.apache.org/download.cgi#binaries>
> > > >
> > > > For instance, this is a full name of the previous release -
> > > > apache-ignite-fabric-2.3.0-bin.
> > > > It’s a little oversight on our side because the project has not been
> > > > positioned as a fabric for a while.
> > > >
> > > > Proposal! Remove “fabric” from the name and have the binary releases
> > > named
> > > > as - apache-ignite-{version}-bin.
> > > >
> > > > If we’re in consensus then let’s make the change in 2.4.
> > > >
> > > > —
> > > > Denis
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-7247) C++: Change default mapper behavior for BinaryConfiguration

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-7247:


 Summary: C++: Change default mapper behavior for 
BinaryConfiguration
 Key: IGNITE-7247
 URL: https://issues.apache.org/jira/browse/IGNITE-7247
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.3
Reporter: Alexey Popov


C# and Java use the following BinaryConfiguration params by default:
*BinaryBasicNameMapper with simpleName property set to false, and 
*BinaryBasicIdMapper with lowerCase property set to true.
while
C++ uses the following BinaryConfiguration params by default:
*BinaryBasicNameMapper with simpleName property set to *true*, and 
*BinaryBasicIdMapper with lowerCase property set to true.

So, the Java (for instance, a Visor app) can't join C++ nodes by default.

Let's have the default configuration properties the same for all platforms.

The same issue was changed for .NET under 
https://issues.apache.org/jira/browse/IGNITE-2398




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

[jira] [Created] (IGNITE-7246) MarshallerContextimpl.putAtIndex

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7246:


 Summary: MarshallerContextimpl.putAtIndex
 Key: IGNITE-7246
 URL: https://issues.apache.org/jira/browse/IGNITE-7246
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.4
Reporter: Alexander Belyak
Priority: Minor


1) putAtIndex in org.apache.ignite.internal.MarshallerContextImpl contains code 
for unordered insertion, but it didn't work (add only into tail of allCaches 
collection). Test:
{panel}
public static void main(String[] args) {
ArrayList> all = new ArrayList<>();
ConcurrentMap m0 = new ConcurrentHashMap<>();
ConcurrentMap m1 = new ConcurrentHashMap<>();
putAtIndex(m1, all,(byte)1, all.size());
putAtIndex(m0, all, (byte)0, all.size());
System.out.println(all.get(0)==m0);
System.out.println(all.get(1)==m1);
System.out.println(all.size());
}
{panel}
2) Interface Collection is unordered (javadoc: "Some are ordered and others 
unordered") so its better to use List interface;
3) putAtIndex called only from getCacheFor(byte) method from synchro block so 
it can get size of allCaches by itself



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

[GitHub] ignite pull request #3252: Ignite 1.9.3 p2

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite 1.9.3 p2



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

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

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

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


commit 8c56e4516e55c7ed9c14779f0e77e00f055d9a81
Author: vozerov-gridgain 
Date:   2016-09-02T15:05:16Z

IGNITE-3827: Removed double marshalling of keys in 
DataStreamerImpl.addData(Map) method.

commit 4dc624fc9a8852f77f1fe7db4dc06a474b34c2eb
Author: vozerov-gridgain 
Date:   2016-09-02T15:23:09Z

IGNITE-3829: Optimized affinity key field name handling.

commit 7b0d2326ccc62afd5d162b056398f96d8d7c9100
Author: vozerov-gridgain 
Date:   2016-09-05T07:19:48Z

IGNITE-3829: Additional fix.

commit b8cb82de65a529040ea18b0dc03fa7109c69bb4a
Author: Vasiliy Sisko 
Date:   2016-12-29T07:48:45Z

IGNITE-4442 Implemented cache affinity configuration.

(cherry picked from commit f4a1e6c)

commit 71412cecd861119965a873520da96078f99c94e2
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 852f03829c997883376245e3515e47822e9012eb
Author: Andrey Novikov 
Date:   2017-01-11T09:34:23Z

Merge branches 'ignite-1.7.5' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit fe424591161595de1151a29cf1cdeb50456c3e39
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:43:21Z

Minors

commit cf9f0a79da7540dc40c3ac860a94158e87e2d7ec
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:50:02Z

Minors

commit d3e2e0c5574f7677645e73e1fbafaee3563895f1
Author: Andrey Novikov 
Date:   2017-01-25T07:27:01Z

Merge branches 'ignite-1.7.6' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit 295f80d10da02692540435d46961a9c3cca99b3c
Author: Andrey Novikov 
Date:   2017-01-25T06:58:57Z

IGNITE-4520 Added credential request for authentication on proxy.

(cherry picked from commit ef04f35)

commit faa20530a707014ac34477cba8adaaa4b67de1bb
Author: Andrey Novikov 
Date:   2017-01-25T09:48:05Z

IGNITE-1596 Fixed version sort.

(cherry picked from commit 128ba07)

commit 1b3bbdb1758eb19c755dabcb5fe329529fa0f378
Author: Andrey Novikov 
Date:   2017-01-27T04:30:49Z

IGNITE-4622 Fixed generation in domain model for cache store.

(cherry picked from commit 43007d5)

commit a8355feef630a5c8c4edbe02224c8325dd5952d3
Author: Andrey Novikov 
Date:   2017-02-03T04:58:43Z

IGNITE-4610 Added more informative message.

(cherry picked from commit 9ff2a8f)

commit 94d8a6fc0a61bb3046e2ebd8b3cbffb8917c2b6a
Author: Andrey Novikov 
Date:   2017-02-08T04:43:22Z

IGNITE-4472 Added user activities in Web Console.

(cherry picked from commit 26ee9c2)

commit b571fd40f009709718bce0c969d47b62be06b8f6
Author: Andrey Novikov 
Date:   2017-02-08T10:05:08Z

IGNITE-4472 Added user activities in Web Console.

(cherry picked from commit 26ee9c2)

commit db48f545a83bb72cded77d8269fe4f8820e8380f
Author: Andrey Novikov 
Date:   2017-02-10T08:55:05Z

IGNITE-4678 Web Console: Implemented demo load as service.

(cherry picked from commit a600caf)

commit e4b54c985f256478ae2cae23b423d9b8e0842df8
Author: Andrey Novikov 
Date:   2017-02-13T02:48:50Z

Merge branch 'ignite-1.8.3' of https://github.com/gridgain/apache-ignite 
into web-console-production

commit 2d6735a20ac8009d1ac3f003da4fcd319271bd71
Author: Alexey Kuznetsov 
Date:   2017-02-09T09:44:41Z

IGNITE-4676 Fixed hang if closure executed nested internal task with 
continuation. Added test.

(cherry picked from commit e7a5307)

commit d307e2eced1fd10b007ee08c3dd113e7bb4f22ba
Author: Andrey Novikov 
Date:   2017-02-13T10:35:29Z

IGNITE-4687 Added pool to process REST request in Web Agent.

(cherry picked from commit 262a341)

commit 8874f99f44dc2edf08a525619edb49d5db70b938
Author: dkarachentsev 
Date:   2017-02-14T15:44:57Z

IGNITE-4641 - Refresh client attributes during reconnect

commit ca5956bedfc0c3bd18290c64b6a6c2e3f114a440
Author: Andrey Novikov 
Date:   2017-02-14T16:28:06Z

IGNITE-4472 UI fix, minor fixes

(cherry picked from commit 79e1e53)

commit db9252c9588c671279664484bb8c397312d265e6
Author: Andrey Novikov 
Date:   2017-02-15T09:08:57Z

IGNITE-4678 Node version in range.

(cherry picked from commit 2cfd55d)

commit 58c0c49d31605bf4608e7ee97099b75b324a782f
Author: Andrey Novikov 
Date:   2017-02-16T03:41:30Z

IGNITE-4472 Fixed became this user.

(cherry picked from commit ee832e4)

commit 2ccbf32ea3ecaff1068832accf37235a32734

[GitHub] ignite pull request #3251: IGNITE-7242: Broken javadoc for KNN

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Created] (IGNITE-7245) Missing description in javadoc for ignite-dev-utils

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7245:


 Summary: Missing description in javadoc for ignite-dev-utils
 Key: IGNITE-7245
 URL: https://issues.apache.org/jira/browse/IGNITE-7245
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov
Priority: Minor


Need add description in java doc



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

[jira] [Created] (IGNITE-7244) Missing README.txt for ignite-dev-utils module

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7244:


 Summary: Missing README.txt for ignite-dev-utils module
 Key: IGNITE-7244
 URL: https://issues.apache.org/jira/browse/IGNITE-7244
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Suntsov


We need to add some information about this module in README.txt




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

[GitHub] ignite pull request #3251: IGNITE-7242: Broken javadoc for KNN

[YuriBabak]

GitHub user YuriBabak opened a pull request:

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

IGNITE-7242: Broken javadoc for KNN

fixed

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

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

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

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


commit 25f0d5de50555a4fb93b697141a0eb23c8632471
Author: YuriBabak 
Date:   2017-12-19T10:26:06Z

IGNITE-7242: Broken javadoc for KNN

fixed




---

[jira] [Created] (IGNITE-7243) Web console: Improve phone number field on profile page

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7243:
-

 Summary: Web console: Improve phone number field on profile page
 Key: IGNITE-7243
 URL: https://issues.apache.org/jira/browse/IGNITE-7243
 Project: Ignite
  Issue Type: Bug
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov


Should contain information about expected international number format.
Add number formatting and validation.
Country code can be detected automatically from selected country field.




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

Re: IGNITE-7107 Apache Ignite RPM packages

[vveider]

Done. See updated PR#3171 [1]


[1] https://github.com/apache/ignite/pull/3171



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

[jira] [Created] (IGNITE-7242) Broken javadoc for KNN

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7242:
--

 Summary: Broken javadoc for KNN
 Key: IGNITE-7242
 URL: https://issues.apache.org/jira/browse/IGNITE-7242
 Project: Ignite
  Issue Type: Bug
  Components: ml
Reporter: Yury Babak
Assignee: Yury Babak
 Fix For: 2.4






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

[jira] [Created] (IGNITE-7241) Create shell (bat) script for run IgniteWalConverter

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7241:


 Summary: Create shell (bat) script for run IgniteWalConverter
 Key: IGNITE-7241
 URL: https://issues.apache.org/jira/browse/IGNITE-7241
 Project: Ignite
  Issue Type: Improvement
  Components: build
Affects Versions: 2.3
Reporter: Ilya Suntsov


IgniteWalConverter allow us to parse WAL.
I guess we should add to {{bin}} directory script that will start this 
converter with parameters.



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

Re: Partition loss policy - how to use?

[Alexey Kuznetsov]

Val,

I'm not an expert in how caches subsystem works internally,
 but  I think it is a good idea to add this info and tooling to Web Console
/ Visor.

Could you create issues with description on what part of Web Console /
Visor it could be added.
I guess for Visor CMD  it could be some mode for "cache"  command I think.


On Fri, Dec 15, 2017 at 8:54 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Folks,
>
> Since 2.0 we have introduced PartitionLossPolicy which blocks access to
> cache if data loss occurred. This is an awesome feature, however it is not
> very clear how to use it properly.
>
> First of all, there is no documentation. Ticket already exists though and
> hopefully it will be completed soon:
> https://issues.apache.org/jira/browse/IGNITE-6994
>
> Second of all, looks like there is no required tooling. Visor and Web
> Console should be able to show the status (i.e. which partitions are
> available and which are not), fire alerts in case of partition loss,
> provide an ability to restore partitions via Ignite#resetLostPartitions
> method, etc.
>
> And finally (most importantly), I'm a bit confused
> by Ignite#resetLostPartitions method itself. What are the best practices
> for using it? How a user should decide that partitions are actually
> restored and how should he choose when to call this method? For example, if
> we have persistence enabled, is it enough to just bring back the nodes or
> something else is needed? Actually, why don't we detect this automatically
> in this scenario?
>
> I would appreciate any inputs and thoughts on this topic.
>
> -val
>



-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-7240) Upload ignite-dev-utils module in maven

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7240:


 Summary: Upload ignite-dev-utils module in maven
 Key: IGNITE-7240
 URL: https://issues.apache.org/jira/browse/IGNITE-7240
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 2.1
Reporter: Ilya Suntsov


Module  ignite-dev-utils allow us to parse WAL.
We should upload it to maven.



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

[jira] [Created] (IGNITE-7239) In case of not serializable cache update response, future on node requester will never complete

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-7239:
---

 Summary: In case of not serializable cache update response, future 
on node requester will never complete
 Key: IGNITE-7239
 URL: https://issues.apache.org/jira/browse/IGNITE-7239
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Dmitry Karachentsev
Priority: Minor


To avoid such hang, if response could not be serialized, create other response 
with text of the error.



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

IGNITE-5136 is ready for review (GridLogThrottle memory leak)

[Дмитрий Рябов]

Hello, igniters!
I've done with this ticket, tests are ok. Can you review?

JIRA: https://issues.apache.org/jira/browse/IGNITE-5136
PR: https://github.com/apache/ignite/pull/3236
Upsource (old changes):
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-344
Upsource (new changes):
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-436
CI tests: 
https://ci.ignite.apache.org/viewLog.html?buildId=1004471&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAll

Re: Future linux packages repositories

[Petr Ivanov]

Denis, Yakov, thanks for feedback!


As far as I understand the process of uploading our current binary archives to 
apache.org/dist, we just have to prepare corresponding debian / rhel 
repositories directory structure and upload it as well as binaries (and add new 
instructions to documentation).
So, I guess, I’ll push with packages to be able to introduce full debian / rhel 
delivery to the nearest release.



> On 18 Dec 2017, at 21:25, Denis Magda  wrote:
> 
> Totally for hosting the packages on ASF infrastructure.
> 
> Petr if anything is required from the ASF side please file tickets and 
> inquiries to INFRA using JIRA. Let me know if my assistance is needed.
> 
> —
> Denis
> 
>> On Dec 18, 2017, at 2:46 AM, Yakov Zhdanov  wrote:
>> 
>> Thanks for update, Petr. I like the solution. I think we can go ahead.
>> 
>> --Yakov
> 

[jira] [Created] (IGNITE-7238) Web console: incorrect "Download agent" button color

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7238:


 Summary: Web console: incorrect "Download agent" button color
 Key: IGNITE-7238
 URL: https://issues.apache.org/jira/browse/IGNITE-7238
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Ilya Borisov
Priority: Minor


*How to reproduce:*
1. Start demo mode, do not start a web agent.
2. Wait for "Connection to Ignite Web Agent is not established" dialog to 
appear.
3. Focus on "Download agent" using Tab button (or any other way).

*What happens:*
"Download agent" label becomes red.

*What should happen:*
"Download agent" label should remain white.



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

[jira] [Created] (IGNITE-7237) Web console: Wrong switcher behaviour on grid deactivation

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7237:
-

 Summary: Web console: Wrong switcher behaviour on grid deactivation
 Key: IGNITE-7237
 URL: https://issues.apache.org/jira/browse/IGNITE-7237
 Project: Ignite
  Issue Type: Bug
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Run node and agent.
# Open notebook page.
# Activate grid.
# Deactivate grid.

In process of deactivation switcher transit to off state. In that transition 
*Deactivation...* message is changed to "Activation...". Progress animation is 
showed in some time after switcher state was changed.



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

[jira] [Created] (IGNITE-7236) SQL: create tests for optimized INSERT and MERGE operations

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7236:
---

 Summary: SQL: create tests for optimized INSERT and MERGE 
operations
 Key: IGNITE-7236
 URL: https://issues.apache.org/jira/browse/IGNITE-7236
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.4


Important optimization IGNITE-4490 was added to the product. However, it lacks 
excessive tests coverage. We need to test the following scenarios:
1) Various data types (especially dates)
2) Single updates vs batched updates
3) Constants and nulls (e.g. {{INSERT INTO ... VALUES (a, b)}})
4) Parameters (e.g. {{INSERT INTO ... VALUES (?, ?)}})
5) Multiple SQL statements at once (e.g. {{INSERT INTO ...; INSERT INTO ...}})
6) Insert multiple lines at once ({{INSERT INTO ... VALUES (a1, b1), (a2, b2)}})
7) Insert multiple lines with parameters
8) Invalid parameters count in different query types - need to make sure that 
we throw correct errors.

All tests except of p.8 should check both correctness and the fact that query 
was executed without H2 involvement (e.g. using some code hack).



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

[GitHub] ignite pull request #1387: IGNITE-4490 Query-less INSERT and MERGE

[asfgit]

Github user asfgit closed the pull request at:

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


---