[jira] [Created] (IGNITE-10703) Queue drainTo should be batched operation
Dmitry Kiriy created IGNITE-10703: - Summary: Queue drainTo should be batched operation Key: IGNITE-10703 URL: https://issues.apache.org/jira/browse/IGNITE-10703 Project: Ignite Issue Type: Improvement Components: data structures Affects Versions: 2.7 Reporter: Dmitry Kiriy Currently drainTo(Collection to, int amount) implemented as cyclic call of poll() method, which is ineffective. Need to be implemented as truly batch operation - trying to read required amount of data at once. current design prevent high-performance data transfer cross queue. P.S. addAll implemented as batch, so together with right drainTo implementation, it will be complete high-performance batched read solution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10702) .NET: Ignite as Dotnet Core Global Tool
Pavel Tupitsyn created IGNITE-10702:
---
Summary: .NET: Ignite as Dotnet Core Global Tool
Key: IGNITE-10702
URL: https://issues.apache.org/jira/browse/IGNITE-10702
Project: Ignite
Issue Type: New Feature
Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.8
.NET Core Global Tool is just a NuGet package that contains a console
application.
This is a perfect solution for standalone nodes:
* Currently there is no way to run standalone nodes on Linux and macOS without
writing code
* Standalone nodes on Windows require downloading the whole binary package or
copying it from NuGet folder on classic .NET
With Global Tool users will be able to run Ignite.NET standalone node is just
two commands:
{code}
dotnet tool install -g apache-ignite
apache-ignite
{code}
Ignite Global Tool should be a separate NuGet package with the same
functionality as Apache.Ignite.exe
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722032#comment-16722032
]
Oleg Ignatenko commented on IGNITE-10701:
-
(i) for bot visa refer to [one in comments to IGNITE-10176
here|https://issues.apache.org/jira/browse/IGNITE-10176?focusedCommentId=16721096=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16721096]
- this is the check that ignored the issue reported here.
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722030#comment-16722030
]
ASF GitHub Bot commented on IGNITE-10701:
-
GitHub user oignatenko opened a pull request:
https://github.com/apache/ignite/pull/5674
IGNITE-10701 missing import in test under java8 directory
- added missing import
-- verified with diffs overview and rebuild
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10701
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5674.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 #5674
commit 453018d0a446c6f62e60b64e48792ef8b524
Author: Oleg Ignatenko
Date: 2018-12-15T06:14:43Z
IGNITE-10701 missing import
- added missing import
-- verified with diffs overview and rebuild
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10555) Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of 'TcpDiscoveryMulticastIpFinder'
[
https://issues.apache.org/jira/browse/IGNITE-10555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722031#comment-16722031
]
Ignite TC Bot commented on IGNITE-10555:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2548656]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2548661buildTypeId=IgniteTests24Java8_RunAll]
> Set 'TcpDiscoveryVmIpFinder' as default IP finder for tests instead of
> 'TcpDiscoveryMulticastIpFinder'
> --
>
> Key: IGNITE-10555
> URL: https://issues.apache.org/jira/browse/IGNITE-10555
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> Most of our tests starting Ignite nodes in the same JVM, that allows
> us using shared 'TcpDiscoveryVmIpFinder'.
> There are following main advantages of using 'TcpDiscoveryVmIpFinder':
> * reducing possible conflicts in the development environment, when
> nodes from different clusters may find each other;
> * speedup of nodes initial discovery, especially on Windows;
> * avoiding of overwriting 'getConfiguration' and copypasta only to set
> up static IP finder in tests;
> We should change the default IP finder in tests to
> 'TcpDiscoveryVmIpFinder' as the first step and remove related
> boilerplate as the second step.
> Once the first step of the change will be finished then we should fill a
> separate task for removing related boilerplate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10701:
Labels: MakeTeamcityGreenAgain (was: )
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko reassigned IGNITE-10701:
---
Assignee: Oleg Ignatenko
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10701:
Fix Version/s: 2.8
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
[
https://issues.apache.org/jira/browse/IGNITE-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-10701:
Ignite Flags: (was: Docs Required)
> add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
> --
>
> Key: IGNITE-10701
> URL: https://issues.apache.org/jira/browse/IGNITE-10701
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> As of now,
> [CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
> lacks imports for {{@RunWith(JUnit4.class)}}.
> Problem was discovered by manual check because this file is in "java8"
> directory and appears to be ignored by Teamcity build check (also I could not
> find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
Oleg Ignatenko created IGNITE-10701:
---
Summary: add missing import to
CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest
Key: IGNITE-10701
URL: https://issues.apache.org/jira/browse/IGNITE-10701
Project: Ignite
Issue Type: Task
Affects Versions: 2.8
Reporter: Oleg Ignatenko
As of now,
[CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest|https://github.com/apache/ignite/blob/master/modules/indexing/src/test/java8/org/apache/ignite/internal/processors/query/h2/CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest.java]
lacks imports for {{@RunWith(JUnit4.class)}}.
Problem was discovered by manual check because this file is in "java8"
directory and appears to be ignored by Teamcity build check (also I could not
find Maven profile to activate its usage)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9120) Metadata writer does not propagate error to failure handler
[
https://issues.apache.org/jira/browse/IGNITE-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721895#comment-16721895
]
ASF GitHub Bot commented on IGNITE-9120:
GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/5673
IGNITE-9120 Metadata writer does not propagate error to failure handler
Signed-off-by: a-polyakov
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a-polyakov/ignite ignite-9120
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5673.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 #5673
commit e44e6df12cd82e2e55952daa7f31538b3f1e332b
Author: a-polyakov
Date: 2018-12-15T00:02:20Z
IGNITE-9120 Metadata writer does not propagate error to failure handler
Signed-off-by: a-polyakov
> Metadata writer does not propagate error to failure handler
> ---
>
> Key: IGNITE-9120
> URL: https://issues.apache.org/jira/browse/IGNITE-9120
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexand Polyakov
>Assignee: Alexand Polyakov
>Priority: Major
>
> In logs
> {code:java}
> [WARN] [tcp-disco-msg-worker- # 2% DPL_GRID% DplGridNodeName%]
> [o.a.i.i.p.c.b.CacheObjectBinaryProcessorImpl] Failed to save metadata for
> typeId: 978611101; The exception was selected: there was no space left on the
> device{code}
> Node does not shut down
> The number of stalled transactions begins to grow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7132) Investigate and document Ignite Persistence usage in Docker
[ https://issues.apache.org/jira/browse/IGNITE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7132: Priority: Minor (was: Major) > Investigate and document Ignite Persistence usage in Docker > --- > > Key: IGNITE-7132 > URL: https://issues.apache.org/jira/browse/IGNITE-7132 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Minor > Fix For: 2.8 > > > Inspired by the following talk: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-in-docker-Native-Persistence-td18426.html > The aim is to investigate how is better to deploy Ignite persistence in > Docker. Probably with the usage of Docker volumes: > https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume > Once the configuration option is clear the following documentation needs to > be updated: > https://apacheignite.readme.io/docs/docker-deployment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-1188) We need to document Visor Cmd
[ https://issues.apache.org/jira/browse/IGNITE-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-1188. --- > We need to document Visor Cmd > - > > Key: IGNITE-1188 > URL: https://issues.apache.org/jira/browse/IGNITE-1188 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko >Priority: Major > > We need to give a list of Visor Commands. > Describe interactive and batch modes. > Give several examples of most useful commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7351) Create a page for continuous queries
[ https://issues.apache.org/jira/browse/IGNITE-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7351: Fix Version/s: (was: 2.7) > Create a page for continuous queries > > > Key: IGNITE-7351 > URL: https://issues.apache.org/jira/browse/IGNITE-7351 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Denis Magda >Priority: Major > > Create a page for continuous queries putting it under Features menu on the > site. This capability is a strong distinguisher from relational databases > that do not support continuous notifications and processing built around them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721768#comment-16721768 ] Denis Magda commented on IGNITE-6526: - Artem, I know you've been updating the capacity planning page. Is this a duplicate ticket? Please close if needed. > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-6526: --- Assignee: Artem Budnikov (was: Denis Magda) > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6526) Ignite 2.x capacity planning guide
[ https://issues.apache.org/jira/browse/IGNITE-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6526: Fix Version/s: (was: 2.7) 2.8 > Ignite 2.x capacity planning guide > -- > > Key: IGNITE-6526 > URL: https://issues.apache.org/jira/browse/IGNITE-6526 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Current capacity planning guide [1] is too high level and should be > elaborated considering durable memory's internals: > - memory pages overhead. > - per-entry overhead > (http://apache-ignite-users.70518.x6.nabble.com/Re-Memory-Overhead-per-entry-in-Apache-Ignite-td9498.html). > - space occupied for indexing needs. > - free lists > - etc. > The page has to include estimates for the Ignite Native Persistence: > - entry size and its overheads. > - index size and overheads. > - data files overheads. > - estimated WAL size and how to shrink it basing on checkpointing settings. > [1] https://apacheignite.readme.io/docs/capacity-planning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8137) Explain how to see SQL schema and table structure in Ignite
[
https://issues.apache.org/jira/browse/IGNITE-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-8137:
Fix Version/s: (was: 2.8)
> Explain how to see SQL schema and table structure in Ignite
> ---
>
> Key: IGNITE-8137
> URL: https://issues.apache.org/jira/browse/IGNITE-8137
> Project: Ignite
> Issue Type: New Feature
> Components: documentation
>Reporter: Denis Magda
>Priority: Major
>
> Presently, Ignite doesn't ship {{SHOW TABLE}} command. Thus, it's not clear
> how to get tables and schema structures in Ignite.
> Until this command is not supported we have to explain that:
> * Many tools use JDBC and ODBC metadata related parameters can pull that
> information out of there and present it to an end user. For instance, SQLline
> utilizes {{!table}} command that gets data from JDBC metadata methods.
> DBeaver utilizes the same approach.
> * Let's create {{Database Administration}} section under SQL reference
> (https://apacheignite-sql.readme.io/docs/sql-reference-overview) and
> presently list approaches supported by various tools (sqlline, dbeaver, etc)
> and how to get the same information from the drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8003) Dead documentation interface element
[ https://issues.apache.org/jira/browse/IGNITE-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8003: Fix Version/s: 2.8 > Dead documentation interface element > > > Key: IGNITE-8003 > URL: https://issues.apache.org/jira/browse/IGNITE-8003 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.4 >Reporter: Peter Ivanov >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > Attachments: Screen_Shot_2018_03_15_at_11_43_07.png > > > Most of the tables in lists of artifacts (for example on Downloads page) have > strange interface element settling down to the right, which does nothing (see > [^Screen_Shot_2018_03_15_at_11_43_07.png]). > I guess it should be either removed or fixed, whatever designation it has. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8091) Create Ignite monitoring guide describing metrics and monitoring facilities
[ https://issues.apache.org/jira/browse/IGNITE-8091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8091: Fix Version/s: (was: 2.8) > Create Ignite monitoring guide describing metrics and monitoring facilities > --- > > Key: IGNITE-8091 > URL: https://issues.apache.org/jira/browse/IGNITE-8091 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Priority: Major > Labels: iep-6 > > Ignite doesn't have a single documentation section which would aggregate all > the metrics the project has. There are random documentation pages spread out > across data grid, memory, persistence and other topics. > The new section will include the following: > * How to gather metrics (JMX, logs, APIs) > * Detailed metrics coverage for memory, persistence, rebalancing, compute, > etc. Consider IGNITE-8078 and IGNITE-8077 > * Monitoring tools > * How to integrate with 3rd party tools. > Use a draft of a monitoring guide as a reference: > https://docs.google.com/document/d/1yl7XoiWWPg_XGhwZJUg9Mm3muEApefoMiNLxEUxggV4/edit# -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9406) Improve SQL "Performance and Debugging" page
[ https://issues.apache.org/jira/browse/IGNITE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9406: Fix Version/s: (was: 2.7) 2.8 > Improve SQL "Performance and Debugging" page > > > Key: IGNITE-9406 > URL: https://issues.apache.org/jira/browse/IGNITE-9406 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > Attachments: ignite_sql_perf.txt > > > I prepared a document for one of Ignite clients with some advanced > information about how various performance optimizations work in Ignite SQL. > Let's compare this document with our "Performance and Debugging" page [1], > and enhance the latter with missing info (if any). > P.S.: Document is attached. Russian language. > [1] > https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10086) CPP: Update documentation stating Clang compiler as a supported
[ https://issues.apache.org/jira/browse/IGNITE-10086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-10086: - Fix Version/s: (was: 2.7) > CPP: Update documentation stating Clang compiler as a supported > --- > > Key: IGNITE-10086 > URL: https://issues.apache.org/jira/browse/IGNITE-10086 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Sapego >Priority: Major > > Need to check all relevant documentation files (readme.io, > modules/platforms/cpp/README.txt, modules/platforms/cpp/DEVNOTES.txt, > modules/platforms/cpp/odbc/README.txt) and add Clang as a supported compiler > if applicable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9798) Add TensorFlow Integration Page to Ignite website
[ https://issues.apache.org/jira/browse/IGNITE-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-9798. - Resolution: Fixed Completed. > Add TensorFlow Integration Page to Ignite website > - > > Key: IGNITE-9798 > URL: https://issues.apache.org/jira/browse/IGNITE-9798 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Denis Magda >Assignee: Yury Babak >Priority: Major > Fix For: 2.7 > > > We need to create a dedicated page for Ignite and TensorFlow integration. > Please put it under Machine Learning item of the Features menu. > [~abchaudhri], will provide a reference to the readme.io page with in-depth > integration description. > [~dmagda], I have discussed this with [~chief]. He will create a separate > section with new pages for TensorFlow Integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9485) Update documentation for ScanQuery with setLocal flag
[ https://issues.apache.org/jira/browse/IGNITE-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9485: Fix Version/s: (was: 2.7) 2.8 > Update documentation for ScanQuery with setLocal flag > - > > Key: IGNITE-9485 > URL: https://issues.apache.org/jira/browse/IGNITE-9485 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9716) Document partition distribution and reset lost partitions commands of control script
[ https://issues.apache.org/jira/browse/IGNITE-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9716: Fix Version/s: (was: 2.7) 2.8 > Document partition distribution and reset lost partitions commands of control > script > > > Key: IGNITE-9716 > URL: https://issues.apache.org/jira/browse/IGNITE-9716 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.8 > > > See [IGNITE-9549] - > control.sh add command to collect information on the distribution of > partitions and reset lost partitions > for details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9943) Update documentation for default WAL archive size (added auto-adjust)
[ https://issues.apache.org/jira/browse/IGNITE-9943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-9943: Fix Version/s: (was: 2.7) 2.8 > Update documentation for default WAL archive size (added auto-adjust) > - > > Key: IGNITE-9943 > URL: https://issues.apache.org/jira/browse/IGNITE-9943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9798) Add TensorFlow Integration Page to Ignite website
[ https://issues.apache.org/jira/browse/IGNITE-9798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-9798. --- > Add TensorFlow Integration Page to Ignite website > - > > Key: IGNITE-9798 > URL: https://issues.apache.org/jira/browse/IGNITE-9798 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Denis Magda >Assignee: Yury Babak >Priority: Major > Fix For: 2.7 > > > We need to create a dedicated page for Ignite and TensorFlow integration. > Please put it under Machine Learning item of the Features menu. > [~abchaudhri], will provide a reference to the readme.io page with in-depth > integration description. > [~dmagda], I have discussed this with [~chief]. He will create a separate > section with new pages for TensorFlow Integration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-2769) Document store session listeners
[ https://issues.apache.org/jira/browse/IGNITE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2769: Priority: Minor (was: Major) > Document store session listeners > > > Key: IGNITE-2769 > URL: https://issues.apache.org/jira/browse/IGNITE-2769 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Prachi Garg >Priority: Minor > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-1188) We need to document Visor Cmd
[ https://issues.apache.org/jira/browse/IGNITE-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-1188. - Resolution: Fixed > We need to document Visor Cmd > - > > Key: IGNITE-1188 > URL: https://issues.apache.org/jira/browse/IGNITE-1188 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: sprint-1 >Reporter: Alexey Kuznetsov >Assignee: Vasiliy Sisko >Priority: Major > > We need to give a list of Visor Commands. > Describe interactive and batch modes. > Give several examples of most useful commands. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations
[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7704: Fix Version/s: 2.8 > Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts > and their relations > --- > > Key: IGNITE-7704 > URL: https://issues.apache.org/jira/browse/IGNITE-7704 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.3 >Reporter: Alexey Popov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.8 > > Attachments: timeouts.md, timeouts_v2.md > > > We often see similar questions related to IgniteConfiguration, > TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations. And we see > several side-effects after incorrect timeout configuration. > It looks like this question is not well documented. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-2769) Document store session listeners
[ https://issues.apache.org/jira/browse/IGNITE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2769: Fix Version/s: (was: 2.8) > Document store session listeners > > > Key: IGNITE-2769 > URL: https://issues.apache.org/jira/browse/IGNITE-2769 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Valentin Kulichenko >Assignee: Prachi Garg >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7611: Fix Version/s: (was: 2.7) 2.8 > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.8 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7739) Write about Spring Injection and IgniteSpringBean in documentation
[ https://issues.apache.org/jira/browse/IGNITE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7739: Priority: Minor (was: Major) > Write about Spring Injection and IgniteSpringBean in documentation > -- > > Key: IGNITE-7739 > URL: https://issues.apache.org/jira/browse/IGNITE-7739 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ilya Kasnacheev >Priority: Minor > Fix For: 2.8 > > > Currently there is no mention of IgniteSpringBean on readme.io > We have section https://apacheignite.readme.io/docs/resource-injection but > it's totally not obvious how to make e.g. SpringResource work, what are > pre-requisites. > Thing is, if Ignite creates Spring context (via Ignition), then Spring > injection would work out of box. > If Spring context creates Ignite as a bean, that bean should be > IgniteSpringBean and not Ignite. Otherwise, Spring context and lifecycle > would not be visible to Ignite and injection won't work. > On unrelated note, maybe we need support for Spring Boot already? See > https://habrahabr.ru/post/310672/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7781) JMX beans documentation
[ https://issues.apache.org/jira/browse/IGNITE-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7781: Priority: Minor (was: Major) > JMX beans documentation > --- > > Key: IGNITE-7781 > URL: https://issues.apache.org/jira/browse/IGNITE-7781 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Assignee: Artem Budnikov >Priority: Minor > Labels: documentation, jmx > Fix For: 2.8 > > Attachments: MXBeansJavaDoc.zip > > > There are about 30 JMX beans implemented in Ignite, but there is no > documentation for most of these beans, except memory metrics and brief > overview of cache metrics. > Folowing MBeans/MXBeans can be documented: > ||MBeans group||Interface||Path||Comment|| > |Eviction > metrics|org.apache.ignite.cache.eviction.fifo.FifoEvictionPolicyMBean, > org.apache.ignite.cache.eviction.igfs.IgfsPerBlockLruEvictionPolicyMXBean, > org.apache.ignite.cache.eviction.lru.LruEvictionPolicyMBean, > org.apache.ignite.cache.eviction.sorted.SortedEvictionPolicyMBean|org.apache|For > each cache, if eviction for cache is configured| > |Cache group > metrics|org.apache.ignite.mxbean.CacheGroupMetricsMXBean|org.apache..."Cache > groups".|For each group| > |Cache > metrics|org.apache.ignite.mxbean.CacheMetricsMXBean|org.apacheCacheClusterMetricsMXBeanImpl, > > org.apacheCacheLocalMetricsMXBeanImpl|For > each cache| > |Cluster > metrics|org.apache.ignite.mxbean.ClusterMetricsMXBean|org.apache...Kernal.ClusterLocalNodeMetricsMXBeanImpl, > org.apache...Kernal.ClusterMetricsMXBeanImpl| > |Data region (memory) > metrics|org.apache.ignite.mxbean.DataRegionMetricsMXBean|org.apache...DataRegionMetrics.|For > each data region| > |Data storage > metrics|org.apache.ignite.mxbean.DataStorageMetricsMXBean|org.apache..."Persistent > Store".DataStorageMetrics| > |Instance > information|org.apache.ignite.mxbean.IgniteMXBean|org.apache...Kernal.IgniteKernal| > |Ignition > state|org.apache.ignite.mxbean.IgnitionMXBean|org.apache..Kernel.Ignition| > |Thread pools metrics|org.apache.ignite.mxbean.ThreadPoolMXBean, > org.apache.ignite.mxbean.StripedExecutorMXBean|org.apache..."Thread > Pools".|For each executor| > |SPI|org.apache.ignite.spi.cache.CacheCheckpointSpiMBean, > org.apache.ignite.spi.collision.fifoqueue.FifoQueueCollisionSpiMBean, > org.apache.ignite.spi.collision.jobstealing.JobStealingCollisionSpiMBean, > org.apache.ignite.spi.collision.priorityqueue.PriorityQueueCollisionSpiMBean, > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpiMBean, > org.apache.ignite.spi.deployment.local.LocalDeploymentSpiMBean, > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpiMBean, > org.apache.ignite.spi.eventstorage.memory.MemoryEventStorageSpiMBean, > org.apache.ignite.spi.failover.always.AlwaysFailoverSpiMBean, > org.apache.ignite.spi.failover.jobstealing.JobStealingFailoverSpiMBean, > org.apache.ignite.spi.failover.never.NeverFailoverSpiMBean, > org.apache.ignite.spi.jdbc.JdbcCheckpointSpiMBean, > org.apache.ignite.spi.loadbalancing.adaptive.AdaptiveLoadBalancingSpiMBean, > org.apache.ignite.spi.loadbalancing.roundrobin.RoundRobinLoadBalancingSpiMBean, > > org.apache.ignite.spi.loadbalancing.weightedrandom.WeightedRandomLoadBalancingSpiMBean, > > org.apache.ignite.spi.sharedfs.SharedFsCheckpointSpiMBean|org.apache...SPIs.| > > JavaDoc for this beans is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7906) Create languages comparison page
[ https://issues.apache.org/jira/browse/IGNITE-7906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7906: Fix Version/s: (was: 2.8) > Create languages comparison page > - > > Key: IGNITE-7906 > URL: https://issues.apache.org/jira/browse/IGNITE-7906 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Denis Magda >Assignee: Vladimir Ozerov >Priority: Major > > In addition to Java, .NET and C++ thick clients, the community is going to > support a variety of thin client for many other languages such as Python, > Node.JS, etc. It will be beneficial to create a page that depicts > capabilities of every language like this one: > https://hazelcast.org/clients-languages/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8195) ZookeeperDiscoverySpi should be properly documented
[ https://issues.apache.org/jira/browse/IGNITE-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-8195. --- > ZookeeperDiscoverySpi should be properly documented > --- > > Key: IGNITE-8195 > URL: https://issues.apache.org/jira/browse/IGNITE-8195 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Priority: Major > > ZookeeperDiscoverySpi as part of public API should be documented with the > same detail level as TcpDiscoverySpi. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8195) ZookeeperDiscoverySpi should be properly documented
[ https://issues.apache.org/jira/browse/IGNITE-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-8195. - Resolution: Won't Fix The docs were improved. > ZookeeperDiscoverySpi should be properly documented > --- > > Key: IGNITE-8195 > URL: https://issues.apache.org/jira/browse/IGNITE-8195 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Priority: Major > > ZookeeperDiscoverySpi as part of public API should be documented with the > same detail level as TcpDiscoverySpi. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8253) CacheConfiguration.keyConfiguration is never documented
[ https://issues.apache.org/jira/browse/IGNITE-8253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8253: Affects Version/s: (was: 2.4) 2.8 > CacheConfiguration.keyConfiguration is never documented > --- > > Key: IGNITE-8253 > URL: https://issues.apache.org/jira/browse/IGNITE-8253 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.8 >Reporter: Ilya Kasnacheev >Priority: Major > > See > http://apache-ignite-users.70518.x6.nabble.com/How-do-you-configure-affinityKey-in-xml-tp21165.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8726) Highlight that memory metrics are local for a node in the docs
[
https://issues.apache.org/jira/browse/IGNITE-8726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-8726:
Affects Version/s: 2.8
> Highlight that memory metrics are local for a node in the docs
> --
>
> Key: IGNITE-8726
> URL: https://issues.apache.org/jira/browse/IGNITE-8726
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.8
>Reporter: Stanislav Lukyanov
>Priority: Major
>
> Memory Metrics (DataRegionMetrics and DataStorageMetrics) in Ignite are local
> for each node. However, this is not highlighted in the documentation enough.
> The code snippets suggest to just call `ignite.dataRegionMetrics()` which
> seems to be a bit at odds with the general use case of Ignite servers being
> started via ignite.sh.
> It would be good to have an easily noticeable warning that the metrics will
> only return data for the local node (and that, for example, on client they
> would typically always print 0).
> Also, would be nice to include a couple of practical approaches other than
> JMX to collect metrics. E.g. a snippet of client code getting metrics from
> all servers:
> {code}
> Collection metricsFromNodes = ignite.compute().broadcast(() -> {
> Ignite ignite = Ignition.localIgnite();
>
> StringBuilder sb = new StringBuilder();
>
> sb.append("Node: " + ignite.name());
>
> for (DataRegionMetrics metrics : ignite.dataRegionMetrics()) {
> // append metrics to the builder
> }
>
> return sb.toString();
> });
> for (String metricsString : metricsFromNodes)
> System.out.println(metricsString);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10051) Kubernetes documentation improvements
[
https://issues.apache.org/jira/browse/IGNITE-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721747#comment-16721747
]
Denis Magda commented on IGNITE-10051:
--
[~abchaudhri], have you applied the changes?
> Kubernetes documentation improvements
> -
>
> Key: IGNITE-10051
> URL: https://issues.apache.org/jira/browse/IGNITE-10051
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.6
>Reporter: Maxim Pudov
>Priority: Major
> Fix For: 2.8
>
> Attachments: kube-dashboard-access.yaml, mongodb-deployment.yaml
>
>
> I verified the deployment instructions of a kubernetes cluster with apache
> ignite and found some issues.
> 1. AWS deployment:
> [https://apacheignite.readme.io/docs/amazon-web-services-eks-deployment]
> miss print:
> {quote}{{kubbectl get pods}}
> {quote}
> has to be:
> {quote}{{kubectl get pods}}
> {quote}
> 2. Google Cloud deployment
> [https://apacheignite.readme.io/docs/google-cloud-deployment]
> Screenshots seem to be outdated
> 3. Microsoft Azure deployment
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment#section-access-to-your-kubernetes-cluster]
> 3.1 At first I had no access to Kubernetes dashboard having this error:
> azure kubernetes dashboard namespaces is forbidden: User
> "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list
> namespaces at the cluster scope
> This problem was solved by adding this config:
> {quote}kubectl create -f [^kube-dashboard-access.yaml]
> {quote}
> 3.2 Screenshots seem to be outdated for azure too.
> 4. Stateless deployment:
> [https://apacheignite.readme.io/docs/stateless-deployment]
> 4.1 At first we create example-cube-rbac.xml locally, but then we don't use
> it.
> 4.2 Instead the configuration file ignite-deployment.yaml
> ([https://apacheignite.readme.io/docs/stateless-deployment#section-ignite-pods-deployment])
> points to the wrong external configuration file:
> {quote}{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml}}
> {quote}
> I believe, it has to point to
> {quote}[{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rback.xml}}|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rbac.xml]
> {quote}
> 4.3 In the same configuration file ignite-deployment.yaml there is a row
> {quote}{{serviceAccountName: ignite}}
> {quote}
> with Tab symbol, which has to be replaced with double Space.
> 5. Web console kubernetes installation.
> [https://apacheignite-tools.readme.io/docs/kubernetes-installation]
> 5.1 mongodb-deployment.yaml doesn't work as is. I had to modified it (check
> the attachment [^mongodb-deployment.yaml])
> 5.2 web-console-deployment.yaml - default image values aren't specified for
> frontend and backend (apacheignite/web-console-frontend,
> apacheignite/web-console-backend)
> 5.3 web-agent-deployment.yaml - serviceAccountName: "ignite-cluster" is
> incorrect. I guess "ignite" is the right one.
> 5.4 No such docker image as apacheignite/web-agent:mytag3.
> 6. General suggestions for kubernetes cluster deployment on GCC, AWS, Azure.
> 6.1 Create cluster via AWS Console, not command line. It's easier to pick
> values from drop down lists, and we don't provide complete installation via
> command line anyway.
> 6.2 When we suggest to use our configuration files for setting up services
> and pods, it is worth mentioning that our configs contain region parameter
> (zones: eu-west-1a) and user has to modify it himself.
> 6.3 The link to download configuration files points to the master branch,
> which could cause problems in future. For AWS it's
> [https://github.com/apache/ignite/tree/master/modules/kubernetes/config/eks]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8411) Binary Client Protocol spec: other parts clarifications
[ https://issues.apache.org/jira/browse/IGNITE-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-8411: Fix Version/s: (was: 2.7) 2.8 > Binary Client Protocol spec: other parts clarifications > --- > > Key: IGNITE-8411 > URL: https://issues.apache.org/jira/browse/IGNITE-8411 > Project: Ignite > Issue Type: Improvement > Components: documentation, thin client >Affects Versions: 2.4 >Reporter: Alexey Kosenchuk >Priority: Major > Fix For: 2.8 > > > issues against previous parts: IGNITE-8039 IGNITE-8212 > Cache Configuration > --- > > [https://apacheignite.readme.io/docs/binary-client-protocol-cache-configuration-operations] > - OP_CACHE_GET_CONFIGURATION and OP_CACHE_CREATE_WITH_CONFIGURATION - > QueryEntity - Structure of QueryField: > absent "default value - type Object" - it is the last field of the > QueryField in reality. > - OP_CACHE_GET_CONFIGURATION - Structure of Cache Configuration: > Absent CacheAtomicityMode - is the first field in reality. > Absent MaxConcurrentAsyncOperations - is between DefaultLockTimeout and > MaxQueryIterators in reality. > "Invalidate" field - does not exist in reality. > - meaning and possible values of every configuration parameter must be > clarified. If clarified in other docs, this spec must have link(s) to that > docs. > - suggest to combine somehow Cache Configuration descriptions in > OP_CACHE_GET_CONFIGURATION and OP_CACHE_CREATE_WITH_CONFIGURATION - to avoid > duplicated descriptions. > SQL and Scan Queries > > [https://apacheignite.readme.io/docs/binary-client-protocol-sql-operations] > - "Flag. Pass 0 for default, or 1 to keep the value in binary form.": > "the value in binary form" flag should be left end clarified in the > operations to which it is applicable for. > - OP_QUERY_SQL: > most of the fields in the request must be clarified. If clarified in other > docs, this spec must have link(s) to that docs. > For example: > ** "Name of a type or SQL table": name of what type? > - OP_QUERY_SQL_FIELDS: > most of the fields in the request must be clarified. If clarified in other > docs, this spec must have link(s) to that docs. > For example: > ** is there any correlation between "Query cursor page size" and "Max rows"? > ** "Statement type": why there are only three types? what about INSERT, etc.? > - OP_QUERY_SQL_FIELDS_CURSOR_GET_PAGE Response does not contain Cursor id. > But responses for all other query operations contain it. Is it intentional? > - OP_QUERY_SCAN_CURSOR_GET_PAGE Response - Cursor id is absent in reality. > - OP_QUERY_SCAN_CURSOR_GET_PAGE Response - Row count field: says type > "long". Should be "int". > - OP_QUERY_SCAN: > format and rules of the Filter object must be clarified. If clarified in > other docs, this spec must have link(s) to that docs. > - OP_QUERY_SCAN: > in general, it's not clear how this operation should be supported on > platforms other than the mentioned in "Filter platform" field. > - OP_QUERY_SCAN: "Number of partitions to query" > Should be updated to "A partition number to query" > > Binary Types > > > [https://apacheignite.readme.io/docs/binary-client-protocol-binary-type-operations] > - somewhere should be explained when and why these operations need to be > supported by a client. > - Type id and Field id: > should be clarified that before an Id calculation Type and Field names must > be updated to low case. > - OP_GET_BINARY_TYPE and OP_PUT_BINARY_TYPE - BinaryField - Type id: > in reality it is not a type id (hash code) but a type code (1, 2,... 10,... > 103,...). > - OP_GET_BINARY_TYPE and OP_PUT_BINARY_TYPE - "Affinity key field name": > should be explained what is it. If explained in other docs, this spec must > have link(s) to that docs. > - OP_PUT_BINARY_TYPE - schema id: > mandatory algorithm of schema Id calculation must be described somewhere. If > described in other docs, this spec must have link(s) to that docs. > - OP_REGISTER_BINARY_TYPE_NAME and OP_GET_BINARY_TYPE_NAME: > should be explained when and why these operations need to be supported by a > client. > How this operation should be supported on platforms other than the mentioned > in "Platform id" field. > - OP_REGISTER_BINARY_TYPE_NAME: > Type name - is it "full" or "short" name here? > Type id - is it a hash from "full" or "short" name here? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4221) Document ComputeJobMasterLeaveAware interface usage
[ https://issues.apache.org/jira/browse/IGNITE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721755#comment-16721755 ] Denis Magda commented on IGNITE-4221: - Consider for the new documentation structure. > Document ComputeJobMasterLeaveAware interface usage > --- > > Key: IGNITE-4221 > URL: https://issues.apache.org/jira/browse/IGNITE-4221 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > The usage and applicability of `ComputeJobMasterLeaveAware` have to be > documented on Apache Ignite Readme.io which will help out to avoid discussion > like that [1]. The new page has to be created for the topic and placed here > [2]. > In advance, the following example has to be contributed to Apache Ignite > https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/compute/masterleave/ComputeMasterLeaveAwareExample.java > > [1] > http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html > [2] https://apacheignite.readme.io/docs/compute-grid#section-features -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4222) Document the usage of ComputeJobContinuation API
[ https://issues.apache.org/jira/browse/IGNITE-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721754#comment-16721754 ] Denis Magda commented on IGNITE-4222: - Consider for the new documentation structure. > Document the usage of ComputeJobContinuation API > > > Key: IGNITE-4222 > URL: https://issues.apache.org/jira/browse/IGNITE-4222 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > The usage and applicability of `ComputeJobContinuation` have to be documented > on Apache Ignite Readme.io which will help out to avoid discussion like those > [1] and [4]. The new page has to be created for the topic and placed here [2]. > The content should consist not only of technical details but also provide use > cases for this API: > - don't block a thread from the public pool if a job is waiting for some > result. Put the thread back into the pool and wait for the result > asynchronously. > - splitting a job into several pieces that can be executed in parallel. Refer > to this example [3]. > > [1] > http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html > [2] https://apacheignite.readme.io/docs/compute-grid#section-features > [3] > https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java > [4] > http://apache-ignite-users.70518.x6.nabble.com/ignite-compute-job-continuation-documentation-td16725.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-3690) Log Message Glossary
[ https://issues.apache.org/jira/browse/IGNITE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-3690: Priority: Minor (was: Critical) > Log Message Glossary > > > Key: IGNITE-3690 > URL: https://issues.apache.org/jira/browse/IGNITE-3690 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 1.4 >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Minor > Fix For: 2.8 > > > It's time for Ignite to create a page which lists ALL the log messages, their > common causes and potential solutions. > Probably it makes sense to assign an unique ID for the most well-know errors > so that a user is able to look up an error in the glossary quicker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5678) Need to document and test supported and unsupported SQL features
[ https://issues.apache.org/jira/browse/IGNITE-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-5678: Fix Version/s: (was: 2.8) > Need to document and test supported and unsupported SQL features > > > Key: IGNITE-5678 > URL: https://issues.apache.org/jira/browse/IGNITE-5678 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Dmitriy Setrakyan >Assignee: Sergey Kozlov >Priority: Minor > > We should provide supported and unsupported feature documentation, similar to > PostgreSQL: https://www.postgresql.org/docs/devel/static/features.html > We can do the following: > * Have a very detailed documented list of all the supported/unsupported > features in Ignite SQL engine. > * Once the list is created, ensure that we have sufficient test coverage for > all the supported features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6806) Document logs forwarding to ELK stack
[ https://issues.apache.org/jira/browse/IGNITE-6806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721752#comment-16721752 ] Denis Magda commented on IGNITE-6806: - Consider for the new documentation structure. > Document logs forwarding to ELK stack > - > > Key: IGNITE-6806 > URL: https://issues.apache.org/jira/browse/IGNITE-6806 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > Ignite logs can be forwarded to remote servers and software stacks for > advanced processing. > For instance, this project shows how to do this for ELK stack: > https://github.com/akuramshingg/elk-monitor > Mention it on Ignite logging page: > https://apacheignite.readme.io/docs/logging -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5678) Need to document and test supported and unsupported SQL features
[ https://issues.apache.org/jira/browse/IGNITE-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-5678: Priority: Minor (was: Major) > Need to document and test supported and unsupported SQL features > > > Key: IGNITE-5678 > URL: https://issues.apache.org/jira/browse/IGNITE-5678 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Dmitriy Setrakyan >Assignee: Sergey Kozlov >Priority: Minor > > We should provide supported and unsupported feature documentation, similar to > PostgreSQL: https://www.postgresql.org/docs/devel/static/features.html > We can do the following: > * Have a very detailed documented list of all the supported/unsupported > features in Ignite SQL engine. > * Once the list is created, ensure that we have sufficient test coverage for > all the supported features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5922) Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize
[ https://issues.apache.org/jira/browse/IGNITE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721753#comment-16721753 ] Denis Magda commented on IGNITE-5922: - Consider for the new documentation. > Improve FifoCollisionSpi doc - ParallelJobsNumber should be less than > PublicThreadPoolSize > -- > > Key: IGNITE-5922 > URL: https://issues.apache.org/jira/browse/IGNITE-5922 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Prachi Garg >Priority: Minor > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6993) Document SMTP server documentation for Web Console
[ https://issues.apache.org/jira/browse/IGNITE-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-6993: Priority: Minor (was: Major) > Document SMTP server documentation for Web Console > -- > > Key: IGNITE-6993 > URL: https://issues.apache.org/jira/browse/IGNITE-6993 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.3 >Reporter: Denis Magda >Assignee: Artem Budnikov >Priority: Minor > Fix For: 2.8 > > > Document how to configure a custom SMTP server for Web Console on this domain > under "Ignite Web Console" section: > https://apacheignite-tools.readme.io/docs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7268) SQL Tutorials Per Language
[ https://issues.apache.org/jira/browse/IGNITE-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-7268. - Resolution: Won't Fix No longer relevant. We'll rework the entire documentation once the new structure is approved. > SQL Tutorials Per Language > -- > > Key: IGNITE-7268 > URL: https://issues.apache.org/jira/browse/IGNITE-7268 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Priority: Major > Fix For: 2.8 > > > Create SQL getting started tutorials for major programming languages relying > on JDBC/ODBC drivers. Have Spanner's tutorials in mind as an example: > https://cloud.google.com/spanner/docs/getting-started/nodejs/ > This is an umbrella ticket. Language-specific tutorials will be handled as > subtasks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7336) Improve peer class loading documentation
[ https://issues.apache.org/jira/browse/IGNITE-7336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7336. --- > Improve peer class loading documentation > > > Key: IGNITE-7336 > URL: https://issues.apache.org/jira/browse/IGNITE-7336 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.3 >Reporter: Valentin Kulichenko >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > [Zero Deployment|https://apacheignite.readme.io/docs/zero-deployment] page > should be updated with the following: > * Applicability of the feature (where it can and can't be used). > * Warning about anonymous classes and lambdas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7336) Improve peer class loading documentation
[ https://issues.apache.org/jira/browse/IGNITE-7336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-7336. - Resolution: Won't Fix The documentation would be reworked completely after the new structure gets approved. > Improve peer class loading documentation > > > Key: IGNITE-7336 > URL: https://issues.apache.org/jira/browse/IGNITE-7336 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.3 >Reporter: Valentin Kulichenko >Assignee: Prachi Garg >Priority: Major > Fix For: 2.8 > > > [Zero Deployment|https://apacheignite.readme.io/docs/zero-deployment] page > should be updated with the following: > * Applicability of the feature (where it can and can't be used). > * Warning about anonymous classes and lambdas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10051) Kubernetes documentation improvements
[
https://issues.apache.org/jira/browse/IGNITE-10051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda reassigned IGNITE-10051:
Assignee: Akmal Chaudhri
> Kubernetes documentation improvements
> -
>
> Key: IGNITE-10051
> URL: https://issues.apache.org/jira/browse/IGNITE-10051
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.6
>Reporter: Maxim Pudov
>Assignee: Akmal Chaudhri
>Priority: Major
> Fix For: 2.8
>
> Attachments: kube-dashboard-access.yaml, mongodb-deployment.yaml
>
>
> I verified the deployment instructions of a kubernetes cluster with apache
> ignite and found some issues.
> 1. AWS deployment:
> [https://apacheignite.readme.io/docs/amazon-web-services-eks-deployment]
> miss print:
> {quote}{{kubbectl get pods}}
> {quote}
> has to be:
> {quote}{{kubectl get pods}}
> {quote}
> 2. Google Cloud deployment
> [https://apacheignite.readme.io/docs/google-cloud-deployment]
> Screenshots seem to be outdated
> 3. Microsoft Azure deployment
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment#section-access-to-your-kubernetes-cluster]
> 3.1 At first I had no access to Kubernetes dashboard having this error:
> azure kubernetes dashboard namespaces is forbidden: User
> "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list
> namespaces at the cluster scope
> This problem was solved by adding this config:
> {quote}kubectl create -f [^kube-dashboard-access.yaml]
> {quote}
> 3.2 Screenshots seem to be outdated for azure too.
> 4. Stateless deployment:
> [https://apacheignite.readme.io/docs/stateless-deployment]
> 4.1 At first we create example-cube-rbac.xml locally, but then we don't use
> it.
> 4.2 Instead the configuration file ignite-deployment.yaml
> ([https://apacheignite.readme.io/docs/stateless-deployment#section-ignite-pods-deployment])
> points to the wrong external configuration file:
> {quote}{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-persistence.xml}}
> {quote}
> I believe, it has to point to
> {quote}[{{https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rback.xml}}|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube-rbac.xml]
> {quote}
> 4.3 In the same configuration file ignite-deployment.yaml there is a row
> {quote}{{serviceAccountName: ignite}}
> {quote}
> with Tab symbol, which has to be replaced with double Space.
> 5. Web console kubernetes installation.
> [https://apacheignite-tools.readme.io/docs/kubernetes-installation]
> 5.1 mongodb-deployment.yaml doesn't work as is. I had to modified it (check
> the attachment [^mongodb-deployment.yaml])
> 5.2 web-console-deployment.yaml - default image values aren't specified for
> frontend and backend (apacheignite/web-console-frontend,
> apacheignite/web-console-backend)
> 5.3 web-agent-deployment.yaml - serviceAccountName: "ignite-cluster" is
> incorrect. I guess "ignite" is the right one.
> 5.4 No such docker image as apacheignite/web-agent:mytag3.
> 6. General suggestions for kubernetes cluster deployment on GCC, AWS, Azure.
> 6.1 Create cluster via AWS Console, not command line. It's easier to pick
> values from drop down lists, and we don't provide complete installation via
> command line anyway.
> 6.2 When we suggest to use our configuration files for setting up services
> and pods, it is worth mentioning that our configs contain region parameter
> (zones: eu-west-1a) and user has to modify it himself.
> 6.3 The link to download configuration files points to the master branch,
> which could cause problems in future. For AWS it's
> [https://github.com/apache/ignite/tree/master/modules/kubernetes/config/eks]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Prokofyev reassigned IGNITE-4440:
---
Assignee: Alexander Prokofyev
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Assignee: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9893) add hibernate-5.3 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721695#comment-16721695 ] Scott Feldstein commented on IGNITE-9893: - hi [~ilyak], thanks for the update. I'll try to match the formatting unless you have an auto-formatter that i can use :) questions: # Did you figure what needs to happen in order to publish the dependencies? Is there a licensing issue? # DFLT_CACHE_NAME_PROPERTY doesn't make sense in ignite 2.x, so my plan is to remove that functionality from the hibernate-4.2 module - do you have any comments on that? I'll try to find time to work on it in the next few days.. > add hibernate-5.3 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10700) [ML] Working with Binary Objects
Yury Babak created IGNITE-10700: --- Summary: [ML] Working with Binary Objects Key: IGNITE-10700 URL: https://issues.apache.org/jira/browse/IGNITE-10700 Project: Ignite Issue Type: Improvement Reporter: Yury Babak Assignee: Yury Babak Fix For: 2.8 Currently, we do not support working with caches which contains Binary Objects, we should add support of building datasets from those objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721609#comment-16721609
]
ASF GitHub Bot commented on IGNITE-10176:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5659
> migrate non-core modules tests from Junit 3 to 4
>
>
> Key: IGNITE-10176
> URL: https://issues.apache.org/jira/browse/IGNITE-10176
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> If needed, refer parent task for more details.
> Migrate using new API introduced and tested at prior step.
> Also, make sure that there are no inappropriate annotations in methods that
> override {{beforeTest}} and {{afterTest}} as explained in more details [in
> comments
> below|https://issues.apache.org/jira/browse/IGNITE-10176?focusedCommentId=16718914=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16718914].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-10176:
Fix Version/s: 2.8
> migrate non-core modules tests from Junit 3 to 4
>
>
> Key: IGNITE-10176
> URL: https://issues.apache.org/jira/browse/IGNITE-10176
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> If needed, refer parent task for more details.
> Migrate using new API introduced and tested at prior step.
> Also, make sure that there are no inappropriate annotations in methods that
> override {{beforeTest}} and {{afterTest}} as explained in more details [in
> comments
> below|https://issues.apache.org/jira/browse/IGNITE-10176?focusedCommentId=16718914=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16718914].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-4015) Continuous query events could be lost on backup node when primary leaves (transactional cache).
[ https://issues.apache.org/jira/browse/IGNITE-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4015: --- Labels: MakeTeamcityGreenAgain transactions (was: transactions) > Continuous query events could be lost on backup node when primary leaves > (transactional cache). > --- > > Key: IGNITE-4015 > URL: https://issues.apache.org/jira/browse/IGNITE-4015 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 1.6, 1.7 >Reporter: Andrew Mashenkov >Priority: Major > Labels: MakeTeamcityGreenAgain, transactions > > Consider the following scenario: > 1) One stable node in topology; > 2) PARTITIONED, TRANSACTIONAL cache with 1 backup; > 3) Continuous query is set on the cache; > 4) Put some data to cache. > If another node joins the cluster, it will handle some updates. > But when it leaves the topology during put transaction, transaction rolled > back with retry and events are lost. > Reproducer can be found in > org.apache.ignite.loadtests.continuous.CacheContinuousQueryFailoverTxPrimaryWriteOrderLoadTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10657) Thin clients (ODBC, JDBC, Java) should call ctx.security().onSessionExpired(subjid) on disconnect to avoid the possible leaking of the memory
[ https://issues.apache.org/jira/browse/IGNITE-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721599#comment-16721599 ] ASF GitHub Bot commented on IGNITE-10657: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5658 > Thin clients (ODBC, JDBC, Java) should call > ctx.security().onSessionExpired(subjid) on disconnect to avoid the possible > leaking of the memory > - > > Key: IGNITE-10657 > URL: https://issues.apache.org/jira/browse/IGNITE-10657 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.8 > > > At the moment all classes that implement > ClientListenerAbstractConnectionContext don't call the > ctx.security().onSessionExpired(subjid) on disconect. > It provides the leaking of the memory related to resources that were > generated during authentification. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10176) migrate non-core modules tests from Junit 3 to 4
[
https://issues.apache.org/jira/browse/IGNITE-10176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721592#comment-16721592
]
Eduard Shangareev commented on IGNITE-10176:
[~oignatenko], I have looked through, looks great! Enormous efforts.
> migrate non-core modules tests from Junit 3 to 4
>
>
> Key: IGNITE-10176
> URL: https://issues.apache.org/jira/browse/IGNITE-10176
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> If needed, refer parent task for more details.
> Migrate using new API introduced and tested at prior step.
> Also, make sure that there are no inappropriate annotations in methods that
> override {{beforeTest}} and {{afterTest}} as explained in more details [in
> comments
> below|https://issues.apache.org/jira/browse/IGNITE-10176?focusedCommentId=16718914=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16718914].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10591) MVCC: Incorrect data region metrics.
[
https://issues.apache.org/jira/browse/IGNITE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov reassigned IGNITE-10591:
-
Assignee: Andrew Mashenkov
> MVCC: Incorrect data region metrics.
>
>
> Key: IGNITE-10591
> URL: https://issues.apache.org/jira/browse/IGNITE-10591
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, persistence
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode failed.
> {noformat}
> junit.framework.AssertionFailedError: Number of allocated pages is different
> than in metrics for [node=db.IgnitePdsDataRegionMetricsTest0, cache=default]
> expected:<13542> but was:<13881>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:159)
> at junit.framework.TestCase.assertEquals(TestCase.java:316)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.checkMetricsConsistency(IgnitePdsDataRegionMetricsTest.java:337)
> at
> org.apache.ignite.internal.processors.cache.persistence.db.IgnitePdsDataRegionMetricsTest.testMemoryUsageSingleNode(IgnitePdsDataRegionMetricsTest.java:155){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10421) MVCC: Assertion in checkpointer thread.
[
https://issues.apache.org/jira/browse/IGNITE-10421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov reassigned IGNITE-10421:
-
Assignee: Andrew Mashenkov
> MVCC: Assertion in checkpointer thread.
> ---
>
> Key: IGNITE-10421
> URL: https://issues.apache.org/jira/browse/IGNITE-10421
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, persistence
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> Reproducers:
> * {{WalModeChangeAdvancedSelfTest#testJoin}} with enabled MVCC.
> * {{IgniteDynamicCacheStartFailWithPersistenceTest}}
> {noformat}
> [2018-11-27
> 14:56:47,548][ERROR][db-checkpoint-thread-#358%srv_3%][IgniteTestResources]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=SingletonSet [SYSTEM_WORKER_BLOCKED]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.IgniteCheckedException: Compound exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for
> CountDownFuture.
> at
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
> at
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
> at
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3957)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Suppressed: java.lang.AssertionError: off=3000,
> allocated=1000, pageId=00020002,
> file=/home/gridgain/Documents/work/incubator-ignite/work/db/node02-20092321-f30d-498f-8609-21ff87e4d104/TxLog/index.bin
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.write(FilePageStore.java:550)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.writeInternal(FilePageStoreManager.java:520)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.writePages(GridCacheDatabaseSharedManager.java:4022)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3930)
> ... 3 more
> Suppressed: java.lang.AssertionError: off=4000,
> allocated=1000, pageId=00020003,
> file=/home/gridgain/Documents/work/incubator-ignite/work/db/node02-20092321-f30d-498f-8609-21ff87e4d104/TxLog/index.bin
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.write(FilePageStore.java:550)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.writeInternal(FilePageStoreManager.java:520)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.writePages(GridCacheDatabaseSharedManager.java:4022)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3930)
> ... 3 more
> Suppressed: java.lang.AssertionError: off=2000,
> allocated=1000, pageId=00020001,
> file=/home/gridgain/Documents/work/incubator-ignite/work/db/node02-20092321-f30d-498f-8609-21ff87e4d104/TxLog/index.bin
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.write(FilePageStore.java:550)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.writeInternal(FilePageStoreManager.java:520)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.writePages(GridCacheDatabaseSharedManager.java:4022)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3930)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-2229) Full text queries do not return valid results on unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-2229: --- Labels: MakeTeamcityGreenAgain (was: ) > Full text queries do not return valid results on unstable topology > -- > > Key: IGNITE-2229 > URL: https://issues.apache.org/jira/browse/IGNITE-2229 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > > Added test > org.apache.ignite.internal.processors.cache.IgniteCacheFullTextQueryNodeJoiningSelfTest > that fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10480) [ML] Stacking for training and inference
[ https://issues.apache.org/jira/browse/IGNITE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721582#comment-16721582 ] ASF GitHub Bot commented on IGNITE-10480: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5635 > [ML] Stacking for training and inference > > > Key: IGNITE-10480 > URL: https://issues.apache.org/jira/browse/IGNITE-10480 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Artem Malykh >Priority: Major > Fix For: 2.8 > > > Stacking is an ensemble learning technique that combines multiple > classification or regression models via a meta-classifier or a > meta-regressor. The base level models are trained based on a complete > training set, then the meta-model is trained on the outputs of the base level > model as features. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10573) [ML] Consistent API for Ensemble training
[ https://issues.apache.org/jira/browse/IGNITE-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Malykh reassigned IGNITE-10573: - Assignee: Artem Malykh > [ML] Consistent API for Ensemble training > - > > Key: IGNITE-10573 > URL: https://issues.apache.org/jira/browse/IGNITE-10573 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Artem Malykh >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9328) IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write.
[ https://issues.apache.org/jira/browse/IGNITE-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9328: --- Ignite Flags: (was: Docs Required) > IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write. > -- > > Key: IGNITE-9328 > URL: https://issues.apache.org/jira/browse/IGNITE-9328 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Assignee: Stanislav Lukyanov >Priority: Major > Labels: MakeTeamcityGreenAgain > > After I have re-enabled it in IGNITE-9220 it started failing. I have also > migrated it to multiJvm. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9328) IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write.
[ https://issues.apache.org/jira/browse/IGNITE-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9328: --- Labels: MakeTeamcityGreenAgain (was: ) > IgniteDevOnlyLogTest.testDevOnlyQuietMessage() fails to write. > -- > > Key: IGNITE-9328 > URL: https://issues.apache.org/jira/browse/IGNITE-9328 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Kasnacheev >Assignee: Stanislav Lukyanov >Priority: Major > Labels: MakeTeamcityGreenAgain > > After I have re-enabled it in IGNITE-9220 it started failing. I have also > migrated it to multiJvm. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10699) Update documentation for control.sh
Sergey Antonov created IGNITE-10699:
---
Summary: Update documentation for control.sh
Key: IGNITE-10699
URL: https://issues.apache.org/jira/browse/IGNITE-10699
Project: Ignite
Issue Type: Task
Affects Versions: 2.8
Reporter: Sergey Antonov
Assignee: Artem Budnikov
I renamed view parameters in control.sh utility. The changes are following:
||Was||Has been||
|--skipZeros|--skip-zeros|
|--cacheFilter|--cache-filter|
|checkFirst|--check-first|
|checkThrough|--check-through|
|limit| --limit|
|order|--order|
|minDuration|--min-duration|
|minSize|--min-size|
|label|--label|
|nodes|--nodes|
|xid|--xid|
You could find current output command {{control.sh --cache help}}
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
The '--cache subcommand' is used to get information about and perform actions
with caches. The command has the following syntax:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
[--keystore-type KEYSTORE_TYPE] [--keystore KEYSTORE] [--keystore-password
KEYSTORE_PASSWORD] [--truststore-type TRUSTSTORE_TYPE] [--truststore
TRUSTSTORE] [--truststore-password TRUSTSTORE_PASSWORD] --cache[subcommand]
The subcommands that take [nodeId] as an argument ('list', 'contention' and
'validate_indexes') will be executed on the given node or on all server nodes
if the option is not specified. Other commands will run on a random server node.
Subcommands:
--cache list regexPattern [groups|seq] [nodeId] [--config] [--output-format
multi-line]
Show information about caches, groups or sequences that match a regular
expression. When executed without parameters, this subcommand prints the list
of caches.
Parameters:
--config - print a all configuration parameters for each cache.
--output-format multi-line - print configuration parameters per line. This
option has effect only when used with --config and without [groups|seq].
--cache contention minQueueSize [nodeId] [maxPrint]
Show the keys that are point of contention for multiple transactions.
--cache idle_verify [--dump] [--skip-zeros] [cache1,...,cacheN] [--cache-filter
ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT]
Verify counters and hash sums of primary and backup partitions for the
specified caches on an idle cluster and print out the differences, if any.
--cache validate_indexes [cache1,...,cacheN] [nodeId] [--check-first
N|--check-through K]
Validate indexes on an idle cluster and print out the keys that are missing in
the indexes.
Parameters:
--check-first N - validate only the first N keys
--check-through K - validate every Kth key
--cache distribution nodeId|null [cacheName1,...,cacheNameN] [--user-attributes
attName1,...,attrNameN]
Prints the information about partition distribution.
--cache reset_lost_partitions cacheName1,...,cacheNameN
Reset the state of lost partitions for the specified caches.{noformat}
And {{control.sh --help}}
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
Contol.sh is used to execute admin commands on cluster or get common cluster
info. The command has the following syntax:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
[--keystore-type KEYSTORE_TYPE] [--keystore KEYSTORE] [--keystore-password
KEYSTORE_PASSWORD] [--truststore-type TRUSTSTORE_TYPE] [--truststore
TRUSTSTORE] [--truststore-password TRUSTSTORE_PASSWORD] [command]
This utility can do the following commands:
Activate cluster:
control.sh --activate
Deactivate cluster:
control.sh --deactivate [--yes]
Print current cluster state:
control.sh --state
Print cluster baseline topology:
control.sh
[jira] [Updated] (IGNITE-10699) Update documentation for control.sh
[
https://issues.apache.org/jira/browse/IGNITE-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-10699:
Affects Version/s: (was: 2.8)
Fix Version/s: 2.8
Component/s: documentation
> Update documentation for control.sh
> ---
>
> Key: IGNITE-10699
> URL: https://issues.apache.org/jira/browse/IGNITE-10699
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> I renamed view parameters in control.sh utility. The changes are following:
> ||Was||Has been||
> |--skipZeros|--skip-zeros|
> |--cacheFilter|--cache-filter|
> |checkFirst|--check-first|
> |checkThrough|--check-through|
> |limit| --limit|
> |order|--order|
> |minDuration|--min-duration|
> |minSize|--min-size|
> |label|--label|
> |nodes|--nodes|
> |xid|--xid|
>
> You could find current output command {{control.sh --cache help}}
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> The '--cache subcommand' is used to get information about and perform actions
> with caches. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
> SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
> [--keystore-type KEYSTORE_TYPE] [--keystore KEYSTORE] [--keystore-password
> KEYSTORE_PASSWORD] [--truststore-type TRUSTSTORE_TYPE] [--truststore
> TRUSTSTORE] [--truststore-password TRUSTSTORE_PASSWORD] --cache[subcommand]
>
> The subcommands that take [nodeId] as an argument ('list', 'contention' and
> 'validate_indexes') will be executed on the given node or on all server nodes
> if the option is not specified. Other commands will run on a random server
> node.
> Subcommands:
>
> --cache list regexPattern [groups|seq] [nodeId] [--config] [--output-format
> multi-line]
> Show information about caches, groups or sequences that match a regular
> expression. When executed without parameters, this subcommand prints the list
> of caches.
> Parameters:
> --config - print a all configuration parameters for each cache.
> --output-format multi-line - print configuration parameters per line. This
> option has effect only when used with --config and without [groups|seq].
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
> --cache idle_verify [--dump] [--skip-zeros] [cache1,...,cacheN]
> [--cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT]
> Verify counters and hash sums of primary and backup partitions for the
> specified caches on an idle cluster and print out the differences, if any.
>
> --cache validate_indexes [cache1,...,cacheN] [nodeId] [--check-first
> N|--check-through K]
> Validate indexes on an idle cluster and print out the keys that are missing
> in the indexes.
> Parameters:
> --check-first N - validate only the first N keys
> --check-through K - validate every Kth key
>
> --cache distribution nodeId|null [cacheName1,...,cacheNameN]
> [--user-attributes attName1,...,attrNameN]
> Prints the information about partition distribution.
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.{noformat}
> And {{control.sh --help}}
> {noformat}
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> Contol.sh is used to execute admin commands on cluster or get common cluster
> info. The command has the following syntax:
> control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
> PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
> [--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
> SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
> [--keystore-type
[jira] [Commented] (IGNITE-8823) Incorrect transaction state in tx manager
[
https://issues.apache.org/jira/browse/IGNITE-8823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721565#comment-16721565
]
Andrey Kuznetsov commented on IGNITE-8823:
--
[~dpavlov], I just have rolled new master up. Also, TeamCity tests have been
re-triggered, waiting for results.
> Incorrect transaction state in tx manager
> -
>
> Key: IGNITE-8823
> URL: https://issues.apache.org/jira/browse/IGNITE-8823
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: Ignite8823ReproducerTest.java
>
>
> Reproducable by test method {{testCreateConsistencyMultithreaded}} in
> {{IgfsPrimaryMultiNodeSelfTest}} and
> {{IgfsPrimaryRelaxedConsistencyMultiNodeSelfTest}}:
> {noformat}
> 18:34:40,701][SEVERE][sys-stripe-0-#44%ignite%][GridCacheIoManager] Failed
> processing message [senderId=e273c3f8-02ed-4201-9ac8-09f9ab6a1d31,
> msg=GridNearTxPrepareResponse [pending=[],
> futId=b4df8831461-9735f9d5-79a0-47a3-a951-e62a03af71ef, miniId=1,
> dhtVer=GridCacheVersion [topVer=140816081, order=1529336085358, nodeOrder=3],
> writeVer=GridCacheVersion [topVer=140816081, order=1529336085360,
> nodeOrder=3], ownedVals=null, retVal=GridCacheReturn [v=null, cacheObj=null,
> success=true, invokeRes=true, loc=true, cacheId=0], clientRemapVer=null,
> super=GridDistributedTxPrepareResponse
> [txState=IgniteTxImplicitSingleStateImpl [init=true, recovery=false],
> part=-1, err=null, super=GridDistributedBaseMessage [ver=GridCacheVersion
> [topVer=140816081, order=1529336085224, nodeOrder=1], committedVers=null,
> rolledbackVers=null, cnt=0, super=GridCacheIdMessage [cacheId=0]
> java.lang.AssertionError: true instead of GridCacheReturnCompletableWrapper
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager.removeTxReturn(IgniteTxManager.java:1098)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.ackBackup(GridNearTxFinishFuture.java:533)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:500)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:417)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3341)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal$19.apply(GridNearTxLocal.java:3335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.processors.cache.GridCacheCompoundFuture.onDone(GridCacheCompoundFuture.java:56)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onComplete(GridNearOptimisticTxPrepareFuture.java:310)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:288)
> at
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.onDone(GridNearOptimisticTxPrepareFuture.java:78)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:144)
> at
> org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
>
[jira] [Commented] (IGNITE-9171) Use lazy mode with results pre-fetch
[
https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721548#comment-16721548
]
Ignite TC Bot commented on IGNITE-9171:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Inspections] Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2546537]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2546542buildTypeId=IgniteTests24Java8_RunAll]
> Use lazy mode with results pre-fetch
>
>
> Key: IGNITE-9171
> URL: https://issues.apache.org/jira/browse/IGNITE-9171
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Blocker
> Labels: sql-stability
> Fix For: 2.8
>
>
> Current implementation of the {{lazy}} mode always starts separate thread for
> {{MapQueryLazyWorker}}. It causes excessive overhead for requests that
> produces small results set.
> We have to begin execute query at the {{QUERY_POOL}} thread pool and fetch
> first page of the results. In case results set is bigger than one page
> {{MapQueryLazyWorker}} is started and link with {{MapNodeResults}} to handle
> next pages lazy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9836) Invalid check of ea java versions
[
https://issues.apache.org/jira/browse/IGNITE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-9836:
-
Fix Version/s: 2.8
> Invalid check of ea java versions
> -
>
> Key: IGNITE-9836
> URL: https://issues.apache.org/jira/browse/IGNITE-9836
> Project: Ignite
> Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
>
> On check of '1.8.0_192-ea' java version in ignite.sh the next messages in
> console are printed:
> {code:java}
> ./include/functions.sh: line 81: [: -lt: unary operator expected
> ./ignite.sh: line 61:
> /home/vsisko/Downloads/distr/bin/include/build-classpath.sh: No such file or
> directory
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10680) Add the ability to use existing kernel context in standalone WAL iterator
[
https://issues.apache.org/jira/browse/IGNITE-10680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721531#comment-16721531
]
ASF GitHub Bot commented on IGNITE-10680:
-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5669
> Add the ability to use existing kernel context in standalone WAL iterator
> -
>
> Key: IGNITE-10680
> URL: https://issues.apache.org/jira/browse/IGNITE-10680
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
>
> In the current implementation it's only possible to use fake kernel context
> in standalone WAL iterator. If we need to use binary meta from the running
> Ignite node we must specify binary meta directory in parameters of standalone
> WAL iterator factory. But there is a possible race with binary meta files
> read/write since binary meta received with {{MetadataUpdateProposedMessage}}
> can be written to the file and concurrently read from the same file at the
> same time. This can lead to assertions like the following:
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:305)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:121)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10103)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:117)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:251)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.binaryProcessor(StandaloneGridKernalContext.java:180)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.(StandaloneGridKernalContext.java:155)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.prepareSharedCtx(IgniteWalIteratorFactory.java:359)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.iterator(IgniteWalIteratorFactory.java:177)
> {noformat}
> To solve this we can use in standalone WAL iterator existing kernel context
> of the started node instead of creating new fake one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8558) Provide an opportunity to stop grids and cancel tasks after execution all tests
[
https://issues.apache.org/jira/browse/IGNITE-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721537#comment-16721537
]
Ignite TC Bot commented on IGNITE-8558:
---
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=2546592]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccReplicatedSqlQueriesTest.testAccountsTxSql_ClientServer_Backups2 -
0,0% fails in last 402 master runs.
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
8|https://ci.ignite.apache.org/viewLog.html?buildId=2546581]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperDiscoverySpiTest.testCustomEventsSimple1_SingleNode - 0,0% fails in
last 406 master runs.
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2546553]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousWithTransformerPartitionedSelfTest.testContinuousWithTransformerAndRegularListenerKeepBinaryAsync
- 0,0% fails in last 0 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2546642buildTypeId=IgniteTests24Java8_RunAll]
> Provide an opportunity to stop grids and cancel tasks after execution all
> tests
> ---
>
> Key: IGNITE-8558
> URL: https://issues.apache.org/jira/browse/IGNITE-8558
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Rodion
>Priority: Minor
> Fix For: 2.8
>
>
> The -IGNITE-6842- issue provides an ability gracefully shutdown all ignite
> instances by default after execution of tests. Ignite instances are stopped
> by calling the method - {{stopAllGrids}} ({{cancel = false}} is used). You
> can refer to these lines of code for the details of how the node stopped:
> {code:java|title=GridAbstractTest.java:1789}
> if (isSafeTopology()) {
> stopAllGrids(false);
> if (stopGridErr) {
> err = new RuntimeException("Not all Ignite instances has been
> stopped. " +
> "Please, see log for details.", err);
> }
> }
> {code}
> As part of IGNITE-8266 a lot of boilerplate code have been successfully
> removed. For instance,
> {code:java}
> /** {@inheritDoc} */
> @Override protected void afterTestsStopped() throws Exception {
> super.afterTestsStopped();
> stopAllGrids();
> }
> {code}
> We need to,
> * Provide the ability to override the behaviour of gracefully instance
> shutdown and use {{stopAllGirds(true)}} after all tests execution. Assume a
> new method would be introduced like {{GridAbstractTest#isSafeTopology}}, so
> the behaviour can be overridden in subclasses.
> * Remove the other boilerplate parts of the code. For instance,
> {code:java}
> /** {@inheritDoc} */
> @Override protected void afterTestsStopped() throws Exception {
> stopAllGrids(true);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10698) Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions
Yakov Zhdanov created IGNITE-10698:
--
Summary: Get rid of @MXBeanParametersNames and
@MXBeanParametersDescriptions
Key: IGNITE-10698
URL: https://issues.apache.org/jira/browse/IGNITE-10698
Project: Ignite
Issue Type: Task
Reporter: Yakov Zhdanov
Fix For: 3.0
{noformat}
@MXBeanDescription("Returns or kills transactions matching the filter
conditions.")
@MXBeanParametersNames(
{
"minDuration",
"minSize",
"prj",
"consistentIds",
"xid",
"lbRegex",
"limit",
"order",
"detailed",
"kill"
}
)
@MXBeanParametersDescriptions(
{
"Minimum duration (seconds).",
"Minimum size.",
"Projection (servers|clients).",
"Consistent ids (separated by comma).",
"Transaction XID.",
"Label regexp.",
"Limit a number of transactions collected on each node.",
"Order by DURATION|SIZE.",
"Show detailed description, otherwise only count.",
"Kill matching transactions (be careful)."
}
)
{noformat}
Above looks pretty ugly and is very error prone due to messing names and descr
order or number of strings.
I would suggest to introduce individual parameters annotations and get them via
mtd.getParamterAnnotations() at runtime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-10680) Add the ability to use existing kernel context in standalone WAL iterator
[
https://issues.apache.org/jira/browse/IGNITE-10680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-10680:
Comment: was deleted
(was: Looks good to me.
[~alex_pl], please merge.)
> Add the ability to use existing kernel context in standalone WAL iterator
> -
>
> Key: IGNITE-10680
> URL: https://issues.apache.org/jira/browse/IGNITE-10680
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
>
> In the current implementation it's only possible to use fake kernel context
> in standalone WAL iterator. If we need to use binary meta from the running
> Ignite node we must specify binary meta directory in parameters of standalone
> WAL iterator factory. But there is a possible race with binary meta files
> read/write since binary meta received with {{MetadataUpdateProposedMessage}}
> can be written to the file and concurrently read from the same file at the
> same time. This can lead to assertions like the following:
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:305)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:121)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10103)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:117)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:251)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.binaryProcessor(StandaloneGridKernalContext.java:180)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.(StandaloneGridKernalContext.java:155)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.prepareSharedCtx(IgniteWalIteratorFactory.java:359)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.iterator(IgniteWalIteratorFactory.java:177)
> {noformat}
> To solve this we can use in standalone WAL iterator existing kernel context
> of the started node instead of creating new fake one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10680) Add the ability to use existing kernel context in standalone WAL iterator
[
https://issues.apache.org/jira/browse/IGNITE-10680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721527#comment-16721527
]
Ivan Rakov commented on IGNITE-10680:
-
Looks good to me.
[~alex_pl], please merge.
> Add the ability to use existing kernel context in standalone WAL iterator
> -
>
> Key: IGNITE-10680
> URL: https://issues.apache.org/jira/browse/IGNITE-10680
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
>
> In the current implementation it's only possible to use fake kernel context
> in standalone WAL iterator. If we need to use binary meta from the running
> Ignite node we must specify binary meta directory in parameters of standalone
> WAL iterator factory. But there is a possible race with binary meta files
> read/write since binary meta received with {{MetadataUpdateProposedMessage}}
> can be written to the file and concurrently read from the same file at the
> same time. This can lead to assertions like the following:
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:305)
> at
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:121)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
> at
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10103)
> at
> org.apache.ignite.internal.processors.cache.binary.BinaryMetadataFileStore.restoreMetadata(BinaryMetadataFileStore.java:117)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:251)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.binaryProcessor(StandaloneGridKernalContext.java:180)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneGridKernalContext.(StandaloneGridKernalContext.java:155)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.prepareSharedCtx(IgniteWalIteratorFactory.java:359)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.reader.IgniteWalIteratorFactory.iterator(IgniteWalIteratorFactory.java:177)
> {noformat}
> To solve this we can use in standalone WAL iterator existing kernel context
> of the started node instead of creating new fake one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10697) [ML] Add Frequency Encoding
Aleksey Zinoviev created IGNITE-10697: - Summary: [ML] Add Frequency Encoding Key: IGNITE-10697 URL: https://issues.apache.org/jira/browse/IGNITE-10697 Project: Ignite Issue Type: New Feature Components: ml Affects Versions: 2.8 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.8 Encode the values to a fraction of all the labels. Can work with linear models if the frequency is correlated with the target value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10279) Control.sh utility unify options naming format
[
https://issues.apache.org/jira/browse/IGNITE-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721499#comment-16721499
]
ASF GitHub Bot commented on IGNITE-10279:
-
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5672
IGNITE-10279 Control.sh unify options naming and rework help.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10279
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5672.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 #5672
commit 416ff563bab57e8850f0e644619689df5bd0a44c
Author: Sergey Antonov
Date: 2018-12-14T12:57:58Z
IGNITE-10279 WIP
commit 5a6eea61a651fcdf9603501a4c25c5adb8cd6ba8
Author: Sergey Antonov
Date: 2018-12-14T13:56:25Z
IGNITE-10279 Rework join method
commit 929e595c642acb05acd4bafb4c0c6378aaefee14
Author: Sergey Antonov
Date: 2018-12-14T14:19:16Z
IGNITE-10279 Remove toString() invocation.
commit 022e274650feaf8339a13ff3b5a7cdd5995c4d04
Author: Sergey Antonov
Date: 2018-12-14T14:58:27Z
IGNITE-10279 Rework help.
> Control.sh utility unify options naming format
> --
>
> Key: IGNITE-10279
> URL: https://issues.apache.org/jira/browse/IGNITE-10279
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
>
> Now we have options in several styles:
> {noformat}
> --ping-interval
> {noformat}
> {noformat}
> --skipZeros
> {noformat}
> I think, we must unify options naming format and we should use linux like
> format, i.e. {{--word1-word2}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10691) thin clients: PY, PHP and NodeJS clients mixed up UUID taken from Java or C++ client
[
https://issues.apache.org/jira/browse/IGNITE-10691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Petroshenko reassigned IGNITE-10691:
--
Assignee: Dmitry Melnichuk
> thin clients: PY, PHP and NodeJS clients mixed up UUID taken from Java or
> C++ client
> -
>
> Key: IGNITE-10691
> URL: https://issues.apache.org/jira/browse/IGNITE-10691
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
> Fix For: 2.8
>
>
> Trying to put uuid with PY or PHP or NodeJS client and get from Java or C++
> client have different results
> Python put
> {code}
> cache = client.get_or_create_cache("UUID_PY")
> cache.put(1, UUID("d597be47-949e-475b-8918-44ca836798a3"),
> key_hint=IntObject, value_hint=UUIDObject)
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_PY");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> 5b479e94-47be-97d5-a398-6783ca441889
> {code}
> Same for C++ thin client
> And they looks like mixed up in a different order
> Python: {code}d597be47-949e-475b-8918-44ca836798a3{code}
> Java: {code}5b479e94-47be-97d5-a398-6783ca441889{code}
> For example take "ca" in 7-8 number from the end of java uuid
> On left we have "83", but in python "83" stay on right side from "ca"
> Different for "44" which is on right for Java but on left for Python
> NodeJS put
> 5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
> {code}
> cache = (await igniteClient.getOrCreateCache("UUID_JS"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
> .setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
> key = 1;
> value = [95,190,238,78,178,166,68,220,153,172,100,68,215,254,125,246];
> await cache.put(key, value);
> {code}
> Py get
> {code}
> cache = client.get_or_create_cache("UUID_JS")
> result = cache.get(1, key_hint=IntObject)
> print(result)
> {code}
> Py output
> {code}
> 5fbeee4e-b2a6-44dc-99ac-6444d7fe7df6
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_JS");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> dc44a6b2-4eee-be5f-f67d-fed74464ac99
> {code}
> PHP put
> [238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205] =
> "ee0f2fed-e07a-42dc-aa59-7f8fc7380acd"
> {code}
> $cache =
> $client->getOrCreateCache("UUID_PH")->setKeyType(ObjectType::INTEGER)->setValueType(ObjectType::UUID);
> $cache->put(1,[238,15,47,237,224,122,66,220,170,89,127,143,199,56,10,205]);
> {code}
> JS get
> {code}
> cache = (await igniteClient.getOrCreateCache("UUID_PH"))
> .setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER)
> .setValueType(ObjectType.PRIMITIVE_TYPE.UUID);
> result = (await cache.get(1));
> {code}
> JS output
> {code}
> 238 15 47 237 224 122 66 220 170 89 127 143 199 56 10 205
> {code}
> Java get
> {code}
> ClientCache cache = igniteClient.getOrCreateCache("UUID_PH");
> UUID id = cache.get(1);
> System.out.println(id);
> {code}
> Java output
> {code}
> dc427ae0-ed2f-0fee-cd0a-38c78f7f59aa
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7190) Docker Hub official repository deployment
[ https://issues.apache.org/jira/browse/IGNITE-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-7190: Assignee: Ilya Murchenko (was: Peter Ivanov) > Docker Hub official repository deployment > - > > Key: IGNITE-7190 > URL: https://issues.apache.org/jira/browse/IGNITE-7190 > Project: Ignite > Issue Type: New Feature >Reporter: Peter Ivanov >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > > Research possibility to integrate into Official Docker Hub Repositories. > Use > https://docs.docker.com/docker-hub/official_repos/#how-do-i-create-a-new-official-repository > as start. > https://docs.docker.com/docker-hub/official_repos > Official Docker Hub Git Hub repository: > * https://github.com/docker-library/official-images > * https://github.com/docker-library/docs > Examples (Apache Geode): > * [Bashbrew > file|https://github.com/docker-library/official-images/pull/3685/commits/0e34248d4b2a0ed10029577f2f50427469d6b2f4] > * [Docs|https://github.com/docker-library/docs/pull/1062] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721494#comment-16721494
]
Dmitriy Pavlov commented on IGNITE-4440:
[~kuaw26] kindly reminder
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8441) Java 9/10/11 Support [2.5-2.7]
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-8441: - Summary: Java 9/10/11 Support [2.5-2.7] (was: Java 9/10/11 Support [2.7]) > Java 9/10/11 Support [2.5-2.7] > -- > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10696) Java 9/10/11 Support [2.8]
[ https://issues.apache.org/jira/browse/IGNITE-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10696: -- Description: Enhance Apache Ignite with ability to build and run tests under JDK 9-11. (was: Enhance [Ignite Tests 2.4+ (Java 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] project with ability to run build and tests under JDK9. Fix all incoming problems so that full Run All test runs on same branches provide similar results (excluding flaky tests). Some known problems: * some current versions of used maven plugins and 3rd party dependencies are still not ready for Java 9 * some JVM options of current test build configurations require revision * scala -- both 2.10 and 2.11 currently used in building and testing do not support Java 9) > Java 9/10/11 Support [2.8] > -- > > Key: IGNITE-10696 > URL: https://issues.apache.org/jira/browse/IGNITE-10696 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.8 > > > Enhance Apache Ignite with ability to build and run tests under JDK 9-11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout
[
https://issues.apache.org/jira/browse/IGNITE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721502#comment-16721502
]
Alexey Goncharuk commented on IGNITE-9213:
--
[~sboikov], can you attach a TC bot visa please?
> CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading
> to TC timeout
> ---
>
> Key: IGNITE-9213
> URL: https://issues.apache.org/jira/browse/IGNITE-9213
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Semen Boikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments: ignite-9213-threaddump.txt
>
>
> Probability is quite low, < 5%.
> One thread gets stuck in GridCacheAdapter.lockAll(...), holding gw readlock
> and waiting for future that never completes. Another one cannot acquire gw
> writelock.
> {code}
> "test-runner-#123405%distributed.CacheLockReleaseNodeLeaveTest%" #136172
> prio=5 os_prio=0 tid=0x7f20cd3d7000 nid=0x356f
> sleeping[0x7f1eae48b000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7678)
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:970)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2195)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2082)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2595)
> - locked <0xc2e69580> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2558)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1153)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1196)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1174)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest.testLockTopologyChange(CacheLockReleaseNodeLeaveTest.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2156)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2071)
> at java.lang.Thread.run(Thread.java:745)
> "test-lock-thread-4" #136488 prio=5 os_prio=0 tid=0x7f208802a000
> nid=0x36a5 waiting on condition [0x7f1ea81c3000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.lockAll(GridCacheAdapter.java:3405)
> at
> org.apache.ignite.internal.processors.cache.CacheLockImpl.lock(CacheLockImpl.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest$3.run(CacheLockReleaseNodeLeaveTest.java:154)
> at
> org.apache.ignite.testframework.GridTestUtils$6.call(GridTestUtils.java:1254)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7132) Investigate and document Ignite Persistence usage in Docker
[ https://issues.apache.org/jira/browse/IGNITE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-7132: Assignee: Ilya Murchenko (was: Peter Ivanov) > Investigate and document Ignite Persistence usage in Docker > --- > > Key: IGNITE-7132 > URL: https://issues.apache.org/jira/browse/IGNITE-7132 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > > Inspired by the following talk: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-in-docker-Native-Persistence-td18426.html > The aim is to investigate how is better to deploy Ignite persistence in > Docker. Probably with the usage of Docker volumes: > https://docs.docker.com/engine/admin/volumes/volumes/#use-a-read-only-volume > Once the configuration option is clear the following documentation needs to > be updated: > https://apacheignite.readme.io/docs/docker-deployment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9213) CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading to TC timeout
[
https://issues.apache.org/jira/browse/IGNITE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9213:
-
Ignite Flags: (was: Docs Required)
> CacheLockReleaseNodeLeaveTest.testLockTopologyChange hangs sometimes, leading
> to TC timeout
> ---
>
> Key: IGNITE-9213
> URL: https://issues.apache.org/jira/browse/IGNITE-9213
> Project: Ignite
> Issue Type: Bug
>Reporter: Ilya Lantukh
>Assignee: Semen Boikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Attachments: ignite-9213-threaddump.txt
>
>
> Probability is quite low, < 5%.
> One thread gets stuck in GridCacheAdapter.lockAll(...), holding gw readlock
> and waiting for future that never completes. Another one cannot acquire gw
> writelock.
> {code}
> "test-runner-#123405%distributed.CacheLockReleaseNodeLeaveTest%" #136172
> prio=5 os_prio=0 tid=0x7f20cd3d7000 nid=0x356f
> sleeping[0x7f1eae48b000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7678)
> at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.onStopped(GridCacheGateway.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.blockGateways(GridCacheProcessor.java:970)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2195)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2082)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2595)
> - locked <0xc2e69580> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2558)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1153)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1196)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.stopAllGrids(GridAbstractTest.java:1174)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest.testLockTopologyChange(CacheLockReleaseNodeLeaveTest.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2156)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2071)
> at java.lang.Thread.run(Thread.java:745)
> "test-lock-thread-4" #136488 prio=5 os_prio=0 tid=0x7f208802a000
> nid=0x36a5 waiting on condition [0x7f1ea81c3000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.lockAll(GridCacheAdapter.java:3405)
> at
> org.apache.ignite.internal.processors.cache.CacheLockImpl.lock(CacheLockImpl.java:74)
> at
> org.apache.ignite.internal.processors.cache.distributed.CacheLockReleaseNodeLeaveTest$3.run(CacheLockReleaseNodeLeaveTest.java:154)
> at
> org.apache.ignite.testframework.GridTestUtils$6.call(GridTestUtils.java:1254)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions
[
https://issues.apache.org/jira/browse/IGNITE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-4890:
--
Assignee: Venky Kandaswamy
> Unable to create tables automatically because 'unconfigured columnfamily'
> error is not handled for older Cassandra versions
> ---
>
> Key: IGNITE-4890
> URL: https://issues.apache.org/jira/browse/IGNITE-4890
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
>Reporter: Venky Kandaswamy
>Assignee: Venky Kandaswamy
>Priority: Major
> Labels: patch
>
> PROBLEM:
> When running Ignite with older Cassandra versions (i.e DSE 4.8.10, Cassandra
> 2.1.6 or older), we noticed that only the first tabel in an Ignite config is
> created and the others fail with 'unconfigured columnfamily' exception.
> SUGGESTED FIX:
> It appears that the error from Cassandra is changed in newer versions to
> 'unconfigured table ...' and this is handled. The conditions checked in
> org.apache.ignite.cache.store.cassandra.common.CassandraHelper needs to be
> modified to handle the older Cassandra errors.
> We are submitting a patch to do that.
> 13:44:28,753 ERROR com.walmartlabs.qarth.ignite.tests.utils.CacheStoreHelper
> [main] - Failed to execute Cassandra CQL statement: insert into
> "test1"."blob_test2" ("key", "value") values (?,?);
> class org.apache.ignite.IgniteException: Failed to execute Cassandra CQL
> statement: insert into "test1"."blob_test2" ("key", "value") values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:163)
> at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.write(CassandraCacheStore.java:276)
> at
> com.walmartlabs.qarth.ignite.tests.cassandra.CassandraDirectPersistenceTest.blobStrategyTest(CassandraDirectPersistenceTest.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: class org.apache.ignite.IgniteException: Failed to prepare
> Cassandra CQL statement: insert into "test1"."blob_test2" ("key", "value")
> values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.prepareStatement(CassandraSessionImpl.java:615)
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:133)
> ... 27 more
> Caused by: com.datastax.driver.core.exceptions.InvalidQueryException:
> unconfigured columnfamily blob_test2
> at
>
[jira] [Updated] (IGNITE-10696) Java 9/10/11 Support [2.8]
[ https://issues.apache.org/jira/browse/IGNITE-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-10696: -- Description: Enhance Apache Ignite with ability to build, test and run under JDK 9-11. (was: Enhance Apache Ignite with ability to build and run tests under JDK 9-11.) > Java 9/10/11 Support [2.8] > -- > > Key: IGNITE-10696 > URL: https://issues.apache.org/jira/browse/IGNITE-10696 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 2.8 > > > Enhance Apache Ignite with ability to build, test and run under JDK 9-11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721495#comment-16721495
]
Dmitriy Pavlov edited comment on IGNITE-4440 at 12/14/18 3:00 PM:
--
[~prokofyev] could you please assign the issue to yourself? I've added you to
list of contributors.
was (Author: dpavlov):
[~prokofyev] could you please assign the issue to yourself. I've added you to
list of contributors.
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4440) scalar misses bcastCall() in ScalarProjectionPimp class
[
https://issues.apache.org/jira/browse/IGNITE-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721495#comment-16721495
]
Dmitriy Pavlov commented on IGNITE-4440:
[~prokofyev] could you please assign the issue to yourself. I've added you to
list of contributors.
> scalar misses bcastCall() in ScalarProjectionPimp class
> ---
>
> Key: IGNITE-4440
> URL: https://issues.apache.org/jira/browse/IGNITE-4440
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.8
>Reporter: Alexander Prokofyev
>Priority: Minor
> Labels: scala
>
> It would be nice if ScalarProjectionPimp will add also bcastCall() method to
> ClusterGroup class like it already does with
> {code}
> def bcastRun(@Nullable r: Run, @Nullable p: NF) {
> value.ignite().compute(forPredicate(p)).broadcast(toRunnable(r))
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10594) Remove 'java 8' source in indexing module, add test to regular suite
[ https://issues.apache.org/jira/browse/IGNITE-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721493#comment-16721493 ] Ilya Kasnacheev commented on IGNITE-10594: -- [~dpavlov] I have addressed all of proposed changes, please review. > Remove 'java 8' source in indexing module, add test to regular suite > > > Key: IGNITE-10594 > URL: https://issues.apache.org/jira/browse/IGNITE-10594 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > > CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest to be precise -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10695) MVCC: Fix cache API conditional update operations.
[ https://issues.apache.org/jira/browse/IGNITE-10695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-10695: -- Ignite Flags: (was: Docs Required) > MVCC: Fix cache API conditional update operations. > -- > > Key: IGNITE-10695 > URL: https://issues.apache.org/jira/browse/IGNITE-10695 > Project: Ignite > Issue Type: Bug > Components: mvcc >Affects Versions: 2.7 >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > Fix For: 2.8 > > > Operation like putIfAbsent and replace now tries to transfer Predicate > instance (filter) to remote node. > # Almost all filters can't be serialized as they do not have assigned direct > type. > # Seems, we have no enough tests and we miss remote-call case for such > operations. > # Predicate should be transferred only for "replace" operation if certain > entry provided, otherwise we should send a correct operation code and use > corresponding static filter on remote side. > # This change will break protocol compatibility. Should we bother about it? > Let's fix protocol and add tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions
[
https://issues.apache.org/jira/browse/IGNITE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721490#comment-16721490
]
Dmitriy Pavlov commented on IGNITE-4890:
[~venky1963] could you assign the issue to yourself? It will be easier for
committers to find it. Now It is unassigned but patch available.
> Unable to create tables automatically because 'unconfigured columnfamily'
> error is not handled for older Cassandra versions
> ---
>
> Key: IGNITE-4890
> URL: https://issues.apache.org/jira/browse/IGNITE-4890
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.9
>Reporter: Venky Kandaswamy
>Priority: Major
> Labels: patch
>
> PROBLEM:
> When running Ignite with older Cassandra versions (i.e DSE 4.8.10, Cassandra
> 2.1.6 or older), we noticed that only the first tabel in an Ignite config is
> created and the others fail with 'unconfigured columnfamily' exception.
> SUGGESTED FIX:
> It appears that the error from Cassandra is changed in newer versions to
> 'unconfigured table ...' and this is handled. The conditions checked in
> org.apache.ignite.cache.store.cassandra.common.CassandraHelper needs to be
> modified to handle the older Cassandra errors.
> We are submitting a patch to do that.
> 13:44:28,753 ERROR com.walmartlabs.qarth.ignite.tests.utils.CacheStoreHelper
> [main] - Failed to execute Cassandra CQL statement: insert into
> "test1"."blob_test2" ("key", "value") values (?,?);
> class org.apache.ignite.IgniteException: Failed to execute Cassandra CQL
> statement: insert into "test1"."blob_test2" ("key", "value") values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:163)
> at
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.write(CassandraCacheStore.java:276)
> at
> com.walmartlabs.qarth.ignite.tests.cassandra.CassandraDirectPersistenceTest.blobStrategyTest(CassandraDirectPersistenceTest.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: class org.apache.ignite.IgniteException: Failed to prepare
> Cassandra CQL statement: insert into "test1"."blob_test2" ("key", "value")
> values (?,?);
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.prepareStatement(CassandraSessionImpl.java:615)
> at
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:133)
> ... 27 more
> Caused by:
[jira] [Commented] (IGNITE-10376) Fail to update metadata during invocation on cache
[
https://issues.apache.org/jira/browse/IGNITE-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721491#comment-16721491
]
Sergey Chugunov commented on IGNITE-10376:
--
[~ivanan.fed],
Updating metadata never waits for PME: it is a process built on top of
discovery custom messages that are independent from PME.
Moving metadate update process from discovery thread to system pool is a wrong
way to solve the issue, don't waste your efforts.
In a nutshell it is essential to execute all updates to binary metadata in a
single-threaded fashion, so if there are any ongoing updates other threads
(e.g. executing transactions) may need to wait for current updates to finish.
First thing to do here is to figure out the exact sequence of events that lead
to metadata update hang. It may be the case that in
{{CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:685)}}
thread don't need to wait at all, and a simple additional check will fix the
deadlock.
> Fail to update metadata during invocation on cache
> ---
>
> Key: IGNITE-10376
> URL: https://issues.apache.org/jira/browse/IGNITE-10376
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Fedotov
>Assignee: Ivan Fedotov
>Priority: Major
> Labels: MakeTeamcityGreenAgain, stability, test-fail
> Fix For: 2.8
>
> Attachments: IGNITE-10376 log.txt
>
>
> BinaryObjectException exception sometimes appears in
> [testAtomicOnheapTwoBackupAsyncFullSync|https://ci.ignite.apache.org/viewLog.html?buildId=2398013=buildResultsDiv=IgniteTests24Java8_ContinuousQuery4#testNameId3300126853696550025]
> at the
> [moment|https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/query/continuous/CacheContinuousQueryOrderingEventTest.java#L371]
> of CacheEntryProcessor invocation.
> {code}class org.apache.ignite.binary.BinaryObjectException: Failed to update
> meta data for type:
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryOrderingEventTest$QueryTestValue
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.addMeta(CacheObjectBinaryProcessorImpl.java:516)
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$1.addMeta(CacheObjectBinaryProcessorImpl.java:194)
> at
> org.apache.ignite.internal.binary.BinaryContext.updateMetadata(BinaryContext.java:1332)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1815)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1150)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:831)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:787)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1438)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1482)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1228)
> at
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryOrderingEventTest$1.run(CacheContinuousQueryOrderingEventTest.java:373)
> at
> org.apache.ignite.testframework.GridTestUtils$7.call(GridTestUtils.java:1300)
> at
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84){code}
> It can be because of absence of locks in
> GridCacheMapEntry#touch(GridCacheMapEntry.java:5063).
> It seems that test does not work after integration MVCC in Continuous Query.
--
This message was
[jira] [Assigned] (IGNITE-10438) [ML] DBSCAN
[ https://issues.apache.org/jira/browse/IGNITE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Zinoviev reassigned IGNITE-10438: - Assignee: Aleksey Zinoviev > [ML] DBSCAN > --- > > Key: IGNITE-10438 > URL: https://issues.apache.org/jira/browse/IGNITE-10438 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Aleksey Zinoviev >Priority: Major > > Density-based spatial clustering of applications with noise (DBSCAN) > [wiki description|https://en.wikipedia.org/wiki/DBSCAN] > We could test this algorithm on TWO_CLASSED_IRIS and IRIS (see > MLSandboxDatasets enum) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8441) Java 9/10/11 Support [2.5-2.7]
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov closed IGNITE-8441. > Java 9/10/11 Support [2.5-2.7] > -- > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9747) [ML] Add Bernoulli Naive Bayes classifier
[ https://issues.apache.org/jira/browse/IGNITE-9747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721479#comment-16721479 ] Dmitriy Pavlov commented on IGNITE-9747: [~chief] could you please take a look? > [ML] Add Bernoulli Naive Bayes classifier > - > > Key: IGNITE-9747 > URL: https://issues.apache.org/jira/browse/IGNITE-9747 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Ravil Galeyev >Assignee: Ravil Galeyev >Priority: Major > Fix For: 2.8 > > > Naive Bayes classifiers are a family of simple probabilistic classifiers > based on applying Bayes' theorem with strong (naive) independence assumptions > between the features. > So we want to add this algorithm to Apache Ignite ML module. > [Bernoulli Naive > Bayes|http://scikit-learn.org/stable/modules/naive_bayes.html#bernoulli-naive-bayes] > implements the naive Bayes training and classification algorithms for data > that is distributed according to multivariate Bernoulli distributions; i.e., > there may be multiple features but each one is assumed to be a binary-valued > (Bernoulli, boolean) variable. > Requirements for successful PR: > # PartitionedDataset usage > # Trainer-Model paradigm support > # Tests for Model and for Trainer (and other stuff) > # Example of usage with small, but famous dataset like IRIS, Titanic or > House Prices > # Javadocs/codestyle according guidelines -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8441) Java 9/10/11 Support [2.5-2.7]
[ https://issues.apache.org/jira/browse/IGNITE-8441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov resolved IGNITE-8441. -- Resolution: Done > Java 9/10/11 Support [2.5-2.7] > -- > > Key: IGNITE-8441 > URL: https://issues.apache.org/jira/browse/IGNITE-8441 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > > Enhance [Ignite Tests 2.4+ (Java > 8)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=projectOverview] > project with ability to run build and tests under JDK9. Fix all incoming > problems so that full Run All test runs on same branches provide similar > results (excluding flaky tests). > Some known problems: > * some current versions of used maven plugins and 3rd party dependencies are > still not ready for Java 9 > * some JVM options of current test build configurations require revision > * scala -- both 2.10 and 2.11 currently used in building and testing do not > support Java 9 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
