[GitHub] ignite pull request #3247: IGNITE-7229 .NET: Rename ICache.QueryFields to Qu...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Removing "fabric" from Ignite binary package name

[Vladimir Ozerov]

+1, definitely

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

Re: Removing "fabric" from Ignite binary package name

[Vladimir Ozerov]

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

Re: Removing "fabric" from Ignite binary package name

[Valentin Kulichenko]

+1

On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan 
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
> >
>

[GitHub] ignite pull request #3250: IGNITE-3464

[BiryukovVA]

GitHub user BiryukovVA opened a pull request:

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

IGNITE-3464

Fixed bug - race between partition exchange and prepare/finish requests.

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

$ git pull https://github.com/BiryukovVA/ignite IGNITE-3464

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

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


commit a370e2f30008b244f26fcdda0eb0a30e8132f04a
Author: Vitaliy Biryukov 
Date:   2017-12-18T23:15:24Z

IGNITE-3464: Fixed bug - race between partition exchange and prepare/finish 
requests.




---

[GitHub] ignite pull request #3249: IGNITE-6785: Affinity key field ignore case.

[dolphin1414]

GitHub user dolphin1414 opened a pull request:

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

IGNITE-6785: Affinity key field ignore case.

Fix for an affinity field name upper-case issue.

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

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

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

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


commit acf0e7dada672e6cd0027d46977279a7c0ab9f91
Author: rkondakov 
Date:   2017-12-18T20:29:32Z

IGNITE-6785: Changed affinity key fields names comparison from the equals() 
to equalsIgnoreCase().




---

Re: Removing "fabric" from Ignite binary package name

[Dmitriy Setrakyan]

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

Re: Future linux packages repositories

[Denis Magda]

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

Re: IGNITE-7107 Apache Ignite RPM packages

[Denis Magda]

Hi Petr,

Proposed to rename Ignite binary packages so that there is no “fabric” 
mentioning:
http://apache-ignite-developers.2346864.n4.nabble.com/Removing-quot-fabric-quot-from-Ignite-binary-package-name-td25419.html
 


Please consider this for RPM and DEB packages/instructions. 

All the docs including DEVNOTES.txt will be updated once the “fabric” name is 
purged.

—
Denis

> On Dec 17, 2017, at 11:59 PM, vveider  wrote:
> 
> Hi, Denis!
> 
> Can you be a little bit more specific about "fabric" mentions? What exactly
> should be renamed?
> Package has final name "apache-ignite-fabric" in order to follow the
> convention of upstream source naming and DEVNOTES.txt instructions just name
> files as they are.
> 
> 
> 
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Removing "fabric" from Ignite binary package name

[Denis Magda]

Igniters,

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.

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-7235) Add warning with with a list of restrictions when Ignite native persistence is used with write-though cache store

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7235:


 Summary: Add warning with with a list of restrictions when Ignite 
native persistence is used with write-though cache store
 Key: IGNITE-7235
 URL: https://issues.apache.org/jira/browse/IGNITE-7235
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.4






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

[GitHub] ignite pull request #3248: IGNITE-6736: Switched GridCacheMapEntry synchroni...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6736: Switched GridCacheMapEntry synchronization to locks.

For test purpose

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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6736

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

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


commit 009e8710779355feb375ce63a60a24f12900c761
Author: Andrey Kuznetsov 
Date:   2017-12-18T15:36:01Z

IGNITE-6736: Switched GridCacheMapEntry synchronization to locks.




---

[jira] [Created] (IGNITE-7234) Optimize TC suites

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-7234:
-

 Summary: Optimize TC suites
 Key: IGNITE-7234
 URL: https://issues.apache.org/jira/browse/IGNITE-7234
 Project: Ignite
  Issue Type: Task
  Components: build
Affects Versions: 2.3
Reporter: Sergey Kozlov


The current organization of test suites on CI servers looks like inefficient. 
We've 90+ test suites and the number of tests is permanently growing.

The plan of optimization might look following:
# Analyze and join short executed suites into single(s) suite
# Analyze execution time of suites (tests) to check ability to split tests into 
regular and long running suites (e.g. Basic and Basic Long, Cache and Cache 
Long, etc)
# Check the approach to compile binaries at once and the run tests against them
# Make the report of distribution of time-execution of tests, for instance:
0-10%: X tests
11-20%: Y tests 
...





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

