[jira] [Updated] (IGNITE-7284) Introduce DEV_ONLY marker to IgniteLogger

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-7284:

Description: 
Need to add markers support to {{IgniteLogger}} and then introduce {{DEV_ONLY}} 
marker for warnings that can be suppressed in prod environments.

Problem and solution are discussed in more detail here: 
http://apache-ignite-developers.2346864.n4.nabble.com/Suppressing-quot-development-quot-warning-td25195.html

Make sure to update Loggers documentation explaining how the parameter works 
and what's it for:
https://apacheignite.readme.io/docs/logging

  was:
Need to add markers support to {{IgniteLogger}} and then introduce {{DEV_ONLY}} 
marker for warnings that can be suppressed in prod environments.

Problem and solution are discussed in more detail here: 
http://apache-ignite-developers.2346864.n4.nabble.com/Suppressing-quot-development-quot-warning-td25195.html


> Introduce DEV_ONLY marker to IgniteLogger
> -
>
> Key: IGNITE-7284
> URL: https://issues.apache.org/jira/browse/IGNITE-7284
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
> Fix For: 2.4
>
>
> Need to add markers support to {{IgniteLogger}} and then introduce 
> {{DEV_ONLY}} marker for warnings that can be suppressed in prod environments.
> Problem and solution are discussed in more detail here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Suppressing-quot-development-quot-warning-td25195.html
> Make sure to update Loggers documentation explaining how the parameter works 
> and what's it for:
> https://apacheignite.readme.io/docs/logging



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

[jira] [Created] (IGNITE-7285) Add default query timeout

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7285:
---

 Summary: Add default query timeout
 Key: IGNITE-7285
 URL: https://issues.apache.org/jira/browse/IGNITE-7285
 Project: Ignite
  Issue Type: Improvement
  Components: cache, sql
Affects Versions: 2.3
Reporter: Valentin Kulichenko
 Fix For: 2.4


Currently it's possible to provide timeout only on query level. It would be 
very useful to have default timeout value provided on cache startup. Let's add 
{{CacheConfiguration#defaultQueryTimeout}} configuration property.



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Description: 
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core: IGNITE-7281
* VS Code and Rider

  was:
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core: IGNITE-7281


> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Exceptions and delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * Service proxies are not supported because {{Remoting}} is not available on 
> .NET Core: IGNITE-7281
> * VS Code and Rider



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

[jira] [Created] (IGNITE-7284) Introduce DEV_ONLY marker to IgniteLogger

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7284:
---

 Summary: Introduce DEV_ONLY marker to IgniteLogger
 Key: IGNITE-7284
 URL: https://issues.apache.org/jira/browse/IGNITE-7284
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.3
Reporter: Valentin Kulichenko
 Fix For: 2.4


Need to add markers support to {{IgniteLogger}} and then introduce {{DEV_ONLY}} 
marker for warnings that can be suppressed in prod environments.

Problem and solution are discussed in more detail here: 
http://apache-ignite-developers.2346864.n4.nabble.com/Suppressing-quot-development-quot-warning-td25195.html



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Andrey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300410#comment-16300410
 ] 

Andrey Kuznetsov commented on IGNITE-6743:
--

[~ezhuravl], 'if' has been changed. As for turning Method vars into class 
fields, it's not useful change to me: currently, local vars are captured by 
cleaner closure, so they behave effectively in the same way as class members, 
but don't pollute class scope. Moreover, one of them is not needed for Java 9. 

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Commented] (IGNITE-7217) Add abilities to monitor custom thread pools

[Dmitry Karachentsev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300392#comment-16300392
 ] 

Dmitry Karachentsev commented on IGNITE-7217:
-

Also should be added MXBeans for missed pools, for example for svcExecSvc.

> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures a custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Evgenii Zhuravlev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300359#comment-16300359
 ] 

Evgenii Zhuravlev commented on IGNITE-6743:
---

[~andrey-kuznetsov], can we get rid of "!" in "if" block? I mean we can just 
swap these 2 blocks.

Also, I think we can save Methods to the class fields, what do you think?


> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Commented] (IGNITE-7197) Premature access to services() causes NullPointerException

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300310#comment-16300310
 ] 

ASF GitHub Bot commented on IGNITE-7197:


Github user alamar closed the pull request at:

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


> Premature access to services() causes NullPointerException
> --
>
> Key: IGNITE-7197
> URL: https://issues.apache.org/jira/browse/IGNITE-7197
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceEntries(GridServiceProcessor.java:1289)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceDescriptors(GridServiceProcessor.java:762)
> at 
> org.apache.ignite.internal.IgniteServicesImpl.serviceDescriptors(IgniteServicesImpl.java:203)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:60)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:44)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> {code}
> Happens with non-Visor jobs and callables, too!



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

[jira] [Commented] (IGNITE-7197) Premature access to services() causes NullPointerException

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300309#comment-16300309
 ] 

ASF GitHub Bot commented on IGNITE-7197:


Github user alamar closed the pull request at:

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


> Premature access to services() causes NullPointerException
> --
>
> Key: IGNITE-7197
> URL: https://issues.apache.org/jira/browse/IGNITE-7197
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 2.3
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>
> {code}
> Caused by: java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceEntries(GridServiceProcessor.java:1289)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.serviceDescriptors(GridServiceProcessor.java:762)
> at 
> org.apache.ignite.internal.IgniteServicesImpl.serviceDescriptors(IgniteServicesImpl.java:203)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:60)
> at 
> org.apache.ignite.internal.visor.service.VisorServiceTask$VisorServiceJob.run(VisorServiceTask.java:44)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> {code}
> Happens with non-Visor jobs and callables, too!



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

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[Ilya Kasnacheev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300298#comment-16300298
 ] 

Ilya Kasnacheev commented on IGNITE-7107:
-

I have rebuilt RPM with this spec and have a number of objections for the 
provided patch. Note that I have actually tested it with 2.3 binary 
distribution.
* I have noticed that both spec and DEVNOTES are made to use tabs alongside 
with spaces. I thought we are avoiding tabs? Please confirm that usage of tabs 
is desired in this case.
* Maybe it's my CentOS but initially build will fail with the following 
message, which I had to fix in spec
{code}
+ cd 'apache-ignite-*'
/var/tmp/rpm-tmp.KwOoyl: line 34: cd: apache-ignite-*: No such file or directory
{code}
* We absolutely should not inline configuration files (such as 
default-config.xml) into build scripts. We should just copy over 
default-config.xml from config/ to /etc, with dependencies if needed.
* We should discuss whether default discovery is applicable for packaged 
Ignite, but it should not list a random IP as it does now.
* I'm not sure PDS should be ON by default. Better provide it in examples but 
disable by default.

Less severe:
* I cannot comment on firewall rules validity, but firewall and service 
configurations should be stored in sources, as files, supplied with release 
(somewhere in packages/) and installed from there
* sqlline.sh fails to connect initially, needs to be specified 
jdbc:ignite:thin://localhost, then it works. I think that sqlline should become 
available as /usr/bin/apache-ignite-sqlline for example, to be in $PATH. And 
figure out how to connect by itself.
* ignitevisorcmd.sh becomes confused. first it scans /usr/share/apache-ignite 
for configs, then it fails to write to  /usr/share/apache-ignite/work. We 
should consider how it can be fixed (a symlink from 
/usr/share/apache-ignite/config to /etc/apache-ignite, perhaps, and work dir in 
/tmp?), and made available as /usr/bin/apache-ignite-visorcmd.

Minor things to consider:
* Not everything should go into /usr/share. classpath libs belong to /usr/lib.
* We are building from binary package and not from sources. If it is used by 
internal RPM building this is tolerable, but any distro or repository will want 
to build from source.
* spec contains version (2.4.0) - will be needed to be changed for every 
release. I'm not sure if it's possible to extract.
* Package description may be improved. service description lacks '-' in "In 
Memory".

> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



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

[jira] [Issue Comment Deleted] (IGNITE-6715) .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-6715:
---
Comment: was deleted

(was: WalCompactionEnabled is also missing)

> .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity
> 
>
> Key: IGNITE-6715
> URL: https://issues.apache.org/jira/browse/IGNITE-6715
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
> Fix For: 2.4
>
>
> Add {{DataStorageConfiguration.WalAutoArchiveAfterInactivity}} property.



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

[jira] [Commented] (IGNITE-6715) .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300216#comment-16300216
 ] 

Pavel Tupitsyn commented on IGNITE-6715:


WalCompactionEnabled is also missing

> .NET: DataStorageConfiguration.WalAutoArchiveAfterInactivity
> 
>
> Key: IGNITE-6715
> URL: https://issues.apache.org/jira/browse/IGNITE-6715
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, newbie
> Fix For: 2.4
>
>
> Add {{DataStorageConfiguration.WalAutoArchiveAfterInactivity}} property.



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

[jira] [Comment Edited] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300162#comment-16300162
 ] 

Pavel Tupitsyn edited comment on IGNITE-7279 at 12/21/17 4:04 PM:
--

All done, project compiles and tests run on Linux and macOS.
New TeamCity configuration created without NuGet dependencies.
Waiting for TC run.


was (Author: ptupitsyn):
All done, project compiles and tests run on Linux and macOS.
Waiting for TC run.

> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Andrey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300212#comment-16300212
 ] 

Andrey Kuznetsov commented on IGNITE-6743:
--

[~ezhuravl], thanks for your notes. I'll move the stuff to {{IgniteUtils}}. Can 
we complete curent discussion on Upsource?

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Commented] (IGNITE-6729) Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300196#comment-16300196
 ] 

ASF GitHub Bot commented on IGNITE-6729:


Github user andrey-kuznetsov closed the pull request at:

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


> Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)
> ---
>
> Key: IGNITE-6729
> URL: https://issues.apache.org/jira/browse/IGNITE-6729
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> This method use some internal API which is no longer accessible to cleanup 
> {{URLCLassLoader}} properly. The only usage of this method is in 
> {{GridUriDeploymentFileProcessor}} class.



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

[jira] [Commented] (IGNITE-6729) Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300167#comment-16300167
 ] 

Andrey Gura commented on IGNITE-6729:
-

LGTM. Merged to master branch. Thanks for contribution!

> Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)
> ---
>
> Key: IGNITE-6729
> URL: https://issues.apache.org/jira/browse/IGNITE-6729
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> This method use some internal API which is no longer accessible to cleanup 
> {{URLCLassLoader}} properly. The only usage of this method is in 
> {{GridUriDeploymentFileProcessor}} class.



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

[jira] [Assigned] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-7000:
--

Assignee: Pavel Tupitsyn

> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Exceptions and delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * Service proxies are not supported because {{Remoting}} is not available on 
> .NET Core: IGNITE-7281



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

[jira] [Commented] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300162#comment-16300162
 ] 

Pavel Tupitsyn commented on IGNITE-7279:


All done, project compiles and tests run on Linux and macOS.
Waiting for TC run.

> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Comment Edited] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300046#comment-16300046
 ] 

Pavel Tupitsyn edited comment on IGNITE-7279 at 12/21/17 3:22 PM:
--

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7279 .NET: Compile on Linux



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

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

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

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



was (Author: githubbot):
GitHub user ptupitsyn opened a pull request:

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

IGNITE-7279 .NET: Compile on Linux



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

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

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

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


commit 21fddfcf98fd00db081fd8448d7186c59a9311e3
Author: Pavel Tupitsyn 
Date:   2017-12-21T11:58:58Z

IGNITE-7279 Compile on Linux

commit f4eb4e7203bfa265b155cc52f86afd4fe6d51383
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:13:40Z

adding services test

commit fbaa141a641c4b12f5dd8fa8013cf9126c481b34
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:24:51Z

Fixing compilation (services)

commit 687be44bcbd3229918f0965d189aabc8fc22377a
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:38:20Z

wip

commit 88b503c4a14c30bf31ebdea1f0fc7de833cfc29c
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:41:06Z

wip

commit d5c9ab4835380004e296cb6978866b3baf10e2e6
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:55:35Z

Add LINQ project

commit aa9fa750a94d3948010e5e1978ea56e827d0c0d0
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:05:55Z

wip

commit b6fb0ec2c617463143221415a3d624105ce31179
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:10:52Z

Add dotnetcore solution file

commit 6d38376cd8ec0b611549da19a98c67b5fd3ed2d0
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:11:57Z

fix assembly names

commit f07daace1ead92e7c9ac86f5392b0f0462eeb9ab
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:14:35Z