Re: IGNITE-7203 Java 8 by default

[Yury Babak]

Hi,

please check github review comments.

Regards,
Yury



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

[GitHub] ignite pull request #3247: IGNITE-7229 .NET: Rename ICache.QueryFields to Qu...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7229 .NET: Rename ICache.QueryFields to Query, add FieldNames



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

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

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

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


commit 8abf09fcdcec0a259fcab4345e64db2f5f133f3d
Author: Pavel Tupitsyn 
Date:   2017-12-18T11:37:27Z

IGNITE-7229 .NET: Rename ICache query methods to Query

commit 6758d728b33b53033261011ef8ea7a9a96d5fd46
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:07:49Z

wip

commit 85ec136958c41ac03af585d39e42284e868d4ca3
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:10:42Z

wip

commit 3f55d7383ed0e07269ebfcda472ae9d9642d6e25
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:11:43Z

wip

commit dca634c9173aef0414e661f8b59719a2bb6a69cc
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:13:20Z

Fix obsolete usages

commit 387553edbd69708b0b18afbfe9c7dd877e0fd4f4
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:33:11Z

Fix usages in examples

commit 75d427ef3621d9e2da764221987a019ba68c0816
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:34:45Z

Rename internal method

commit 8ca35ba2a88ccf691af11eb8499ea59b33d13648
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:36:05Z

Fixing all usages

commit ce6e299a89a8e97236c95507f5e24783b03eb350
Author: Pavel Tupitsyn 
Date:   2017-12-18T12:37:41Z

Fixing tests

commit 0b0b02ae4e22408ee47d8d82879399600b6312f1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:00:54Z

Adding FieldNames tests

commit de38b92477b8c3b8f0addc1034904201d6ca2804
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:02:55Z

wip

commit 393d9f2460205a8688556c91163b195c24cedb0f
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:05:12Z

wip

commit dc9376e6c540c51a4e568f574c490de845e4dd10
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:12:41Z

wip

commit 48abd84fe6e19471ed707ec27992621dd5cc5b06
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:18:50Z

Adding field meta call

commit 951adccd0796fa6a955fbdd3356933c042f3b9cf
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:23:43Z

fieldNames done

commit 51c1898b561d73a3e9341c7166705ea06336ac9b
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:31:36Z

wip tests

commit 2b804743787b9e389e864758739516c4dc672ab1
Author: Pavel Tupitsyn 
Date:   2017-12-18T13:43:46Z

TestFieldNames done




---

[jira] [Created] (IGNITE-7233) Problems with classpath on Windows when IGNITE_HOME contains spaces

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-7233:
---

 Summary: Problems with classpath on Windows when IGNITE_HOME 
contains spaces
 Key: IGNITE-7233
 URL: https://issues.apache.org/jira/browse/IGNITE-7233
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
 Environment: Windows, cmd, batch files
Reporter: Ilya Kasnacheev


{code}
C:\releases> cd "apache-ignite-fabric-2.3.0 bin"
REM note the white space in folder name ^
C:\releases\apache-ignite-fabric-2.3.0 bin>set 
IGNITE_HOME="C:\releases\apache-ignite-fabric-2.3.0 bin"
C:\releases\apache-ignite-fabric-2.3.0 bin>bin\ignite.bat 
%IGNITE_HOME%\config\default.xml
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
Error: Could not find or load main class 
bin\libs\*;C:\releases\apache-ignite-fabric-2.3.0\*
bin\ignite.bat, WARN: Failed to resolve JMX host. JMX will be disabled.
class org.apache.ignite.IgniteException: Failed to create Ignite component 
(consider adding ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:966)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to create 
Ignite component (consider adding ignite-spring module to classpath) 
[component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
at 
org.apache.ignite.internal.IgniteComponentType.componentException(IgniteComponentType.java:320)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:296)
at 
org.apache.ignite.internal.IgniteComponentType.create(IgniteComponentType.java:207)
at 
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:671)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:874)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.ignite.internal.IgniteComponentType.create0(IgniteComponentType.java:282)
... 8 more
Failed to start grid: Failed to create Ignite component (consider adding 
ignite-spring module to classpath) [component=SPRING, 
cls=org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl]
Note! You may use 'USER_LIBS' environment variable to specify your classpath.
Press any key to continue . . .
{code}



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

[jira] [Created] (IGNITE-7232) .NET: remove localhost="127.0.0.1" from App.config to run cross-platform .NET examples with standalone node

[Irina Zaporozhtseva (JIRA)]

Irina Zaporozhtseva created IGNITE-7232:
---

 Summary: .NET: remove localhost="127.0.0.1" from App.config to run 
cross-platform .NET examples with standalone node
 Key: IGNITE-7232
 URL: https://issues.apache.org/jira/browse/IGNITE-7232
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.4
Reporter: Irina Zaporozhtseva
 Fix For: 2.4


need to remove localhost="127.0.0.1" from App.config to run cross-platform .NET 
examples with standalone node with default config



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

[GitHub] ignite pull request #1706: Ignite 4862

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3246: IGNITE-7174: Local MLP

[artemmalykh]

GitHub user artemmalykh opened a pull request:

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

IGNITE-7174: Local MLP



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

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

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

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


commit b8744c201860b2a5a79982445e27304b6b9c176a
Author: Artem Malykh 
Date:   2017-12-18T11:13:19Z

IGNITE-7174: WIP.

commit 16921b14b5e384e1e15ac91de2e231d52aab24fe
Author: Artem Malykh 
Date:   2017-12-18T11:14:59Z

IGNITE-7174: First version of local MLP.

commit e5ef258e31eff165a0cc754b6c907bfa5b390b44
Author: Artem Malykh 
Date:   2017-12-18T11:27:18Z

IGNITE-7174: Moved zipFolders from matrix api to utils.

commit 0275a58b5565eaff892def5767bba76939d8fb7e
Author: Artem Malykh 
Date:   2017-12-18T11:45:45Z

IGNITE-7174: Some refactorings.

commit 0be2300776ee064ad7d3f84deedd27e1a8f8583f
Author: Artem Malykh 
Date:   2017-12-18T11:52:07Z

IGNITE-7174: Added bias and weight getters.




---

[GitHub] ignite pull request #3113: Ignite 2.3.1.b1

[alamar]

Github user alamar closed the pull request at:

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


---

[jira] [Created] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7231:
-

 Summary: Cassandra-sessions-pool is running after Ignition.stop
 Key: IGNITE-7231
 URL: https://issues.apache.org/jira/browse/IGNITE-7231
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
Assignee: Mikhail Cherkasov
 Fix For: 2.4


Cassandra-sessions-pool is running after Ignition.stop.




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

[jira] [Created] (IGNITE-7230) Improve rebalance logging and metrics

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-7230:


 Summary: Improve rebalance logging and metrics
 Key: IGNITE-7230
 URL: https://issues.apache.org/jira/browse/IGNITE-7230
 Project: Ignite
  Issue Type: New Feature
Reporter: Anton Vinogradov


1) Node's log should contain messages that
- local node finished rebalancing from other nodes
- whole cluster finished rebalancing (awaitPartitionMaxExchange analogue)

2) We should be able to turn on same logging per cache group.
- local node finished cache group rebalancing 
- whole cluster finished cache group rebalancing

3) We should update MBean to show progress 
- % of partitions rebalanced locally 
- % of partitions rebalanced at cluster



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

Re: Future linux packages repositories

[Yakov Zhdanov]

Thanks for update, Petr. I like the solution. I think we can go ahead.

--Yakov

Re: Future linux packages repositories

[Petr Ivanov]

Hi, Yakov


 - Hadoop [1]
 - Cassandra [2] [3]
 And possibly more.

Also as far as I know - getting to Apache Dist Archive have to mean getting 
into mirrors as well (as mirrors synchronising with all or part of whole 
archive)


[1] http://apache.org/dist/hadoop/common/ 

[2] http://apache.org/dist/cassandra/redhat/ 

[3] http://cassandra.apache.org/download/ 



> On 18 Dec 2017, at 13:15, Yakov Zhdanov  wrote:
> 
> Petr, what debs and rpms can I currently download using apache.org/dist?
> Please provide examples. I also think you should mostly work with mirrors.
> Correct?
> 
> --Yakov