Fix classpath in tests

commit a33e7733fd97a835f28974a60762a8f40470f271
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:32:52Z

update DEVNOTES

commit e29b72a4cde5c270c27c5552df9e94c18c02ddac
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:50:33Z

wip

commit 228cf3ee7b5353506cb6e08e3af37439c08b33a4
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:51:51Z

wip readme

commit 802c6763be2cc70a151773d13f37c98820cad134
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:52:03Z

wip

commit 973ec4fd444ad846a4ae78501500b2f5e096e6af
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:54:41Z

suppress warnings




> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Evgenii Zhuravlev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300117#comment-16300117
 ] 

Evgenii Zhuravlev commented on IGNITE-6743:
---

[~andrey-kuznetsov], I've added my thoughts on upsource, also, I have one more 
suggestion: let's move almost all new code from GridUnsafe to IgniteUtils. We 
need Unsafe here only for invoking a method on it, so, let's just add something 
like the invokeMethod method for GridUnsafe and just use it from IgniteUtils.

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Updated] (IGNITE-7283) .NET: Include all tests in DotNetCore test project

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7283:
---
Description: 
Currently we have a separate folder for .NET Core tests 
{{Apache.Ignite.Core.Tests.DotNetCore}}.
Ideally we should get rid of it and place 
{{Apache.Ignite.Core.Tests.DotNetCore.csproj}} in the 
{{Apache.Ignite.Core.Tests}} folder so that all tests are included.

This will require a lot of {{#if !NETCOREAPP2_0}}, but we'll explicitly see 
which tests are cross-platform.

> .NET: Include all tests in DotNetCore test project
> --
>
> Key: IGNITE-7283
> URL: https://issues.apache.org/jira/browse/IGNITE-7283
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Currently we have a separate folder for .NET Core tests 
> {{Apache.Ignite.Core.Tests.DotNetCore}}.
> Ideally we should get rid of it and place 
> {{Apache.Ignite.Core.Tests.DotNetCore.csproj}} in the 
> {{Apache.Ignite.Core.Tests}} folder so that all tests are included.
> This will require a lot of {{#if !NETCOREAPP2_0}}, but we'll explicitly see 
> which tests are cross-platform.



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

[jira] [Created] (IGNITE-7283) .NET: Include all tests in DotNetCore test project

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7283:
--

 Summary: .NET: Include all tests in DotNetCore test project
 Key: IGNITE-7283
 URL: https://issues.apache.org/jira/browse/IGNITE-7283
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn






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

[jira] [Commented] (IGNITE-7279) .NET: Compile on Linux

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300046#comment-16300046
 ] 

ASF GitHub Bot commented on IGNITE-7279:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-7279 .NET: Compile on Linux



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

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

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

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


commit 21fddfcf98fd00db081fd8448d7186c59a9311e3
Author: Pavel Tupitsyn 
Date:   2017-12-21T11:58:58Z

IGNITE-7279 Compile on Linux

commit f4eb4e7203bfa265b155cc52f86afd4fe6d51383
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:13:40Z

adding services test

commit fbaa141a641c4b12f5dd8fa8013cf9126c481b34
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:24:51Z

Fixing compilation (services)

commit 687be44bcbd3229918f0965d189aabc8fc22377a
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:38:20Z

wip

commit 88b503c4a14c30bf31ebdea1f0fc7de833cfc29c
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:41:06Z

wip

commit d5c9ab4835380004e296cb6978866b3baf10e2e6
Author: Pavel Tupitsyn 
Date:   2017-12-21T12:55:35Z

Add LINQ project

commit aa9fa750a94d3948010e5e1978ea56e827d0c0d0
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:05:55Z

wip

commit b6fb0ec2c617463143221415a3d624105ce31179
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:10:52Z

Add dotnetcore solution file

commit 6d38376cd8ec0b611549da19a98c67b5fd3ed2d0
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:11:57Z

fix assembly names

commit f07daace1ead92e7c9ac86f5392b0f0462eeb9ab
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:14:35Z

Fix classpath in tests

commit a33e7733fd97a835f28974a60762a8f40470f271
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:32:52Z

update DEVNOTES

commit e29b72a4cde5c270c27c5552df9e94c18c02ddac
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:50:33Z

wip

commit 228cf3ee7b5353506cb6e08e3af37439c08b33a4
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:51:51Z

wip readme

commit 802c6763be2cc70a151773d13f37c98820cad134
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:52:03Z

wip

commit 973ec4fd444ad846a4ae78501500b2f5e096e6af
Author: Pavel Tupitsyn 
Date:   2017-12-21T13:54:41Z

suppress warnings




> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Assigned] (IGNITE-5217) Gradient descent for OLS lin reg

[Yury Babak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Babak reassigned IGNITE-5217:
--

Assignee: Yury Babak

> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



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

[jira] [Commented] (IGNITE-5217) Gradient descent

[Yury Babak (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1637#comment-1637
 ] 

Yury Babak commented on IGNITE-5217:


Currently we speak only about new trainer implementation for OLS lin reg.

> Gradient descent
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



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

[jira] [Updated] (IGNITE-5217) Gradient descent for OLS lin reg

[Yury Babak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yury Babak updated IGNITE-5217:
---
Summary: Gradient descent for OLS lin reg  (was: Gradient descent)

> Gradient descent for OLS lin reg
> 
>
> Key: IGNITE-5217
> URL: https://issues.apache.org/jira/browse/IGNITE-5217
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>
> We should implement Gradient Descent for Ignite ML. Current we have only 
> normal equation for linear regression.



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

[jira] [Updated] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7279:
---
Description: 
Make it possible to develop Ignite.NET on Linux.
* Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
* Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
-> {{dotnet test}})
* Update DEVNOTES

  was:
Make it possible to develop Ignite.NET on Linux.
* Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
* Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
-> {{dotnet test}})


> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})
> * Update DEVNOTES



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

[jira] [Commented] (IGNITE-6730) Java 9: fix project build procedure

[Andrey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1624#comment-1624
 ] 

Andrey Kuznetsov commented on IGNITE-6730:
--

I'd like to reject this as duplicate of [1]. [~vozerov], any objections?

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

> Java 9: fix project build procedure
> ---
>
> Key: IGNITE-6730
> URL: https://issues.apache.org/jira/browse/IGNITE-6730
> Project: Ignite
>  Issue Type: Task
>  Components: build
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> 1) In most modules compiler level is set to 1.7 explicitly. Should we fix it 
> somehow? See commit {{a450452e}} for reference.
> 2) Most probably we will have separate code flows for Java 7/8 and Java 9. 
> Need to understand how to organize this. Most probably we will have two 
> pluggable modules producing separate JARs, which will be linked in runtime. 
> Any other ideas?



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