[jira] [Created] (IGNITE-7229) .NET: Rename ICache query methods to Query

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7229:
--

 Summary: .NET: Rename ICache query methods to Query
 Key: IGNITE-7229
 URL: https://issues.apache.org/jira/browse/IGNITE-7229
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


Currently some queries share a single method, while others use a different name.
Rename {{QueryFields}} and {{QueryContinuous}} to {{Query}} to have a more 
consistent API.
Keep old methods and mark them with {{[Obsolete]}}.

* {{ICacheClient}} uses same method name for all queries
* {{IgniteCache}} in Java uses same method name for all queries




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

Re: Future linux packages repositories

[Yakov Zhdanov]

Petr, what debs and rpms can I currently download using apache.org/dist?
Please provide examples. I also think you should mostly work with mirrors.
Correct?

--Yakov

[jira] [Created] (IGNITE-7228) .NET: SSL in ClientConnectorConfiguration

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7228:
--

 Summary: .NET: SSL in ClientConnectorConfiguration
 Key: IGNITE-7228
 URL: https://issues.apache.org/jira/browse/IGNITE-7228
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Add SSL configuration properties to {{ClientConnectorConfiguration}}.
We should support predefined {{SslContextFactory}} on .NET side.



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

[jira] [Created] (IGNITE-7227) Web console: Wrong count of user in filtered table

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7227:
-

 Summary: Web console: Wrong count of user in filtered table
 Key: IGNITE-7227
 URL: https://issues.apache.org/jira/browse/IGNITE-7227
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Open Admin panel
# Select some user
# Filter table.
In label with selected user count showed wrong count of showed rows in table.



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

[jira] [Created] (IGNITE-7226) Web console: Stub on empty user table

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7226:
-

 Summary: Web console: Stub on empty user table
 Key: IGNITE-7226
 URL: https://issues.apache.org/jira/browse/IGNITE-7226
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Open Admin panel
# Filter all data in table.
Table showed without data and any information message.



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

[jira] [Created] (IGNITE-7225) Web console: improve CSV export

[Ilya Borisov (JIRA)]

Ilya Borisov created IGNITE-7225:


 Summary: Web console: improve CSV export
 Key: IGNITE-7225
 URL: https://issues.apache.org/jira/browse/IGNITE-7225
 Project: Ignite
  Issue Type: Bug
  Components: wizards
 Environment: Browsers with ru and en locales.
Reporter: Ilya Borisov
Assignee: Ilya Borisov


*What to do:*
When exporting to CSV, rely on user's locale and number decimal separator 
symbol to determine what to use as a CSV separator.

*Motivation:*
During export to CSV, numbers are formatted depending on user's locale. In 
_non-import mode_, MS Excel requires comma as a decimal separator and semicolon 
as a CSV separator for _ru _locale and dot/comma respectively for _en_. After 
resolving this issue, CSV export will become more aware of user's environment.



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

[jira] [Created] (IGNITE-7224) Web console: Remove deprecated fields from configuration

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7224:
-

 Summary: Web console: Remove deprecated fields from configuration
 Key: IGNITE-7224
 URL: https://issues.apache.org/jira/browse/IGNITE-7224
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov


Ignite configuration:
# setMarshaller is deprecated since 2.1.
# setLateAffinityAssignment is always enabled since 2.1.




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

Future linux packages repositories

[Petr Ivanov]

Hi, all!


As you possibly noticed — an initiative was risen about packaging Apache Ignite 
into RPM and DEB package for purposes of project distribution through, 
including, 3rd party and official Linux repositories.
While the job of packages' introducing is still in progress, I think it is time 
also to rise a discussion about where should we place and how to distribute 
these packages.

At first sight the Apache Software Foundation Distribution Directory [1] suites 
these needs (for the first iteration of packages allocation) perfectly.

What do you think about starting an integration with it?


[1] http://www.apache.org/dist/ 

[jira] [Created] (IGNITE-7223) Web console: Double unsaved changes check on import of model

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-7223:
-

 Summary: Web console: Double unsaved changes check on import of 
model
 Key: IGNITE-7223
 URL: https://issues.apache.org/jira/browse/IGNITE-7223
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov


# Open model configuration page.
# Make some changes without saving.
# Open import from database dialog.
# Click "Ok" on dialog about unsaved changes.
Dialog about unsaved changes showed second time.
Data is reset to last saved state after first dialog.



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