[jira] [Commented] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299964#comment-16299964
 ] 

Pavel Tupitsyn commented on IGNITE-7279:


We could target {{netstandard2.0}}, but it does not support {{DynamicMethod}}, 
even though {{netcoreapp2.0}} supports it.

So for development purposes {{netcoreapp2.0}} target will do, we are not going 
to release binaries build on Linux.

> .NET: Compile on Linux
> --
>
> Key: IGNITE-7279
> URL: https://issues.apache.org/jira/browse/IGNITE-7279
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, xplat
>
> Make it possible to develop Ignite.NET on Linux.
> * Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
> * Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
> -> {{dotnet test}})



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

[jira] [Commented] (IGNITE-6734) Java 9: do not use sun.misc.BASE64Encoder

[Andrey Kuznetsov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299945#comment-16299945
 ] 

Andrey Kuznetsov commented on IGNITE-6734:
--

This change is ready, just waits for changing to Java 8 project-wide.

> Java 9: do not use sun.misc.BASE64Encoder
> -
>
> Key: IGNITE-6734
> URL: https://issues.apache.org/jira/browse/IGNITE-6734
> Project: Ignite
>  Issue Type: Task
>  Components: general, rest
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> For some reason we use {{sun.misc.BASE64Encoder}} in several places:
> 1) {{jiraslurp.groovy}}
> 2) Several REST-related classes in {{ignite-clients}} module.
> Need to remove this usages and use {{Base64}}. Note that this class is 
> available since Java 8. Hopefully we will move to Java 8 in the same release. 
> Otherwise we will have to apply some reflection-based hacks, I think.



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

[jira] [Created] (IGNITE-7282) .NET: Thin client: Failover

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7282:
--

 Summary: .NET: Thin client: Failover
 Key: IGNITE-7282
 URL: https://issues.apache.org/jira/browse/IGNITE-7282
 Project: Ignite
  Issue Type: Improvement
  Components: platforms, thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn


Currently user has to manually connect to some specific Ignite server.
Implement some kind of automatic failover where Thin Client knows about 
multiple nodes.



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

[jira] [Created] (IGNITE-7281) .NET: Services do not work on .NET Core

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7281:
--

 Summary: .NET: Services do not work on .NET Core
 Key: IGNITE-7281
 URL: https://issues.apache.org/jira/browse/IGNITE-7281
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn


We rely on {{System.Runtime.Remoting.Proxies.RealProxy}} for dynamic proxy 
generation. However, remoting is not supported on .NET Core.

Investigate whether we can get id of RealProxy and generate runtime proxies 
manually. Basically, we need to emit an interface implementation where every 
method just delegates to our code.



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Description: 
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core: IGNITE-7281

  was:
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core


> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Exceptions and delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * Service proxies are not supported because {{Remoting}} is not available on 
> .NET Core: IGNITE-7281



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

[jira] [Updated] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-7000:
---
Description: 
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37
* Service proxies are not supported because {{Remoting}} is not available on 
.NET Core

  was:
Create a documentation page about running Ignite.NET under .NET Core and/or 
Linux. Things to mention:
* Exceptions and delegates can't be serialized under .NET Core: 
https://github.com/dotnet/corefx/issues/24424
* Build warning - suppress {{NU1701}} with 
{{NU1701}}
* Java home, dll paths, etc
* Publish and deploy (copy libs folder to {{dotnet publish}} dir)
* macOs: document {{No Java runtime present, requesting install.}} issue 
https://bugs.openjdk.java.net/browse/JDK-7131356, 
https://github.com/s-u/rJava/issues/37


> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Exceptions and delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * Service proxies are not supported because {{Remoting}} is not available on 
> .NET Core



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

[jira] [Commented] (IGNITE-6339) WAL: Avoid closed by interruption exception when user thread is interrupted

[Andrey Gura (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299920#comment-16299920
 ] 

Andrey Gura commented on IGNITE-6339:
-

Implementation is completed. {{MappedByteBuffer}} implementation is default now 
and it can be switched to single writer thread using JVM argument: 
{{-DIGNITE_WAL_MMAP=false}}.

All file operations are noninterruptible for {{MappedByteBuffer}} or performs 
special thread in case of single writer thread.

TC looks good. Please review.

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

> WAL: Avoid closed by interruption exception when user thread is interrupted
> ---
>
> Key: IGNITE-6339
> URL: https://issues.apache.org/jira/browse/IGNITE-6339
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Blocker
>  Labels: important
> Fix For: 2.4
>
>
> We should have a separate writer thread for WAL that will write completed 
> serialized chunks of data. This will allow us avoid closed by interruption 
> exception when user thread is interrupted.



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

[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7280:

Description: 
The following cases must be handled:
1) Single update stmt in TX
2) Multiple update stmts in TX
3) Changes to multiple caches in TX
4) Mix of both selects and updates (e.g. get data from select and then build 
updates based on it)
5) Different operation types - INSERT, UPDATE, MERGE (take in count various DML 
optimizations to ensure that as much code paths are covered as possible)
6) Batch updates
7) Joins (both co-located and distributed)
8) Different cache modes - PARTITIONED, REPLICATED
9) Different backup counts
10) Communication with client node vs communication with server node
11) Both implicit and explicit transactions

  was:
The following cases must be handled:
1) Single update stmt in TX
2) Multiple update stmts in TX
3) Changes to multiple caches in TX
4) Mix of both selects and updates (e.g. get data from select and then build 
updates based on it)
5) Different operation types - INSERT, UPDATE, MERGE (take in count various DML 
optimizations to ensure that as much code paths are covered as possible)
6) Batch updates
7) Joins (both co-located and distributed)
8) Different cache modes - PARTITIONED, REPLICATED
9) Different backup counts
10) Communication with client node vs communcation with server node


> SQL TX: improve JDBC test coverage
> --
>
> Key: IGNITE-7280
> URL: https://issues.apache.org/jira/browse/IGNITE-7280
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.5
>
>
> The following cases must be handled:
> 1) Single update stmt in TX
> 2) Multiple update stmts in TX
> 3) Changes to multiple caches in TX
> 4) Mix of both selects and updates (e.g. get data from select and then build 
> updates based on it)
> 5) Different operation types - INSERT, UPDATE, MERGE (take in count various 
> DML optimizations to ensure that as much code paths are covered as possible)
> 6) Batch updates
> 7) Joins (both co-located and distributed)
> 8) Different cache modes - PARTITIONED, REPLICATED
> 9) Different backup counts
> 10) Communication with client node vs communication with server node
> 11) Both implicit and explicit transactions



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

[jira] [Created] (IGNITE-7280) SQL TX: improve JDBC test coverage

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7280:
---

 Summary: SQL TX: improve JDBC test coverage
 Key: IGNITE-7280
 URL: https://issues.apache.org/jira/browse/IGNITE-7280
 Project: Ignite
  Issue Type: Bug
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.5


The following cases must be handled:
1) Single update stmt in TX
2) Multiple update stmts in TX
3) Changes to multiple caches in TX
4) Mix of both selects and updates (e.g. get data from select and then build 
updates based on it)
5) Different operation types - INSERT, UPDATE, MERGE (take in count various DML 
optimizations to ensure that as much code paths are covered as possible)
6) Batch updates
7) Joins (both co-located and distributed)
8) Different cache modes - PARTITIONED, REPLICATED
9) Different backup counts
10) Communication with client node vs communcation with server node



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

[jira] [Commented] (IGNITE-6732) Java 9: Hadoop module should not start on Java 9

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299917#comment-16299917
 ] 

ASF GitHub Bot commented on IGNITE-6732:


GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6732: Preventing Hadoop module from start on Java >= 9.



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

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

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

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


commit 03e5f470866b252c17984d2f408ee7dcea43f498
Author: Andrey Kuznetsov 
Date:   2017-12-21T12:12:57Z

IGNITE-6732: Preventing Hadoop module from start on Java >= 9.




> Java 9: Hadoop module should not start on Java 9
> 
>
> Key: IGNITE-6732
> URL: https://issues.apache.org/jira/browse/IGNITE-6732
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> Hadoop module heavily relies on the fact that application class loader is 
> {{URLClassLoader}}. It is used to inspect class path and hack it in various 
> ways. But in Java 9 another class loader type is used. 
> Looks like there is no simple solution at the moment. Let's check for Java 
> version during startup and throw an exception if it Java 9 or later.



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

[jira] [Commented] (IGNITE-7109) .NET: Thin client: Async cache operations

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299903#comment-16299903
 ] 

Pavel Tupitsyn commented on IGNITE-7109:


Merged from master, compilation fixed. [~vozerov] waiting for review.

> .NET: Thin client: Async cache operations
> -
>
> Key: IGNITE-7109
> URL: https://issues.apache.org/jira/browse/IGNITE-7109
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Add async operations to {{ICacheClient}}.
> Thin client suppots asynchrony with requestId mechanism. Make sure it works 
> with .NET.



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

[jira] [Comment Edited] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299883#comment-16299883
 ] 

Vladimir Ozerov edited comment on IGNITE-7266 at 12/21/17 11:24 AM:


Root cause is identified: incorrect merge of IGNITE-6663 - it pass filter 
incorrectly, so the same PK could be returned more than once if there are 
backups. 

See relevant TODO in {{H2TreeIndex.find}} method.


was (Author: vozerov):
Root cause is identified: incorrect merge of IGNITE-6663 - it pass filter 
incorrectly, so the same PK could be returned more than once if there are 
backups.

> SQL TX: Joins return duplicated result when MVCC is disabled
> 
>
> Key: IGNITE-7266
> URL: https://issues.apache.org/jira/browse/IGNITE-7266
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
> Fix For: 2.5
>
>
> Affected tests:
> {{IgniteCacheJoinQueryWithAffinityKeyTest}}
> {{IgniteCacheCrossCacheJoinRandomTest}}
> All tests failed for the same reason: {{expected=X, actual=2*X}}. Looks like 
> we return too much results in some cases.



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

[jira] [Assigned] (IGNITE-3935) ClassLoaders are not switched during object deserialization

[Stanilovsky Evgeny (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stanilovsky Evgeny reassigned IGNITE-3935:
--

Assignee: Alexey Goncharuk

> ClassLoaders are not switched during object deserialization
> ---
>
> Key: IGNITE-3935
> URL: https://issues.apache.org/jira/browse/IGNITE-3935
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.6
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>
> If an object is being deserialized with ClassLoader A then this ClassLoader A 
> will be used for the deserialization of the whole object's state, i.e., 
> including all its fields that can be custom objects loaded by ClassLoader B. 
> In a basic scenario we can have an object of some Ignite class that is 
> presented in the classpath. That Ignite class may enclose an object that is 
> loaded by peer-class-loading class loader. The deserialization will fail 
> because Ignite won't switch to the peer-class-loading loader when it's needed.
> To reproduce the issue do the following:
> 1. Start a remote ignite node using {{./ignite.sh 
> ../examples/config/example-ignite.xml}}
> 2. Run the code below
> {code}
> public class StreamingExample {`
> public static class StreamingExampleCacheEntryProcessor implements 
> CacheEntryProcessor {
> @Override
> public Object process(MutableEntry e, Object... arg) throws 
> EntryProcessorException {
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(StreamTransformer.from(new 
> StreamingExampleCacheEntryProcessor()));
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> {code}
> However if to modify this code to the following everything will work fine 
> {code}
> public class StreamingExample {
> public static class StreamingExampleCacheEntryProcessor extends 
> StreamTransformer {
> @Override
> public Object process(MutableEntry e, Object... arg) 
> throws EntryProcessorException {
> System.out.println("Executed!");
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, 
> IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(new StreamingExampleCacheEntryProcessor());
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299883#comment-16299883
 ] 

Vladimir Ozerov commented on IGNITE-7266:
-

Root cause is identified: incorrect merge of IGNITE-6663 - it pass filter 
incorrectly, so the same PK could be returned more than once if there are 
backups.

> SQL TX: Joins return duplicated result when MVCC is disabled
> 
>
> Key: IGNITE-7266
> URL: https://issues.apache.org/jira/browse/IGNITE-7266
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
> Fix For: 2.5
>
>
> Affected tests:
> {{IgniteCacheJoinQueryWithAffinityKeyTest}}
> {{IgniteCacheCrossCacheJoinRandomTest}}
> All tests failed for the same reason: {{expected=X, actual=2*X}}. Looks like 
> we return too much results in some cases.



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

[jira] [Commented] (IGNITE-7217) Add abilities to monitor custom thread pools

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299881#comment-16299881
 ] 

ASF GitHub Bot commented on IGNITE-7217:


GitHub user slukyano opened a pull request:

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

IGNITE-7217: Add abilities to monitor custom thread pools

Added logging and MX beans for custom executors (plus simple tests for 
availability of other MX beans).

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

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

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

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


commit 127be326b76916d6afeb70d4c35a001d1e18a7a6
Author: Stanislav Lukyanov 
Date:   2017-12-20T15:38:25Z

IGNITE-7217: added logging for custom thread pools

commit a21731651994e7267e328a3dcd8be2830ec1c77c
Author: Stanislav Lukyanov 
Date:   2017-12-21T10:44:34Z

IGNITE-7217: added JMX beans for custom executors




> Add abilities to monitor custom thread pools
> 
>
> Key: IGNITE-7217
> URL: https://issues.apache.org/jira/browse/IGNITE-7217
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
> Fix For: 2.4
>
>
> We have a periodic metrics logger that prints out different stats including 
> the ones for public and system thread pools:
> {noformat}
> ^-- Public thread pool [active=0, idle=0, qSize=0]
> ^-- System thread pool [active=0, idle=8, qSize=0]
> {noformat}
> However, if user configures a custom thread pools via 
> {{IgniteConfiguration#setExecutorConfiguration}}, stats for these thread 
> pools are not added. We also do not register MBeans for these pools.



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

[jira] [Commented] (IGNITE-6951) .NET: Support pointer serialization

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299875#comment-16299875
 ] 

ASF GitHub Bot commented on IGNITE-6951:


Github user asfgit closed the pull request at:

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


> .NET: Support pointer serialization
> ---
>
> Key: IGNITE-6951
> URL: https://issues.apache.org/jira/browse/IGNITE-6951
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Serializing pointers does not make sense and we already throw on {{IntPtr}} 
> fields.
> However, .NET serializer ({{BinaryFormatter}}) supports both {{IntPtr}} and 
> {{void*}}-style pointers.
> Our goal is to replace standard serializer and allow seamless transition, so 
> we should do the same.



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

[jira] [Commented] (IGNITE-6951) .NET: Support pointer serialization

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299874#comment-16299874
 ] 

Pavel Tupitsyn commented on IGNITE-6951:


Merged to master: {{cc5fff5315027eadec5497065a272e14a619770c}}.

> .NET: Support pointer serialization
> ---
>
> Key: IGNITE-6951
> URL: https://issues.apache.org/jira/browse/IGNITE-6951
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Serializing pointers does not make sense and we already throw on {{IntPtr}} 
> fields.
> However, .NET serializer ({{BinaryFormatter}}) supports both {{IntPtr}} and 
> {{void*}}-style pointers.
> Our goal is to replace standard serializer and allow seamless transition, so 
> we should do the same.



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

[jira] [Resolved] (IGNITE-6951) .NET: Support pointer serialization

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn resolved IGNITE-6951.

Resolution: Fixed

> .NET: Support pointer serialization
> ---
>
> Key: IGNITE-6951
> URL: https://issues.apache.org/jira/browse/IGNITE-6951
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Serializing pointers does not make sense and we already throw on {{IntPtr}} 
> fields.
> However, .NET serializer ({{BinaryFormatter}}) supports both {{IntPtr}} and 
> {{void*}}-style pointers.
> Our goal is to replace standard serializer and allow seamless transition, so 
> we should do the same.



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

[jira] [Assigned] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-7266:
---

Assignee: Igor Seliverstov  (was: Vladimir Ozerov)

> SQL TX: Joins return duplicated result when MVCC is disabled
> 
>
> Key: IGNITE-7266
> URL: https://issues.apache.org/jira/browse/IGNITE-7266
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
> Fix For: 2.5
>
>
> Affected tests:
> {{IgniteCacheJoinQueryWithAffinityKeyTest}}
> {{IgniteCacheCrossCacheJoinRandomTest}}
> All tests failed for the same reason: {{expected=X, actual=2*X}}. Looks like 
> we return too much results in some cases.



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

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov reassigned IGNITE-6976:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good. Merged to master.
Please retest.

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




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

[jira] [Created] (IGNITE-7279) .NET: Compile on Linux

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7279:
--

 Summary: .NET: Compile on Linux
 Key: IGNITE-7279
 URL: https://issues.apache.org/jira/browse/IGNITE-7279
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


Make it possible to develop Ignite.NET on Linux.
* Provide separate .NET Core csproj files for {{Core}} and {{Linq}} projects
* Make sure we can compile and run tests from scratch on Linux ({{git clone}} 
-> {{dotnet test}})



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

[jira] [Updated] (IGNITE-7278) Node failed to recover partition from WAL on unstable topology.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-7278:
-
Attachment: page_corrupted2.tar.gz

> Node failed to recover partition from WAL on unstable topology.
> ---
>
> Key: IGNITE-7278
> URL: https://issues.apache.org/jira/browse/IGNITE-7278
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: page_corrupted2.tar.gz
>
>
> The use case is:
> -Grid with partitioned cache with 2 backups (or replicated)
> -Node-1 is killed in the middle of checkpoint and started again.
> -Node-1 detects unfinished checkpoint and tries to recover it.
> -At this point Node-2 is killed while node-1 recovering is in progress.
> -Node-1 fails with AssertionError.
> PFA logs, parsed WAL, reproducer.
> Can be reproduced with IgnitePdsContinuousRestartTest with minor changes,
> we have to have 2 nodes flapping and kill nodes ungracefully.



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

[jira] [Assigned] (IGNITE-7278) Node failed to recover partition from WAL on unstable topology.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov reassigned IGNITE-7278:


Assignee: Andrew Mashenkov

> Node failed to recover partition from WAL on unstable topology.
> ---
>
> Key: IGNITE-7278
> URL: https://issues.apache.org/jira/browse/IGNITE-7278
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: page_corrupted2.tar.gz
>
>
> The use case is:
> -Grid with partitioned cache with 2 backups (or replicated)
> -Node-1 is killed in the middle of checkpoint and started again.
> -Node-1 detects unfinished checkpoint and tries to recover it.
> -At this point Node-2 is killed while node-1 recovering is in progress.
> -Node-1 fails with AssertionError.
> PFA logs, parsed WAL, reproducer.
> Can be reproduced with IgnitePdsContinuousRestartTest with minor changes,
> we have to have 2 nodes flapping and kill nodes ungracefully.



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

[jira] [Created] (IGNITE-7278) Node failed to recover partition from WAL on unstable topology.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-7278:


 Summary: Node failed to recover partition from WAL on unstable 
topology.
 Key: IGNITE-7278
 URL: https://issues.apache.org/jira/browse/IGNITE-7278
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Andrew Mashenkov
 Fix For: 2.4


The use case is:
-Grid with partitioned cache with 2 backups (or replicated)
-Node-1 is killed in the middle of checkpoint and started again.
-Node-1 detects unfinished checkpoint and tries to recover it.
-At this point Node-2 is killed while node-1 recovering is in progress.
-Node-1 fails with AssertionError.

PFA logs, parsed WAL, reproducer.

Can be reproduced with IgnitePdsContinuousRestartTest with minor changes,
we have to have 2 nodes flapping and kill nodes ungracefully.



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

[jira] [Updated] (IGNITE-7277) JDBC thin driver may list table name twice.

[Vyacheslav Koptilin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-7277:

Description: 
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | PERSON  
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}

Initial discussion on SO: 
https://stackoverflow.com/questions/47869429/duplicate-table-show-using-table-in-sqlline-sh

  was:
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | PERSON  
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}


> JDBC thin driver may list table name twice.
> ---
>
> Key: IGNITE-7277
> URL: https://issues.apache.org/jira/browse/IGNITE-7277
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
>Reporter: Vyacheslav Koptilin
>Assignee: Taras Ledkov
>
> JDBC thin driver duplicates table name in case of using 
> {{CacheConfiguration.setIndexedTypes()}}
> {code}
> CacheConfiguration cfg = new 
> CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
> cfg.setIndexedTypes(Long.class, Person.class);
> IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
> {code}
> {code:title=sqlline output|borderStyle=solid}
> +++++
> |   TABLE_CAT|  TABLE_SCHEM   |   
> TABLE_NAME   |   TABLE_TYPE   |
> +++++
> || PUBLIC | PERSON
>  | TABLE  |
> || PUBLIC | PERSON
>  | TABLE  |
> +++++
> {code}
> On the other hand, the following approach to create a table works as expected
> {code}
> cache.query(new SqlFieldsQuery(
> "CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) 

[jira] [Updated] (IGNITE-7277) JDBC thin driver may list table name twice.

[Vyacheslav Koptilin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-7277:

Description: 
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | PERSON  
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}

  was:
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}


> JDBC thin driver may list table name twice.
> ---
>
> Key: IGNITE-7277
> URL: https://issues.apache.org/jira/browse/IGNITE-7277
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
>Reporter: Vyacheslav Koptilin
>Assignee: Taras Ledkov
>
> JDBC thin driver duplicates table name in case of using 
> {{CacheConfiguration.setIndexedTypes()}}
> {code}
> CacheConfiguration cfg = new 
> CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
> cfg.setIndexedTypes(Long.class, Person.class);
> IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
> {code}
> {code:title=sqlline output|borderStyle=solid}
> +++++
> |   TABLE_CAT|  TABLE_SCHEM   |   
> TABLE_NAME   |   TABLE_TYPE   |
> +++++
> || PUBLIC | PERSON
>  | TABLE  |
> || PUBLIC | PERSON
>  | TABLE  |
> +++++
> {code}
> On the other hand, the following approach to create a table works as expected
> {code}
> cache.query(new SqlFieldsQuery(
> "CREATE TABLE city (id LONG PRIMARY 

[jira] [Updated] (IGNITE-7277) JDBC thin driver may list table name twice.

[Vyacheslav Koptilin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-7277:

Description: 
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
|| PUBLIC | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}

  was:
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}


> JDBC thin driver may list table name twice.
> ---
>
> Key: IGNITE-7277
> URL: https://issues.apache.org/jira/browse/IGNITE-7277
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
>Reporter: Vyacheslav Koptilin
>Assignee: Taras Ledkov
>
> JDBC thin driver duplicates table name in case of using 
> {{CacheConfiguration.setIndexedTypes()}}
> {code}
> CacheConfiguration cfg = new 
> CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
> cfg.setIndexedTypes(Long.class, Person.class);
> IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
> {code}
> {code:title=sqlline output|borderStyle=solid}
> +++++
> |   TABLE_CAT|  TABLE_SCHEM   |   
> TABLE_NAME   |   TABLE_TYPE   |
> +++++
> || PUBLIC | CITY  
>  | TABLE  |
> || PUBLIC | PERSON
>  | TABLE  |
> || PUBLIC | PERSON
>  | TABLE  |
> 

[jira] [Updated] (IGNITE-7277) JDBC thin driver may list table name twice.

[Vyacheslav Koptilin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Koptilin updated IGNITE-7277:

Description: 
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{code}
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
{code}

{code:title=sqlline output|borderStyle=solid}
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
+++++
{code}

On the other hand, the following approach to create a table works as expected
{code}
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
{code}

  was:
JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{{
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
}}

{{sqlline}} output
{{
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
+++++
}}

On the other hand, the following approach to create a table works as expected
{{
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
}}


> JDBC thin driver may list table name twice.
> ---
>
> Key: IGNITE-7277
> URL: https://issues.apache.org/jira/browse/IGNITE-7277
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, sql
>Affects Versions: 2.3
>Reporter: Vyacheslav Koptilin
>Assignee: Taras Ledkov
>
> JDBC thin driver duplicates table name in case of using 
> {{CacheConfiguration.setIndexedTypes()}}
> {code}
> CacheConfiguration cfg = new 
> CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
> cfg.setIndexedTypes(Long.class, Person.class);
> IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
> {code}
> {code:title=sqlline output|borderStyle=solid}
> +++++
> |   TABLE_CAT|  TABLE_SCHEM   |   
> TABLE_NAME   |   TABLE_TYPE   |
> +++++
> || PUBLIC | CITY  
>  | TABLE  |
> || CACHE_NAME | PERSON
>  | TABLE  |
> || CACHE_NAME | PERSON
>  | TABLE  |
> 

[jira] [Created] (IGNITE-7277) JDBC thin driver may list table name twice.

[Vyacheslav Koptilin (JIRA)]

Vyacheslav Koptilin created IGNITE-7277:
---

 Summary: JDBC thin driver may list table name twice.
 Key: IGNITE-7277
 URL: https://issues.apache.org/jira/browse/IGNITE-7277
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, sql
Affects Versions: 2.3
Reporter: Vyacheslav Koptilin
Assignee: Taras Ledkov


JDBC thin driver duplicates table name in case of using 
{{CacheConfiguration.setIndexedTypes()}}

{{
CacheConfiguration cfg = new 
CacheConfiguration<>("CACHE_NAME").setSqlSchema("PUBLIC");
cfg.setIndexedTypes(Long.class, Person.class);
IgniteCache cachePerson = ignite.getOrCreateCache(cfg);
}}

{{sqlline}} output
{{
+++++
|   TABLE_CAT|  TABLE_SCHEM   |   
TABLE_NAME   |   TABLE_TYPE   |
+++++
|| PUBLIC | CITY
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
|| CACHE_NAME | PERSON  
   | TABLE  |
+++++
}}

On the other hand, the following approach to create a table works as expected
{{
cache.query(new SqlFieldsQuery(
"CREATE TABLE city (id LONG PRIMARY KEY, name VARCHAR) WITH 
\"template=partitioned\""));
}}



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

[jira] [Commented] (IGNITE-6729) Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)

[Evgenii Zhuravlev (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299845#comment-16299845
 ] 

Evgenii Zhuravlev commented on IGNITE-6729:
---

[~andrey-kuznetsov], Great! Now it definitely looks better.

> Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)
> ---
>
> Key: IGNITE-6729
> URL: https://issues.apache.org/jira/browse/IGNITE-6729
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> This method use some internal API which is no longer accessible to cleanup 
> {{URLCLassLoader}} properly. The only usage of this method is in 
> {{GridUriDeploymentFileProcessor}} class.



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

[jira] [Commented] (IGNITE-6615) .NET: Thin client: XML configuration

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299837#comment-16299837
 ] 

ASF GitHub Bot commented on IGNITE-6615:


Github user asfgit closed the pull request at:

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


> .NET: Thin client: XML configuration
> 
>
> Key: IGNITE-6615
> URL: https://issues.apache.org/jira/browse/IGNITE-6615
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
>
> Provide a way to configure {{IgniteClientConfiguration}} in XML, similar to 
> {{IgniteConfiguration}}.



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

[jira] [Commented] (IGNITE-6615) .NET: Thin client: XML configuration

[Pavel Tupitsyn (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299832#comment-16299832
 ] 

Pavel Tupitsyn commented on IGNITE-6615:


Merged to master: {{400cbf3f41ca748944dd69445f6ef45f0bcfb356}}.

> .NET: Thin client: XML configuration
> 
>
> Key: IGNITE-6615
> URL: https://issues.apache.org/jira/browse/IGNITE-6615
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
>
> Provide a way to configure {{IgniteClientConfiguration}} in XML, similar to 
> {{IgniteConfiguration}}.



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

[jira] [Resolved] (IGNITE-6615) .NET: Thin client: XML configuration

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn resolved IGNITE-6615.

Resolution: Fixed

> .NET: Thin client: XML configuration
> 
>
> Key: IGNITE-6615
> URL: https://issues.apache.org/jira/browse/IGNITE-6615
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
>
> Provide a way to configure {{IgniteClientConfiguration}} in XML, similar to 
> {{IgniteConfiguration}}.



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

[jira] [Created] (IGNITE-7276) .NET: Enable/disable cache statistics in runtime

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7276:
--

 Summary: .NET: Enable/disable cache statistics in runtime
 Key: IGNITE-7276
 URL: https://issues.apache.org/jira/browse/IGNITE-7276
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 2.4
Reporter: Pavel Tupitsyn


{{ICache.EnableStatistics}}, {{ICluster.EnableStatistics}}.
See IGNITE-369.



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

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[Alex Volkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299751#comment-16299751
 ] 

Alex Volkov commented on IGNITE-7107:
-

Tested on CentOS 7. Looks pretty good.

> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



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

[jira] [Assigned] (IGNITE-7034) Web console: Hide connected clusters label on "become this user"

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-7034:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Connected clusters label remove on "Become user" mode.

> Web console: Hide connected clusters label on "become this user"
> 
>
> Key: IGNITE-7034
> URL: https://issues.apache.org/jira/browse/IGNITE-7034
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>




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

[jira] [Assigned] (IGNITE-7266) SQL TX: Joins return duplicated result when MVCC is disabled

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-7266:
---

Assignee: Vladimir Ozerov  (was: Igor Seliverstov)

> SQL TX: Joins return duplicated result when MVCC is disabled
> 
>
> Key: IGNITE-7266
> URL: https://issues.apache.org/jira/browse/IGNITE-7266
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
> Fix For: 2.5
>
>
> Affected tests:
> {{IgniteCacheJoinQueryWithAffinityKeyTest}}
> {{IgniteCacheCrossCacheJoinRandomTest}}
> All tests failed for the same reason: {{expected=X, actual=2*X}}. Looks like 
> we return too much results in some cases.



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

[jira] [Assigned] (IGNITE-7275) Admin panel: Grant\Revoke menu item text doesn't change

[Alexander Kalinin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Kalinin reassigned IGNITE-7275:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

Fixed adming toggling. Please test.

> Admin panel: Grant\Revoke menu item text doesn't change
> ---
>
> Key: IGNITE-7275
> URL: https://issues.apache.org/jira/browse/IGNITE-7275
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>
> # select any ordinary user and Grant admin rights - admin rights were 
> successfully granted
> # open Action menu - menu item text still says 'Grant' but should be 
> 'Revoke...'
> # select another user then select prev user - only after that menu item 
> become has right text



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