[jira] [Assigned] (IGNITE-19382) [Ignite Website] Ignite Summit 2023_Update website banners
[ https://issues.apache.org/jira/browse/IGNITE-19382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev reassigned IGNITE-19382: -- Assignee: Erlan Aytpaev > [Ignite Website] Ignite Summit 2023_Update website banners > -- > > Key: IGNITE-19382 > URL: https://issues.apache.org/jira/browse/IGNITE-19382 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Evgenia >Assignee: Erlan Aytpaev >Priority: Major > Attachments: FB.jpg, docs.jpg, ignite-Summit.jpg > > > Update summit banners please. Places to update banners: > 1) Featured events > [Distributed Database - Apache Ignite|https://ignite.apache.org/] > 2) Doc's banner > [https://ignite.apache.org/docs/latest/] > 3) Update event page with a new image > [Apache Ignite Events - Meetups, Summit, > Conference|https://ignite.apache.org/events.html#summit] > > Also lets talk about how to move the banner on the main page upper(jn the > first screen) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19071) Update promotion banner
[ https://issues.apache.org/jira/browse/IGNITE-19071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19071. -- > Update promotion banner > --- > > Key: IGNITE-19071 > URL: https://issues.apache.org/jira/browse/IGNITE-19071 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Alexey Alexandrov >Priority: Trivial > > Upcoming Ignite summit has to be featured in documentation top banner. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (IGNITE-19145) Change text in How to start contributing section of the website
[ https://issues.apache.org/jira/browse/IGNITE-19145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erlan Aytpaev closed IGNITE-19145. -- > Change text in How to start contributing section of the website > --- > > Key: IGNITE-19145 > URL: https://issues.apache.org/jira/browse/IGNITE-19145 > Project: Ignite > Issue Type: Task > Components: website >Reporter: Kseniya Romanova >Assignee: Erlan Aytpaev >Priority: Major > > As the process changed, we need to change the text on > [https://ignite.apache.org/our-community.html#contributing] > > In the "4 Steps to Start Contributing..." change Step 02 for: If you don’t > have an [ASF JIRA|https://issues.apache.org/jira/] account, request it > [here|[https://selfserve.apache.org/jira-account.html].] > In the email sample please delete "I don’t have an ASF JIRA account. My > preferred username is [username, no hyphens allowed ]." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-11628) Document the possibility to use JAR files in UriDeploymentSpi
[
https://issues.apache.org/jira/browse/IGNITE-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YuJue Li resolved IGNITE-11628.
---
Fix Version/s: 2.9
(was: 2.16)
Resolution: Fixed
> Document the possibility to use JAR files in UriDeploymentSpi
> -
>
> Key: IGNITE-11628
> URL: https://issues.apache.org/jira/browse/IGNITE-11628
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Mekhanikov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.9
>
>
> {{UriDeploymentSpi}} got a possibility to support regular JAR files along
> with GARs in IGNITE-11380
> This possibility should be reflected in the documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-10268) Remove documentation about "replicatedOnly" flag
[ https://issues.apache.org/jira/browse/IGNITE-10268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li reassigned IGNITE-10268: - Assignee: YuJue Li (was: Artem Budnikov) > Remove documentation about "replicatedOnly" flag > > > Key: IGNITE-10268 > URL: https://issues.apache.org/jira/browse/IGNITE-10268 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: YuJue Li >Priority: Major > Fix For: 2.16 > > > SqlQuery.replicatedOnly and SqlFieldsQuery.replicatedOnly flags were > deprecated. Need to remove all places where it is mentioned from docs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-10895) MVCC: Document several modes of pessimistic transactions are allowed for MVCC caches.
[ https://issues.apache.org/jira/browse/IGNITE-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li resolved IGNITE-10895. --- Fix Version/s: (was: 2.16) Resolution: Won't Fix > MVCC: Document several modes of pessimistic transactions are allowed for MVCC > caches. > - > > Key: IGNITE-10895 > URL: https://issues.apache.org/jira/browse/IGNITE-10895 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Roman Kondakov >Priority: Major > > It is need to document that for MVCC caches optimistic transactions are > prohibited as before, but there are several isolation levels are allowed now: > * READ COMMITTED > * REPEATABLE READ > * SERIALIZABLE > Actually all these levels have the same implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-10895) MVCC: Document several modes of pessimistic transactions are allowed for MVCC caches.
[ https://issues.apache.org/jira/browse/IGNITE-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719093#comment-17719093 ] YuJue Li commented on IGNITE-10895: --- MVCC is deprecated. > MVCC: Document several modes of pessimistic transactions are allowed for MVCC > caches. > - > > Key: IGNITE-10895 > URL: https://issues.apache.org/jira/browse/IGNITE-10895 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Roman Kondakov >Priority: Major > Fix For: 2.16 > > > It is need to document that for MVCC caches optimistic transactions are > prohibited as before, but there are several isolation levels are allowed now: > * READ COMMITTED > * REPEATABLE READ > * SERIALIZABLE > Actually all these levels have the same implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-10977) Document unsupported clear() call for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YuJue Li resolved IGNITE-10977.
---
Fix Version/s: (was: 2.16)
Resolution: Won't Fix
> Document unsupported clear() call for MVCC caches
> -
>
> Key: IGNITE-10977
> URL: https://issues.apache.org/jira/browse/IGNITE-10977
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
>
> Now MVCC caches don't support {{cache.clear()}} by design. So let's document
> it as a known limitations (I suppose we should have such page on readme.io)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-10977) Document unsupported clear() call for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719091#comment-17719091
]
YuJue Li commented on IGNITE-10977:
---
MVCC is deprecated.
> Document unsupported clear() call for MVCC caches
> -
>
> Key: IGNITE-10977
> URL: https://issues.apache.org/jira/browse/IGNITE-10977
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.16
>
>
> Now MVCC caches don't support {{cache.clear()}} by design. So let's document
> it as a known limitations (I suppose we should have such page on readme.io)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-10741) MVCC: Document disabled page evictions for in-memory MVCC caches.
[
https://issues.apache.org/jira/browse/IGNITE-10741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YuJue Li resolved IGNITE-10741.
---
Fix Version/s: (was: 2.16)
Resolution: Won't Fix
> MVCC: Document disabled page evictions for in-memory MVCC caches.
> -
>
> Key: IGNITE-10741
> URL: https://issues.apache.org/jira/browse/IGNITE-10741
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Roman Kondakov
>Priority: Major
>
> Currently data pages evictions are disabled for {{TRANSACTIONAL_SNAPSHOT}}
> caches because it can cause violations for repeatable read guarantees.
> User should either disable evictions or enable persistence in such cases.
> We should reflect it in our documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-10741) MVCC: Document disabled page evictions for in-memory MVCC caches.
[
https://issues.apache.org/jira/browse/IGNITE-10741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719090#comment-17719090
]
YuJue Li commented on IGNITE-10741:
---
MVCC is deprecated.
> MVCC: Document disabled page evictions for in-memory MVCC caches.
> -
>
> Key: IGNITE-10741
> URL: https://issues.apache.org/jira/browse/IGNITE-10741
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Roman Kondakov
>Priority: Major
> Fix For: 2.16
>
>
> Currently data pages evictions are disabled for {{TRANSACTIONAL_SNAPSHOT}}
> caches because it can cause violations for repeatable read guarantees.
> User should either disable evictions or enable persistence in such cases.
> We should reflect it in our documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19313) Update IgniteReleasedVersion for compatibility tests to 2.15.0
[ https://issues.apache.org/jira/browse/IGNITE-19313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-19313: --- Fix Version/s: 2.16 > Update IgniteReleasedVersion for compatibility tests to 2.15.0 > -- > > Key: IGNITE-19313 > URL: https://issues.apache.org/jira/browse/IGNITE-19313 > Project: Ignite > Issue Type: Sub-task >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Update IgniteReleasedVersion for compatibility tests to 2.15.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19416) Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) fails
[ https://issues.apache.org/jira/browse/IGNITE-19416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-19416: --- Fix Version/s: 2.16 > Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) > fails > - > > Key: IGNITE-19416 > URL: https://issues.apache.org/jira/browse/IGNITE-19416 > Project: Ignite > Issue Type: Bug >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.16 > > Time Spent: 10m > Remaining Estimate: 0h > > Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) > always fails after IGNITE-17449 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19416) Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) fails
Aleksey Plekhanov created IGNITE-19416: -- Summary: Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) fails Key: IGNITE-19416 URL: https://issues.apache.org/jira/browse/IGNITE-19416 Project: Ignite Issue Type: Bug Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Test JavaThinCompatibilityTest.testCurrentClientToOldServer(Version 2.14.0) always fails after IGNITE-17449 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19415) GridCommandHandlerTest should be runnable at other modules
Anton Vinogradov created IGNITE-19415: - Summary: GridCommandHandlerTest should be runnable at other modules Key: IGNITE-19415 URL: https://issues.apache.org/jira/browse/IGNITE-19415 Project: Ignite Issue Type: Improvement Reporter: Anton Vinogradov Assignee: Anton Vinogradov Snapshot tests use `CommandHandler()` which logs into control-utility module log path, this cause failures at extended tests at other modules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19415) GridCommandHandlerTest should be runnable at other modules
[ https://issues.apache.org/jira/browse/IGNITE-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-19415: -- Fix Version/s: 2.16 > GridCommandHandlerTest should be runnable at other modules > -- > > Key: IGNITE-19415 > URL: https://issues.apache.org/jira/browse/IGNITE-19415 > Project: Ignite > Issue Type: Improvement >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.16 > > > Snapshot tests use `CommandHandler()` which logs into control-utility module > log path, this cause failures at extended tests at other modules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19314) Release 2.15
[ https://issues.apache.org/jira/browse/IGNITE-19314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-19314: --- Fix Version/s: 2.15 (was: 2.16) > Release 2.15 > > > Key: IGNITE-19314 > URL: https://issues.apache.org/jira/browse/IGNITE-19314 > Project: Ignite > Issue Type: Task >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.15 > > > This is umbrella ticket for 2.15 release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19414) ignite-website: Add documentation, release notes and download links for 2.15.0 release
Aleksey Plekhanov created IGNITE-19414: -- Summary: ignite-website: Add documentation, release notes and download links for 2.15.0 release Key: IGNITE-19414 URL: https://issues.apache.org/jira/browse/IGNITE-19414 Project: Ignite Issue Type: Sub-task Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Add documentation, release notes and download links for 2.15.0 release to Ignite website -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19414) ignite-website: Add documentation, release notes and download links for 2.15.0 release
[ https://issues.apache.org/jira/browse/IGNITE-19414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-19414: --- Fix Version/s: 2.15 > ignite-website: Add documentation, release notes and download links for > 2.15.0 release > -- > > Key: IGNITE-19414 > URL: https://issues.apache.org/jira/browse/IGNITE-19414 > Project: Ignite > Issue Type: Sub-task >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.15 > > > Add documentation, release notes and download links for 2.15.0 release to > Ignite website -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11064) Add documentation for enabling cache statistics only on appropriate nodes.
[ https://issues.apache.org/jira/browse/IGNITE-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11064: --- Fix Version/s: 2.16 (was: 2.15) > Add documentation for enabling cache statistics only on appropriate nodes. > -- > > Key: IGNITE-11064 > URL: https://issues.apache.org/jira/browse/IGNITE-11064 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Evgeny Stanilovsky >Priority: Major > Fix For: 2.16 > > > System property: IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE (false > default) will disable statistic collecting even if statisticsEnabled flag is > true. > [IGNITE-10172|https://issues.apache.org/jira/browse/IGNITE-10172] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11020) Document edge-chasing deadlock detection
[ https://issues.apache.org/jira/browse/IGNITE-11020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11020: --- Fix Version/s: 2.16 (was: 2.15) > Document edge-chasing deadlock detection > > > Key: IGNITE-11020 > URL: https://issues.apache.org/jira/browse/IGNITE-11020 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Ivan Pavlukhin >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > > Documentation for deadlock detection implemented in related ticket is needed. > Initially detection was implemented for MVCC caches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11060) Add documentation about CacheInterceptor.
[ https://issues.apache.org/jira/browse/IGNITE-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11060: --- Fix Version/s: 2.16 (was: 2.15) > Add documentation about CacheInterceptor. > - > > Key: IGNITE-11060 > URL: https://issues.apache.org/jira/browse/IGNITE-11060 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > > I didn't find documentation about CacheInterceptor in > [https://apacheignite.readme.io/] > (search request [https://apacheignite.readme.io/v2.7/search?q=interceptor] ) > I think we should document this feature. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10979) Add documentation for control.sh idle_verify --check-crc
[ https://issues.apache.org/jira/browse/IGNITE-10979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10979: --- Fix Version/s: 2.16 (was: 2.15) > Add documentation for control.sh idle_verify --check-crc > > > Key: IGNITE-10979 > URL: https://issues.apache.org/jira/browse/IGNITE-10979 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Major > Labels: ise > Fix For: 2.16 > > > We should document new option --check-crc in control.sh idle_verify command. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10845) Ignite Production Readiness Section Enhancement
[ https://issues.apache.org/jira/browse/IGNITE-10845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10845: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Production Readiness Section Enhancement > --- > > Key: IGNITE-10845 > URL: https://issues.apache.org/jira/browse/IGNITE-10845 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.16 > > > Enhance Ignite production readiness section with points from here: > https://www.gridgain.com/resources/blog/checklist-assembling-your-first-apacher-ignitetm-cluster -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Alex Plehanov updated IGNITE-6526: -- Fix Version/s: 2.16 (was: 2.15) > 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 A. Magda >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-11252) Docs: Index corruption recovery procedure
[ https://issues.apache.org/jira/browse/IGNITE-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11252: --- Fix Version/s: 2.16 (was: 2.15) > Docs: Index corruption recovery procedure > - > > Key: IGNITE-11252 > URL: https://issues.apache.org/jira/browse/IGNITE-11252 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Denis A. Magda >Assignee: Prachi Garg >Priority: Critical > Fix For: 2.16 > > > We need to document a recovery procedure if an index corruption happens. > Refer to this thread for details and examples of the exception dumped to the > logs if the issue occurs: > http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-index-corruption-issue-gt-unrecoverable-cluster-td39869.html > # Recovering from an index corruption > ## Applicable if > It is known that an index of a cache is corrupted, but the main data > (partition files and WAL) is fine. Show code snippets of possible examples. > Find via the references shared in the dev list discussion. > ## Steps to recover > 1. Stop the node > 2. Delete index.bin of the affected caches (path is > db//cache-/index.bin) > 3. Start the node > - Note: At this point the node is active in the cluster but don’t have > indexes. > It means that it serves SQL queries but their performance can be low. > Avoid running SQL queries on large tables at this point > 4. Wait for message “Finished indexes rebuilding for cache ” in > the Ignite log > # Recovering from a persistent storage corruption > ## Applicable if > A part of the persistent storage (partition files, checkpoint markers or WAL) > was corrupted > and there is no other way to recover it, but there are healthy copies of all > data on other nodes. > ## Steps to recover > 1. Stop the node > 2. Delete all persistence files of the node (best to clear Ignite working > directory, storage directory, WAL and WAL archive directories) > 3. Make sure consistentId is explicitly set in the configuration of the node > - If it isn’t, lookup the generated consistentId using control.sh and set it > explicitly in the config or via IGNITE_CONSISTENT_ID (2.8+ only) > 4. Start the node > 5. Wait for messages for all caches -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11965) Pyton client: Expiration policies are missed
[ https://issues.apache.org/jira/browse/IGNITE-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11965: --- Fix Version/s: 2.16 (was: 2.15) > Pyton client: Expiration policies are missed > > > Key: IGNITE-11965 > URL: https://issues.apache.org/jira/browse/IGNITE-11965 > Project: Ignite > Issue Type: Bug > Components: documentation, thin client >Affects Versions: 2.7, 2.7.5 >Reporter: Andrei Aleksandrov >Priority: Major > Fix For: 2.16 > > > [https://apacheignite.readme.io/docs/expiry-policies] are missed but > [https://apacheignite.readme.io/docs/expiry-policies#section-eager-ttl] can > be set. > Should be added. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10741) MVCC: Document disabled page evictions for in-memory MVCC caches.
[
https://issues.apache.org/jira/browse/IGNITE-10741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-10741:
---
Fix Version/s: 2.16
(was: 2.15)
> MVCC: Document disabled page evictions for in-memory MVCC caches.
> -
>
> Key: IGNITE-10741
> URL: https://issues.apache.org/jira/browse/IGNITE-10741
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Roman Kondakov
>Priority: Major
> Fix For: 2.16
>
>
> Currently data pages evictions are disabled for {{TRANSACTIONAL_SNAPSHOT}}
> caches because it can cause violations for repeatable read guarantees.
> User should either disable evictions or enable persistence in such cases.
> We should reflect it in our documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-10649) Add documentation for control.sh about SSL
[
https://issues.apache.org/jira/browse/IGNITE-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-10649:
---
Fix Version/s: 2.16
(was: 2.15)
> Add documentation for control.sh about SSL
> --
>
> Key: IGNITE-10649
> URL: https://issues.apache.org/jira/browse/IGNITE-10649
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Priority: Major
> Fix For: 2.16
>
>
> Control.sh help output:
> {noformat}
> Control.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_PROTOCOL_N]]
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
> [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
> [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
> [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
> [--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 --baseline
> Add nodes into baseline topology:
> control.sh --baseline add consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Remove nodes from baseline topology:
> control.sh --baseline remove consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Set baseline topology:
> control.sh --baseline set consistentId1[,consistentId2,,consistentIdN]
> [--yes]
> Set baseline topology based on version:
> control.sh --baseline version topologyVersion [--yes]
> List or kill transactions:
> control.sh --tx [--xid XID] [--min-duration SECONDS] [--min-size SIZE]
> [--label PATTERN_REGEX] [--servers|--clients] [--nodes
> consistentId1[,consistentId2,,consistentIdN]] [--limit NUMBER] [--order
> DURATION|SIZE|START_TIME] [--kill] [--yes]
> Print absolute paths of unused archived wal segments on each node:
> control.sh --wal print [consistentId1,consistentId2,,consistentIdN]
> Delete unused archived wal segments on each node:
> control.sh --wal delete [consistentId1,consistentId2,,consistentIdN]
> [--yes]
> View caches information in a cluster. For more details type:
> control.sh --cache help
> By default commands affecting the cluster require interactive confirmation.
> Use --yes option to disable it.
> Default values:
> HOST_OR_IP=127.0.0.1
> PORT=11211
> PING_INTERVAL=5000
> PING_TIMEOUT=3
> SSL_PROTOCOL=TLS
> SSL_KEY_ALGORITHM=SunX509
> KEYSTORE_TYPE=JKS
> TRUSTSTORE_TYPE=JKS
> Exit codes:
> 0 - successful execution.
> 1 - invalid arguments.
> 2 - connection failed.
> 3 - authentication failed.
> 4 - unexpected error.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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
]
Alex Plehanov updated IGNITE-10699:
---
Fix Version/s: 2.16
(was: 2.15)
> Update documentation for control.sh
> ---
>
> Key: IGNITE-10699
> URL: https://issues.apache.org/jira/browse/IGNITE-10699
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.16
>
>
> 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|
> |servers|--servers|
> |clients|--clients|
> |minDuration|--min-duration|
> |minSize|--min-size|
> |label|--label|
> |nodes|--nodes|
> |xid|--xid|
> |kill|--kill|
> |groups|--groups|
> |seq|--seq|
>
> 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_PROTOCOL_N]],
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]],
> [--ssl-key-algorithm SSL_KEY_ALGORITHM], [--keystore-type KEYSTORE_TYPE],
> [--keystore KEYSTORE_PATH], [--keystore-password KEYSTORE_PASSWORD],
> [--truststore-type TRUSTSTORE_TYPE], [--truststore TRUSTSTORE_PATH],
> [--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 attrName1,...,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,
[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 ] Alex Plehanov updated IGNITE-9406: -- Fix Version/s: 2.16 (was: 2.15) > 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.16 > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-10947) CPP: Fix documentation on how to build Ignite C++ on Linux
[
https://issues.apache.org/jira/browse/IGNITE-10947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-10947:
---
Fix Version/s: 2.16
(was: 2.15)
> CPP: Fix documentation on how to build Ignite C++ on Linux
> --
>
> Key: IGNITE-10947
> URL: https://issues.apache.org/jira/browse/IGNITE-10947
> Project: Ignite
> Issue Type: Improvement
> Components: documentation, platforms
>Reporter: Igor Sapego
>Priority: Major
> Fix For: 2.16
>
>
> We now have build step (IGNITE-10940) that performs following steps during
> release of the binary package of the Ignite:
> {code}
> # libtoolize
> # aclocal
> # autoheader
> # automake --add-missing
> # autoreconf
> {code}
> So we now should change documentation, that users only need to run following
> commands to build Ignite C++ from binary distribution of Ignite.
> {code}
> # ./configure
> # make
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13525) Ignite Docs: detect and fix broken cross-links
[ https://issues.apache.org/jira/browse/IGNITE-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13525: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: detect and fix broken cross-links > -- > > Key: IGNITE-13525 > URL: https://issues.apache.org/jira/browse/IGNITE-13525 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.16 > > > It's highly likely that some of the references/links used in the docs are > broken or point out to unreachable places. > We need to use some tool that can check all the deployed pages and report > broken references if any: > https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10895) MVCC: Document several modes of pessimistic transactions are allowed for MVCC caches.
[ https://issues.apache.org/jira/browse/IGNITE-10895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10895: --- Fix Version/s: 2.16 (was: 2.15) > MVCC: Document several modes of pessimistic transactions are allowed for MVCC > caches. > - > > Key: IGNITE-10895 > URL: https://issues.apache.org/jira/browse/IGNITE-10895 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Roman Kondakov >Priority: Major > Fix For: 2.16 > > > It is need to document that for MVCC caches optimistic transactions are > prohibited as before, but there are several isolation levels are allowed now: > * READ COMMITTED > * REPEATABLE READ > * SERIALIZABLE > Actually all these levels have the same implementation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11187) Additional documentation for re-balancing is canceled if client node joins.
[ https://issues.apache.org/jira/browse/IGNITE-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11187: --- Fix Version/s: 2.16 (was: 2.15) > Additional documentation for re-balancing is canceled if client node joins. > --- > > Key: IGNITE-11187 > URL: https://issues.apache.org/jira/browse/IGNITE-11187 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Evgeny Stanilovsky >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > > Need additional documentation for [IGNITE-7165] Re-balancing is canceled if > client node joins. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12368) .NET: Make sure units are specified in documentation where applicable
[ https://issues.apache.org/jira/browse/IGNITE-12368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-12368: --- Fix Version/s: 2.16 (was: 2.15) > .NET: Make sure units are specified in documentation where applicable > - > > Key: IGNITE-12368 > URL: https://issues.apache.org/jira/browse/IGNITE-12368 > Project: Ignite > Issue Type: Improvement > Components: documentation, platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.16 > > > Units are missing in some docs. For example, XMLDoc for > DataRegionConfiguration does not specify that MaxSize is in bytes: > https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Configuration.DataRegionConfiguration.html > Check entire documentation and add units where needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-4221) Document ComputeJobMasterLeaveAware interface usage
[ https://issues.apache.org/jira/browse/IGNITE-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-4221: -- Fix Version/s: 2.16 (was: 2.15) > 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 A. Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.16 > > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-11427) Document custom node fail functional.
[ https://issues.apache.org/jira/browse/IGNITE-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11427: --- Fix Version/s: 2.16 (was: 2.15) > Document custom node fail functional. > - > > Key: IGNITE-11427 > URL: https://issues.apache.org/jira/browse/IGNITE-11427 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.7 >Reporter: Evgeny Stanilovsky >Priority: Critical > Fix For: 2.16 > > Attachments: Screenshot_20190227_100539.png > > > Append additional node fail documentation related to [1] > [1] https://issues.apache.org/jira/browse/IGNITE-11332 > > how it looks into jconsole: > !Screenshot_20190227_100539.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10710) Document new REST API for baseline topology command.
[ https://issues.apache.org/jira/browse/IGNITE-10710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10710: --- Fix Version/s: 2.16 (was: 2.15) > Document new REST API for baseline topology command. > > > Key: IGNITE-10710 > URL: https://issues.apache.org/jira/browse/IGNITE-10710 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.8 >Reporter: Andrey Novikov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-9758) Document data injection via the REST API
[
https://issues.apache.org/jira/browse/IGNITE-9758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-9758:
--
Fix Version/s: 2.16
(was: 2.15)
> Document data injection via the REST API
>
>
> Key: IGNITE-9758
> URL: https://issues.apache.org/jira/browse/IGNITE-9758
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.6
>Reporter: Pavel Petroshenko
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.16
>
>
> There should a documentation on how to post data via the REST API.
>
> Just to capture what was proposed by [~ilyak] over email:
>
> {quote}REST API will convert complex BinaryObjects into JSON by default. But
> to put such objects via REST you will need to define your own
> ConnectorMessageInterceptor and plug it in. You will need to define string to
> entity mapping in onReceive. You can leave onSend returning arg.
>
> This interface should be used:
> [https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ConnectorMessageInterceptor.html].
> You need to put it into ConnectorConfiguration, which you should put into
> IgniteConfiguration.{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 ] Alex Plehanov updated IGNITE-9716: -- Fix Version/s: 2.16 (was: 2.15) > 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: control.sh, documentation >Affects Versions: 2.7 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.16 > > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-10977) Document unsupported clear() call for MVCC caches
[
https://issues.apache.org/jira/browse/IGNITE-10977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-10977:
---
Fix Version/s: 2.16
(was: 2.15)
> Document unsupported clear() call for MVCC caches
> -
>
> Key: IGNITE-10977
> URL: https://issues.apache.org/jira/browse/IGNITE-10977
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Priority: Major
> Fix For: 2.16
>
>
> Now MVCC caches don't support {{cache.clear()}} by design. So let's document
> it as a known limitations (I suppose we should have such page on readme.io)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-10887) .NET: Align .Net docs with Java
[ https://issues.apache.org/jira/browse/IGNITE-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10887: --- Fix Version/s: 2.16 (was: 2.15) > .NET: Align .Net docs with Java > --- > > Key: IGNITE-10887 > URL: https://issues.apache.org/jira/browse/IGNITE-10887 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Priority: Critical > Fix For: 2.16 > > > It seems that the .Net docs are a bit outdated compared to Java ones. > Need to align .Net and Java docs. .Net pages which are not specific to the > platform should be replaced with a simple link to the Java docs. The docs > that have .Net-specific things (e.g. code examples) should be reworked. > The pages with issues > - Performnace Tips page > (https://apacheignite-net.readme.io/docs/performance-tips) > - Off-heap memory (https://apacheignite-net.readme.io/docs/off-heap-memory) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[
https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-12943:
---
Fix Version/s: 2.16
(was: 2.15)
> Document how to filter out metrics from registries
> --
>
> Key: IGNITE-12943
> URL: https://issues.apache.org/jira/browse/IGNITE-12943
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis A. Magda
>Priority: Major
> Labels: IEP-35
> Fix For: 2.16
>
>
> As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter
> out metrics for a specific exporter instance. For instance, this is how we
> can ask a JMX exporter instance to ignore the cache metrics:
> {code}
> JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi();
> jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»));
> cfg.setMetricExporterSpi(jmxSpi);
> {code}
> We should add {{Metrics Filtering}} section to this documentation page [1]
> explaining how to use the filtering. Also, I would clarify in the
> {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out
> certain metrics from a specific exporter.
> Also, should we possibly rename the method to
> {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear?
> [1] https://apacheignite.readme.io/docs/new-metrics
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 ] Alex Plehanov updated IGNITE-7704: -- Fix Version/s: 2.16 (was: 2.15) > 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 >Priority: Major > Fix For: 2.16 > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-10268) Remove documentation about "replicatedOnly" flag
[ https://issues.apache.org/jira/browse/IGNITE-10268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10268: --- Fix Version/s: 2.16 (was: 2.15) > Remove documentation about "replicatedOnly" flag > > > Key: IGNITE-10268 > URL: https://issues.apache.org/jira/browse/IGNITE-10268 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > > SqlQuery.replicatedOnly and SqlFieldsQuery.replicatedOnly flags were > deprecated. Need to remove all places where it is mentioned from docs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11729) Low description for lost policy functional
[
https://issues.apache.org/jira/browse/IGNITE-11729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11729:
---
Fix Version/s: 2.16
(was: 2.15)
> Low description for lost policy functional
> --
>
> Key: IGNITE-11729
> URL: https://issues.apache.org/jira/browse/IGNITE-11729
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.7
>Reporter: ARomantsov
>Priority: Major
> Fix For: 2.16
>
>
> Current description in
> https://apacheignite.readme.io/docs/partition-loss-policies seems not covered
> persistence case and text description is not clear
> Probably we need to transform it into two tables (in-memory, persistence)
> Rows - cache_write, cache_read, cache_remove,sql_read, sql_write
> Columns - READ_ONLY_SAFE ,READ_ONLY_ALL, READ_WRITE_SAFE, etc
> {code:java}
> Policies
> Ignite supports the following PartitionLossPolicies:
> READ_ONLY_SAFE - all writes to a cache/table will fail with an exception.
> Reads will only be allowed for entries belonging to survived/alive
> partitions. Reads from lost partitions will fail with an exception.
> READ_ONLY_ALL - reads are allowed from any partition including the lost ones.
> An exception is thrown in an attempt to write to any partition. The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> READ_WRITE_SAFE - all reads and writes are allowed for entries in
> survived/alive partitions. All reads and writes of entries belonging to the
> lost partitions will fail with an exception.
> READ_WRITE_ALL - all reads and writes will proceed as if all partitions were
> in a consistent state (as if no partition loss happened). The result of
> reading from a lost partition is undefined and may be different on different
> nodes in the cluster.
> IGNORE - this mode never marks a lost partition as lost, pretending that no
> partition loss has happened and clearing the partition loss state right away.
> Technically, the partition will not be added to the collection of
> lostPartitions which is the main difference from READ_WRITE_ALL mode. IGNORE
> mode is used by default.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13611) Ignite Docs: Port Compute Grid/Checkpointing docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13611: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Port Compute Grid/Checkpointing docs from readme.io > > > Key: IGNITE-13611 > URL: https://issues.apache.org/jira/browse/IGNITE-13611 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Fix For: 2.16 > > > The content in the link below is missing from the new version of the document. > https://apacheignite.readme.io/docs/checkpointing -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Alex Plehanov updated IGNITE-9485: -- Fix Version/s: 2.16 (was: 2.15) > 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 >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-9091) IEP-25: creating documentation
[ https://issues.apache.org/jira/browse/IGNITE-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-9091: -- Fix Version/s: 2.16 (was: 2.15) > IEP-25: creating documentation > -- > > Key: IGNITE-9091 > URL: https://issues.apache.org/jira/browse/IGNITE-9091 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alex Volkov >Assignee: Artem Budnikov >Priority: Major > Labels: iep-25 > Fix For: 2.16 > > > It would be great to have proper documentation for IEP-25: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-25:+Partition+Map+Exchange+hangs+resolving] > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11057) Document new SQL system view "CACHE_GROUPS_IO"
[
https://issues.apache.org/jira/browse/IGNITE-11057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11057:
---
Fix Version/s: 2.16
(was: 2.15)
> Document new SQL system view "CACHE_GROUPS_IO"
> --
>
> Key: IGNITE-11057
> URL: https://issues.apache.org/jira/browse/IGNITE-11057
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.16
>
>
> See
> {{modules\indexing\src\main\java\org\apache\ignite\internal\processors\query\h2\sys\view\SqlSystemViewCacheGroupsIOStatistics.java}}
> # {{GROUP_ID}} - cache group ID
> # {{GROUP_ID}} - cache group name
> # {{PHYSICAL_READS}} - number of physical reads (i.e. block read from disk)
> for the given group
> # {{LOGICAL_READS}} - number of logical reads (i.e. from buffer cache) for
> the given group.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-9547) Document DML operations prohibited inside transaction
[ https://issues.apache.org/jira/browse/IGNITE-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-9547: -- Fix Version/s: 2.16 (was: 2.15) > Document DML operations prohibited inside transaction > - > > Key: IGNITE-9547 > URL: https://issues.apache.org/jira/browse/IGNITE-9547 > Project: Ignite > Issue Type: Task > Components: documentation, sql >Reporter: Yury Gerzhedovich >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > > Docs says: > ""Presently, DML supports the atomic mode only meaning that if there is a DML > query that is executed as a part of an Ignite transaction then it will not be > enlisted in the transaction's writing queue and will be executed right away"" > However it's wrong. > We need to document that now any DML operations is prohibited and throw > Exception in case it will be executed inside a transaction. > > Also appeared new boolean property IGNITE_ALLOW_DML_INSIDE_TRANSACTION. it is > necessary to emulate the old behavior. In case value is true then DML > operation is allowed, but it be applied only after transaction will be > commited. > By default value is false. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13528) Ignite Docs: port generic instructions for Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-13528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13528: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: port generic instructions for Kubernetes > - > > Key: IGNITE-13528 > URL: https://issues.apache.org/jira/browse/IGNITE-13528 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.16 > > > The legacy readme.io-based docs had these generic instructions that didn't > make it to the new docs engine: > https://apacheignite.readme.io/docs/generic-configuration > We need to merge all those pages into a single documentation page "Generic > Kubernetes Deployment" that needs to be placed under the "Installation" -> > "Kubernetes" section of the new docs: > https://ignite.apache.org/docs/latest/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches and --cache-filter
[
https://issues.apache.org/jira/browse/IGNITE-11076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11076:
---
Fix Version/s: 2.16
(was: 2.15)
> Add documentation for control.sh idle_verify --exclude-caches and
> --cache-filter
>
>
> Key: IGNITE-11076
> URL: https://issues.apache.org/jira/browse/IGNITE-11076
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Labels: ise
> Fix For: 2.16
>
>
> control.sh cache --help output
> {noformat}
> 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_PROTOCOL_N]]
> [--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
> [--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
> [--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
> [--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
> [--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 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].
> --groups - print information about groups.
> --seq - print information about sequences.
>
> --cache contention minQueueSize [nodeId] [maxPrint]
> Show the keys that are point of contention for multiple transactions.
>
> --cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches
> cacheName1,...,cacheNameN)|(--cache-filter
> ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN]
> 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.
> Parameters:
> --check-crc - check the CRC-sum of pages stored on disk before verifying data
> consistency in partitions between primary and backup nodes.
>
> --cache validate_indexes [cacheName1,...,cacheNameN] [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 attrName1,...,attrNameN]
> Prints the information about partition distribution.
>
> --cache reset_lost_partitions cacheName1,...,cacheNameN
> Reset the state of lost partitions for the specified caches.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[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 ] Alex Plehanov updated IGNITE-8411: -- Fix Version/s: 2.16 (was: 2.15) > 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 >Assignee: Igor Sapego >Priority: Major > Fix For: 2.16 > > > 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 (v8.20.10#820010)
[jira] [Updated] (IGNITE-9984) Documentation for EVT_MANAGEMENT_TASK_STARTED will be required.
[
https://issues.apache.org/jira/browse/IGNITE-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-9984:
--
Fix Version/s: 2.16
(was: 2.15)
> Documentation for EVT_MANAGEMENT_TASK_STARTED will be required.
> ---
>
> Key: IGNITE-9984
> URL: https://issues.apache.org/jira/browse/IGNITE-9984
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.8
>Reporter: Andrei Aleksandrov
>Priority: Major
> Fix For: 2.16
>
>
> New EVT_MANAGEMENT_TASK_STARTED will be added in future release.
> Documentation for it should be added too.
> Next information should be added to web console and visor documentation:
> EVT_MANAGEMENT_TASK_STARTED provide the possibility to track next tasks that
> could be started by the user from web console and visor during some
> operations:
> +Baseline:+
> VisorBaselineTask - Task that will collect information about baseline
> topology and can change its state
> +Binaries:+
> VisorBinaryMetadataCollectorTask - Task that collects binary metadata.
> +Services:+
> VisorCancelServiceTask - Task for cancel services with the specified name.
> +Metrics:+
> VisorComputeResetMetricsTask - Task for cancel services with specified name.
> +Caches:+
> VisorCacheLostPartitionsTask - Collect list of lost partitions.
> VisorCacheResetLostPartitionsTask - Reset lost partitions for caches.
> VisorCacheStartTask - Task that start cache or near cache with specified
> configuration.
> VisorCacheStopTask - Task that stop specified caches on specified node.
> VisorCacheAffinityNodeTask - Task that will find affinity node for key.
> VisorCacheModifyTask - Task that modify value in specified cache.
> VisorCacheRebalanceTask - Pre-loads caches. Made callable just to conform
> common pattern.
> VisorCacheLoadTask - Task to loads caches.
> VisorCacheClearTask - Task that clears specified caches on specified node.
> +Queries+:
> VisorQueryResetMetricsTask - Reset compute grid query metrics.
> VisorQueryTask - Task for executing SQL fields query and get the first page
> of results.
> VisorQueryCancelTask - Task to cancel queries.
> +Computes:+
> VisorComputeResetMetricsTask - Reset compute grid metrics.
> VisorComputeCancelSessionsTask - Cancels given tasks sessions.
> +DEBUG:+
> VisorThreadDumpTask - Creates a thread dump.
> +IGFS:+
> VisorIgfsFormatTask - Format IGFS instance.
> VisorIgfsProfilerClearTask - Remove all IGFS profiler logs.
> VisorIgfsResetMetricsTask - Resets IGFS metrics.
> +LOGS:+
> VisorLogSearchTask - Search text matching in logs
> +CLUSTER:+
> VisorChangeGridActiveStateTask - Task for changing grid active state.
> VisorNodeGcTask - Task to run gc on nodes.
> VisorNodeRestartTask - Restarts nodes.
> VisorNodeStopTask - Stops nodes.
>
> {color:#33}
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
[ https://issues.apache.org/jira/browse/IGNITE-11487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11487: --- Fix Version/s: 2.16 (was: 2.15) > Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property > - > > Key: IGNITE-11487 > URL: https://issues.apache.org/jira/browse/IGNITE-11487 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-9856) Update documentation for control.sh --cache list
[
https://issues.apache.org/jira/browse/IGNITE-9856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-9856:
--
Fix Version/s: 2.16
(was: 2.15)
> Update documentation for control.sh --cache list
>
>
> Key: IGNITE-9856
> URL: https://issues.apache.org/jira/browse/IGNITE-9856
> Project: Ignite
> Issue Type: Improvement
> Components: control.sh, documentation
>Reporter: Sergey Antonov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.16
>
>
> {{Documentation for option --cache list in control.sh}} must be updated.
> As reference could be used help message:
> {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]
> --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] [--skipZeros] [cache1,...,cacheN]
> 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] [checkFirst
> N|checkThrough K]
> Validate indexes on an idle cluster and print out the keys that are
> missing in the indexes.
> Parameters:
> checkFirst N- validate only the first N keys
> checkThrough 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 output example:
> {noformat}
> control.sh --cache list .* --config --yes
> Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
> 2018 Copyright(C) Apache Software Foundation
> User: santonov
>
> ignite-sys-cache: [name=ignite-sys-cache, grpName=null, mode=REPLICATED,
> atomicityMode=TRANSACTIONAL, eagerTtl=true,
> writeSynchronizationMode=FULL_SYNC, invalidate=false,
> maxConcurrentAsyncOps=500, interceptor=null, dfltLockTimeout=0,
> affinityCfg=VisorCacheAffinityConfiguration
> [function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction,
> mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper,
> partitionedBackups=2147483647, partitions=100, exclNeighbors=false],
> rebalanceCfg=VisorCacheRebalanceConfiguration [mode=SYNC, batchSize=524288,
> partitionedDelay=0, throttle=0, timeout=1, batchesPrefetchCnt=2,
> rebalanceOrder=-2], evictCfg=VisorCacheEvictionConfiguration [plc=null,
> plcMaxSize=null, filter=null], nearCfg=VisorCacheNearConfiguration
> [nearEnabled=false, nearStartSize=0, nearEvictPlc=null,
> nearEvictMaxSize=null], storeCfg=VisorCacheStoreConfiguration
> [jdbcStore=false, store=null, storeFactory=null, readThrough=false,
> writeThrough=false,
[jira] [Updated] (IGNITE-10880) Document how we should evolve our persistence functionality while keeping it compatible with files created by old versions
[ https://issues.apache.org/jira/browse/IGNITE-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10880: --- Fix Version/s: 2.16 (was: 2.15) > Document how we should evolve our persistence functionality while keeping it > compatible with files created by old versions > -- > > Key: IGNITE-10880 > URL: https://issues.apache.org/jira/browse/IGNITE-10880 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Eduard Shangareev >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.16 > > > It's not documented at all (???). > We need complete documentation to not break compatibility with previously > created database files while updating/evolving code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10581) Document new flag to filter cache types in control.sh
[ https://issues.apache.org/jira/browse/IGNITE-10581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10581: --- Fix Version/s: 2.16 (was: 2.15) > Document new flag to filter cache types in control.sh > - > > Key: IGNITE-10581 > URL: https://issues.apache.org/jira/browse/IGNITE-10581 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Artem Budnikov >Priority: Major > Fix For: 2.16 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13821) Explain how to include a scope into another tracing scope
[ https://issues.apache.org/jira/browse/IGNITE-13821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13821: --- Fix Version/s: 2.16 (was: 2.15) > Explain how to include a scope into another tracing scope > - > > Key: IGNITE-13821 > URL: https://issues.apache.org/jira/browse/IGNITE-13821 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.16 > > > The documentation explains how to activate a tracing scope: > https://ignite.apache.org/docs/latest/monitoring-metrics/tracing#using-control-script > Also, it's feasible to include another scope inside of a primary one. For > instance, you can ask to include the communication scope into the tx scope. > [Refer to this article in > Russian|https://habr.com/ru/company/gridgain/blog/528836/] for details, > search for the "Мы также можем увеличить степень детализации трейсинга > транзакций, включив трейсинг коммуникационного протокола." occurrence in the > text after which it's show how to include one scope inside of another. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-10846) Improve docs for "Disabling WAL Archiving"
[ https://issues.apache.org/jira/browse/IGNITE-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-10846: --- Fix Version/s: 2.16 (was: 2.15) > Improve docs for "Disabling WAL Archiving" > -- > > Key: IGNITE-10846 > URL: https://issues.apache.org/jira/browse/IGNITE-10846 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Prachi Garg >Assignee: Artem Budnikov >Priority: Critical > Fix For: 2.16 > > > Provide pros and cons of disabling WAL Archiving. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13585) Ignite Docs: Port AWS and GCE deployment docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13585: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Port AWS and GCE deployment docs from readme.io > > > Key: IGNITE-13585 > URL: https://issues.apache.org/jira/browse/IGNITE-13585 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.16 > > > We forgot to port the following pages from readme: > * AWS Deployment: https://apacheignite.readme.io/docs/aws-deployment > * GCE Deployment: > https://apacheignite.readme.io/docs/google-compute-deployment > * RPM installation instructions: > https://apacheignite.readme.io/docs/rpm-and-deb-setup > Move the pages to the new docs and update the references on the Ignite > downloads page sot that they point to the new docs: > https://ignite.apache.org/download.cgi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18496) Handle documentation feedback
[ https://issues.apache.org/jira/browse/IGNITE-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-18496: --- Fix Version/s: 2.16 (was: 2.15) > Handle documentation feedback > - > > Key: IGNITE-18496 > URL: https://issues.apache.org/jira/browse/IGNITE-18496 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Igor Gusev >Assignee: Igor Gusev >Priority: Major > Fix For: 2.16 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We have had bugyard for a while, and there is a lot of useful feedback on > documentation. Its time to go through it and fix all issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11628) Document the possibility to use JAR files in UriDeploymentSpi
[
https://issues.apache.org/jira/browse/IGNITE-11628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11628:
---
Fix Version/s: 2.16
(was: 2.15)
> Document the possibility to use JAR files in UriDeploymentSpi
> -
>
> Key: IGNITE-11628
> URL: https://issues.apache.org/jira/browse/IGNITE-11628
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Mekhanikov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.16
>
>
> {{UriDeploymentSpi}} got a possibility to support regular JAR files along
> with GARs in IGNITE-11380
> This possibility should be reflected in the documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-11184) add example of ssl rest protocol on ignite
[ https://issues.apache.org/jira/browse/IGNITE-11184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11184: --- Fix Version/s: 2.16 (was: 2.15) > add example of ssl rest protocol on ignite > -- > > Key: IGNITE-11184 > URL: https://issues.apache.org/jira/browse/IGNITE-11184 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.7 >Reporter: ARomantsov >Priority: Critical > Fix For: 2.16 > > > Add information about ssl Jetty configuration to ignite documentation about > restApi > https://apacheignite.readme.io/docs/rest-api#sample-jetty-xml-configuration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13523) Ignite Docs: the "layout: toc" tag no longer produces a table of content
[ https://issues.apache.org/jira/browse/IGNITE-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13523: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: the "layout: toc" tag no longer produces a table of content > > > Key: IGNITE-13523 > URL: https://issues.apache.org/jira/browse/IGNITE-13523 > Project: Ignite > Issue Type: Bug > Components: documentation, website >Reporter: Denis A. Magda >Priority: Major > Labels: new-docs > Fix For: 2.16 > > > The "layout: toc" tag that is used on some index pages of a given section is > not taken into account during the HTML generation process. > For instance, the tag is set in sources for this page: > https://github.com/apache/ignite/blob/master/docs/_docs/security/index.adoc > But the TOC is not produced for the HTML output: > https://ignite.apache.org/docs/latest/security/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13529) Ignite Docs: create docs for OpenShift installation
[ https://issues.apache.org/jira/browse/IGNITE-13529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13529: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: create docs for OpenShift installation > --- > > Key: IGNITE-13529 > URL: https://issues.apache.org/jira/browse/IGNITE-13529 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Critical > Labels: new-docs > Fix For: 2.16 > > > We need to create docs specific for OpenShift deployments. Check with > GridGain contributors if GridGain is ready to donate the content of the page > below to Ignite: > https://www.gridgain.com/docs/latest/installation-guide/kubernetes/openshift-deployment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12575) Document @IgniteExperimental annotation
[ https://issues.apache.org/jira/browse/IGNITE-12575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-12575: --- Fix Version/s: 2.16 (was: 2.15) > Document @IgniteExperimental annotation > --- > > Key: IGNITE-12575 > URL: https://issues.apache.org/jira/browse/IGNITE-12575 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.8 >Reporter: Alexey Goncharuk >Priority: Major > Fix For: 2.16 > > > We introduced the annotation to mark APIs which are exposed to users to try > out new features, but the APIs are likely to evolve in the future. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11694) Add documentation for SqlFieldsQuery.updateBatchSize into thin clients docs
[
https://issues.apache.org/jira/browse/IGNITE-11694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11694:
---
Fix Version/s: 2.16
(was: 2.15)
> Add documentation for SqlFieldsQuery.updateBatchSize into thin clients docs
> ---
>
> Key: IGNITE-11694
> URL: https://issues.apache.org/jira/browse/IGNITE-11694
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Priority: Major
> Fix For: 2.16
>
>
> The property {{SqlFieldsQuery.updateBatchSize}} is introduced by the patch
> IGNITE-11499.
> ODBC, thin JDBC, thin client documentation should be changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13651) Ignite Docs: Port Apache Zeppelin docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13651: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Port Apache Zeppelin docs from readme.io > - > > Key: IGNITE-13651 > URL: https://issues.apache.org/jira/browse/IGNITE-13651 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Minor > Labels: new-docs > Fix For: 2.16 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite-sql.readme.io/docs/apache-zeppelin] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13918) Ignite Docs: Port Capacity Planning docs from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13918: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Port Capacity Planning docs from readme.io > --- > > Key: IGNITE-13918 > URL: https://issues.apache.org/jira/browse/IGNITE-13918 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: documentation > Fix For: 2.16 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite.readme.io/docs/capacity-planning] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19314) Release 2.15
[ https://issues.apache.org/jira/browse/IGNITE-19314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-19314: --- Fix Version/s: 2.16 (was: 2.15) > Release 2.15 > > > Key: IGNITE-19314 > URL: https://issues.apache.org/jira/browse/IGNITE-19314 > Project: Ignite > Issue Type: Task >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Fix For: 2.16 > > > This is umbrella ticket for 2.15 release process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-14212) New web documentation promotion
[ https://issues.apache.org/jira/browse/IGNITE-14212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-14212: --- Fix Version/s: 2.16 (was: 2.15) > New web documentation promotion > --- > > Key: IGNITE-14212 > URL: https://issues.apache.org/jira/browse/IGNITE-14212 > Project: Ignite > Issue Type: Wish > Components: documentation >Reporter: Anton Vinogradov >Assignee: Mauricio Stekl >Priority: Critical > Fix For: 2.16 > > > Since AI documentation hosting changed (from > https://apacheignite.readme.io/docs to https://ignite.apache.org/docs) a lot > of people faced with nonrelevant search results problems. > Could we > 1) Promote a new site https://ignite.apache.org/docs to have it on the first > page of google results? > 2) Have pop-up with proposal to go to the new site at > https://apacheignite.readme.io/docs? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11630) Document changes to SQL views
[
https://issues.apache.org/jira/browse/IGNITE-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11630:
---
Fix Version/s: 2.16
(was: 2.15)
> Document changes to SQL views
> -
>
> Key: IGNITE-11630
> URL: https://issues.apache.org/jira/browse/IGNITE-11630
> Project: Ignite
> Issue Type: Task
> Components: documentation, sql
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.16
>
>
> The following changes were made to our views.
> {{CACHE_GROUPS}}
> # {{ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{LOCAL_CACHE_GROUPS_IO}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{CACHES}}
> # {{NAME}} -> {{CACHE_NAME}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{INDEXES}}
> # {{GROUP_ID}} -> {{CACHE_GROUP_ID}}
> # {{GROUP_NAME}} -> {{CACHE_GROUP_NAME}}
> {{NODES}}
> # {{ID}} -> {{NODE_ID}}
> {{TABLES}}
> # Added {{CACHE_GROUP_ID}}
> # Added {{CACHE_GROUP_NAME}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13851) Document persistence forward compatibility policy
[ https://issues.apache.org/jira/browse/IGNITE-13851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13851: --- Fix Version/s: 2.16 (was: 2.15) > Document persistence forward compatibility policy > - > > Key: IGNITE-13851 > URL: https://issues.apache.org/jira/browse/IGNITE-13851 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Nikita A. Safonov >Priority: Major > Fix For: 2.16 > > > We have a policy that you can upgrade from 2.x to 2.y, y > x, while keeping > your persistence files. > Let's document that fact. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11768) CPP documentation:mention default BinaryType methods implementation
[ https://issues.apache.org/jira/browse/IGNITE-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-11768: --- Fix Version/s: 2.16 (was: 2.15) > CPP documentation:mention default BinaryType methods implementation > --- > > Key: IGNITE-11768 > URL: https://issues.apache.org/jira/browse/IGNITE-11768 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.7 >Reporter: Igor Sapego >Priority: Major > Labels: cpp > Fix For: 2.16 > > > Mention BinaryTypeDefaultHashing, BinaryTypeNonNullableType and > BinaryTypeDefaultAll classes introduced in IGNITE-11703 in documentation. > Also, use them where it is possible and appropriate in code snippets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-11789) Document changes of LRT diagnostic messages made in IGNITE-11392
[
https://issues.apache.org/jira/browse/IGNITE-11789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-11789:
---
Fix Version/s: 2.16
(was: 2.15)
> Document changes of LRT diagnostic messages made in IGNITE-11392
>
>
> Key: IGNITE-11789
> URL: https://issues.apache.org/jira/browse/IGNITE-11789
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Chudov
>Priority: Major
> Fix For: 2.16
>
>
> When LRT is detected, in the case if it is active, local node creates a
> request to near (client) node to get the dump of a thread that created the
> transaction. Dump of the client node appears in server node log.
> There is new property in org.apache.ignite.mxbean.TransactionsMXBean class
> that shows is thread dumps requesting allowed or disallowed:
> *TxOwnerDumpRequestsAllowed*
> By default, dump requests are turned on.
> Log messages look like following:
> {code:java}
> Dumping the near node thread that started transaction [xidVer=]
> Stack trace of the transaction owner thread:
>
> {code}
> In case of client error or error while trying to read result:
> {code:java}
> Could not get thread dump from transaction owner near node:
> {code}
> In case of error while trying to send request:
> {code:java}
> Could not send dump request to transaction owner near node:
>
> {code}
> In case if client is already out of topology:
> {code:java}
> Could not get thread dump from transaction owner because near node is now out
> of topology. Node ID: {code}
> In case if client does not support this feature:
> {code:java}
> Could not send dump request to transaction owner near node: node does not
> support this feature.
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13688) Ignite Docs: Port Checkpointing Mapping from readme.io
[ https://issues.apache.org/jira/browse/IGNITE-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-13688: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Port Checkpointing Mapping from readme.io > - > > Key: IGNITE-13688 > URL: https://issues.apache.org/jira/browse/IGNITE-13688 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.9 >Reporter: YuJue Li >Priority: Major > Labels: new-docs > Fix For: 2.16 > > > The content in the link below is missing from the new version of the document: > [https://apacheignite.readme.io/docs/continuous-mapping] > [https://apacheignite.readme.io/docs/checkpointing] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-13524) Ignite Docs: fix Jekyll warnings reported during docs transformation to HTML
[
https://issues.apache.org/jira/browse/IGNITE-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Plehanov updated IGNITE-13524:
---
Fix Version/s: 2.16
(was: 2.15)
> Ignite Docs: fix Jekyll warnings reported during docs transformation to HTML
>
>
> Key: IGNITE-13524
> URL: https://issues.apache.org/jira/browse/IGNITE-13524
> Project: Ignite
> Issue Type: Bug
> Components: documentation
>Reporter: Denis A. Magda
>Priority: Major
> Labels: new-docs
> Fix For: 2.16
>
>
> Try to build the docs with the `run.sh` command located in the docs' root
> folder:
> https://github.com/apache/ignite/tree/master/docs
> Jekyll will report many warnings that need to be reviewed and handled. Some
> of the warnings are printed below:
> {noformat}
> There is an empty tab (C#/.NET) on the JDBC Driver page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/JDBC/jdbc-driver.adoc
> There is an empty tab (C++) on the JDBC Driver page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/JDBC/jdbc-driver.adoc
> There is an empty tab (C++) on the SQL Performance Tuning page:
> /Users/dmagda/ignite-website/_docs/_docs/SQL/sql-tuning.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C++) on the Baseline Topology page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/baseline-topology.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C++) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C#/.NET) on the Connecting Client Nodes page:
> /Users/dmagda/ignite-website/_docs/_docs/clustering/connect-client-nodes.adoc
> There is an empty tab (C++) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> There is an empty tab (C#/.NET) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> There is an empty tab (C++) on the Deploying User Code page:
> /Users/dmagda/ignite-website/_docs/_docs/code-deployment/deploying-user-code.adoc
> asciidoctor: WARNING: : line 56: id assigned to anchor already in use:
> readfrombackup
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C#/.NET) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> There is an empty tab (C++) on the Partition Loss Policy page:
> /Users/dmagda/ignite-website/_docs/_docs/configuring-caches/partition-loss-policy.adoc
> asciidoctor: ERROR: configuration.adoc: line 3: level 0 sections can only be
> used when doctype is book
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> Improper use of Lexer#lex - this method does not receive options. This will
> become an error in a future version.
> There is an empty tab (C#/.NET) on
[jira] [Updated] (IGNITE-14694) .NET: Update documentation links in README, add README to NuGet
[ https://issues.apache.org/jira/browse/IGNITE-14694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-14694: --- Fix Version/s: 2.16 (was: 2.15) > .NET: Update documentation links in README, add README to NuGet > --- > > Key: IGNITE-14694 > URL: https://issues.apache.org/jira/browse/IGNITE-14694 > Project: Ignite > Issue Type: Improvement > Components: documentation, platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Trivial > Labels: .NET > Fix For: 2.16 > > > * README.md has links to old docs: > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet > * Add README to the NuGet package > https://devblogs.microsoft.com/nuget/add-a-readme-to-your-nuget-package/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16949) Update documantaion links for spring-data examples and code snippets
[ https://issues.apache.org/jira/browse/IGNITE-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-16949: --- Fix Version/s: 2.16 (was: 2.15) > Update documantaion links for spring-data examples and code snippets > > > Key: IGNITE-16949 > URL: https://issues.apache.org/jira/browse/IGNITE-16949 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Fix For: 2.16 > > > Some of the examples of the spring-data code snippents and links to the > examples are out of date after the spring-data modules removal. > These documentation pages must be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19378) Ignite Docs: Remove docs related to lazy loading
[ https://issues.apache.org/jira/browse/IGNITE-19378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-19378: --- Fix Version/s: 2.16 (was: 2.15) > Ignite Docs: Remove docs related to lazy loading > > > Key: IGNITE-19378 > URL: https://issues.apache.org/jira/browse/IGNITE-19378 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.15 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Blocker > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > Because of SqlFieldQuery's lazy flag is deprecated and the default value is > set to true, related docs should be deleted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16189) Improve getting started section for Ignite C++
[ https://issues.apache.org/jira/browse/IGNITE-16189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-16189: --- Fix Version/s: 2.16 (was: 2.15) > Improve getting started section for Ignite C++ > -- > > Key: IGNITE-16189 > URL: https://issues.apache.org/jira/browse/IGNITE-16189 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ivan Daschinsky >Assignee: Nikita A. Safonov >Priority: Major > Fix For: 2.16 > > > 1. Lets separate building steps and examples for Ignite.C++ (thick client) > and thin client > 2. Lets remove ODBC (UnixODBC) and OpenSSL dependency for Ignite.C++. > 3. Lets remove JDK dependency for thin client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19407) Sql. Introduce DDL command for ALTER COLUMN TYPE.
[
https://issues.apache.org/jira/browse/IGNITE-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-19407:
--
Description:
Introduce DDL command class.
Implement command validation logic.
Pass command to the CatalogService via DdlHandler.
Validator should allow changing column DEFAULT and changing column type for the
next cases
{noformat}
INT8 -> INT16 -> INT32 -> INT64
FLOAT -> DOUBLE
DECIMAL(10,5) -> DECIMAL(15, 5) // increasing precision only
VARCHAR(10) -> VARCHAR(20)
VARBINARY(10) -> VARBINARY(20)
NOT NULL -> NULLABLE
{noformat}
was:
Introduce DDL command class.
Implement command validation logic.
Pass command to the CatalogService via DdlHandler.
Validator should allow changing column DEFAULT and changing column type for the
next cases
{noformat}
INT8 -> INT16 -> INT32 -> INT64
FLOAT -> DOUBLE
DECIMAL(10,5) -> DECIMAL(15, 5) // increasing precision only
VARCHAR(10) -> VARCHAR(20)
VARBINARY(10) -> VARBINARY(20)
NOT NULL -> NULLABLE
{noformat}
> Sql. Introduce DDL command for ALTER COLUMN TYPE.
> -
>
> Key: IGNITE-19407
> URL: https://issues.apache.org/jira/browse/IGNITE-19407
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> Introduce DDL command class.
> Implement command validation logic.
> Pass command to the CatalogService via DdlHandler.
> Validator should allow changing column DEFAULT and changing column type for
> the next cases
> {noformat}
> INT8 -> INT16 -> INT32 -> INT64
> FLOAT -> DOUBLE
> DECIMAL(10,5) -> DECIMAL(15, 5) // increasing precision only
> VARCHAR(10) -> VARCHAR(20)
> VARBINARY(10) -> VARBINARY(20)
>NOT NULL -> NULLABLE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19407) Sql. Introduce DDL command for ALTER COLUMN TYPE.
[
https://issues.apache.org/jira/browse/IGNITE-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-19407:
--
Description:
Introduce DDL command class.
Implement command validation logic.
Pass command to the CatalogService via DdlHandler.
Validator should allow changing column DEFAULT and changing column type for the
next cases
{noformat}
INT8 -> INT16 -> INT32 -> INT64
FLOAT -> DOUBLE
DECIMAL(10,5) -> DECIMAL(15, 5) // increasing precision only
VARCHAR(10) -> VARCHAR(20)
VARBINARY(10) -> VARBINARY(20)
NOT NULL -> NULLABLE
{noformat}
was:
Introduce DDL command class.
Implement command validation logic.
Pass command to the CatalogService via DdlHandler.
> Sql. Introduce DDL command for ALTER COLUMN TYPE.
> -
>
> Key: IGNITE-19407
> URL: https://issues.apache.org/jira/browse/IGNITE-19407
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> Introduce DDL command class.
> Implement command validation logic.
> Pass command to the CatalogService via DdlHandler.
> Validator should allow changing column DEFAULT and changing column type for
> the next cases
> {noformat}
> INT8 -> INT16 -> INT32 -> INT64
> FLOAT -> DOUBLE
> DECIMAL(10,5) -> DECIMAL(15, 5) // increasing precision only
> VARCHAR(10) -> VARCHAR(20)
> VARBINARY(10) -> VARBINARY(20)
> NOT NULL -> NULLABLE
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19407) Sql. Introduce DDL command for ALTER COLUMN TYPE.
[ https://issues.apache.org/jira/browse/IGNITE-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19407: -- Description: Introduce DDL command class. Implement command validation logic. Pass command to the CatalogService via DdlHandler. was:Create DDL command class, validate and pass it to Catalog. > Sql. Introduce DDL command for ALTER COLUMN TYPE. > - > > Key: IGNITE-19407 > URL: https://issues.apache.org/jira/browse/IGNITE-19407 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Introduce DDL command class. > Implement command validation logic. > Pass command to the CatalogService via DdlHandler. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19413) Ignite 3.0: Change column type feature
[ https://issues.apache.org/jira/browse/IGNITE-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19413: -- Ignite Flags: (was: Docs Required,Release Notes Required) > Ignite 3.0: Change column type feature > -- > > Key: IGNITE-19413 > URL: https://issues.apache.org/jira/browse/IGNITE-19413 > Project: Ignite > Issue Type: Epic > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > > Implement ALTER COLUMN ddl commands to change column type and column defaults. > It includes: > # Describe parser grammar for the DDL commands. > # Transparent row upgrading from prev to the next schema version. > # Optimizations, exploiting compatibility between previous and next schema > versions. > # Support simplest cases at least like constraint relaxation and/or type > widening. > # Support asynchronous data validation for type narrowing or constraint > hardening. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19407) Sql. Introduce DDL command for ALTER COLUMN TYPE.
[ https://issues.apache.org/jira/browse/IGNITE-19407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19407: -- Epic Link: IGNITE-19413 > Sql. Introduce DDL command for ALTER COLUMN TYPE. > - > > Key: IGNITE-19407 > URL: https://issues.apache.org/jira/browse/IGNITE-19407 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Create DDL command class, validate and pass it to Catalog. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19413) Ignite 3.0: Change column type feature
[ https://issues.apache.org/jira/browse/IGNITE-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19413: -- Description: Implement ALTER COLUMN ddl commands to change column type and column defaults. It includes: # Describe parser grammar for the DDL commands. # Transparent row upgrading from prev to the next schema version. # Optimizations, exploiting compatibility between previous and next schema versions. # Support simplest cases at least like constraint relaxation and/or type widening. # Support asynchronous data validation for type narrowing or constraint hardening. was:Implement ALTER COLUMN ddl commands > Ignite 3.0: Change column type feature > -- > > Key: IGNITE-19413 > URL: https://issues.apache.org/jira/browse/IGNITE-19413 > Project: Ignite > Issue Type: Epic > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > > Implement ALTER COLUMN ddl commands to change column type and column defaults. > It includes: > # Describe parser grammar for the DDL commands. > # Transparent row upgrading from prev to the next schema version. > # Optimizations, exploiting compatibility between previous and next schema > versions. > # Support simplest cases at least like constraint relaxation and/or type > widening. > # Support asynchronous data validation for type narrowing or constraint > hardening. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18831) Sql. Dynamic parameters. Inferred types of dynamic parameters are not used by the execution runtime.
[
https://issues.apache.org/jira/browse/IGNITE-18831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Zhuravkov reassigned IGNITE-18831:
-
Assignee: Maksim Zhuravkov
> Sql. Dynamic parameters. Inferred types of dynamic parameters are not used by
> the execution runtime.
>
>
> Key: IGNITE-18831
> URL: https://issues.apache.org/jira/browse/IGNITE-18831
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Maksim Zhuravkov
>Assignee: Maksim Zhuravkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required, ignite-3
> Fix For: 3.0.0-beta2
>
>
> At the moment the execution runtime is not aware of dynamic parameter types
> inferred at the validation stage and when the validation stage completes
> those types are thrown away. During the execution, the runtime uses the
> _java_class_ of a type parameter to perform an operation, which fails in the
> following case:
> A query has a dynamic parameter (string) but the validator, by using implicit
> cast rules inferred, the actual type for that dynamic parameter to be some
> another type that can be implicitly created from a string.
> {code:java}
> CREATE TABLE UUIDS (id INTEGER PRIMARY KEY, uuid_key UUID);
> INSERT INTO UUIDS VALUES(1, ?);
> {code}
> * Execution runtime loses type information of the dynamic parameter and
> assumes it to be a string.
> * At the runtime toInternal call is going to fail, because it expects the
> type of this parameter to be UUID but dynamic parameter contains a string.
> *Solution*
> Use Sql-based RelDataTypes for parameter types and pass them among with
> parameters to the execution runtime.
> We should use Sql-based RelDataTypes instead of JavaDataTypes, because the
> latter are always nullable and that may cause the optimizer to choose a
> suboptimal plan.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19413) Ignite 3.0: Change column type feature
[ https://issues.apache.org/jira/browse/IGNITE-19413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19413: -- Description: Implement ALTER COLUMN ddl commands > Ignite 3.0: Change column type feature > -- > > Key: IGNITE-19413 > URL: https://issues.apache.org/jira/browse/IGNITE-19413 > Project: Ignite > Issue Type: Epic > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > > Implement ALTER COLUMN ddl commands -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19406) Sql. Support ALTER TABLE ALTER COLUMN TYPE.
[
https://issues.apache.org/jira/browse/IGNITE-19406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-19406:
--
Description:
Describe ALTER COLUMN grammar for SQL query parser.
Describe expected behaviour in tests.
SQL API example:
{noformat}
ALTER TABLE ALTER COLUMN 'mycolumn' DEFAULT 10;
ALTER TABLE ALTER COLUMN 'mycolumn' TYPE LONG ;
ALTER TABLE ALTER COLUMN 'mycolumn' TYPE INTEGER DEFAULT -1;
ALTER TABLE ALTER COLUMN 'mycolumn' TYPE INTEGER NULLABLE;
ALTER TABLE ALTER COLUMN 'mycolumn' TYPE LONG NOT NULL DEFAULT -1;
{noformat}
was:
Fix SQL parser.
Add tests.
> Sql. Support ALTER TABLE ALTER COLUMN TYPE.
> ---
>
> Key: IGNITE-19406
> URL: https://issues.apache.org/jira/browse/IGNITE-19406
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
>
> Describe ALTER COLUMN grammar for SQL query parser.
> Describe expected behaviour in tests.
> SQL API example:
> {noformat}
> ALTER TABLE ALTER COLUMN 'mycolumn' DEFAULT 10;
> ALTER TABLE ALTER COLUMN 'mycolumn' TYPE LONG ;
> ALTER TABLE ALTER COLUMN 'mycolumn' TYPE INTEGER DEFAULT -1;
> ALTER TABLE ALTER COLUMN 'mycolumn' TYPE INTEGER NULLABLE;
> ALTER TABLE ALTER COLUMN 'mycolumn' TYPE LONG NOT NULL DEFAULT -1;
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19406) Sql. Support ALTER TABLE ALTER COLUMN TYPE.
[ https://issues.apache.org/jira/browse/IGNITE-19406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-19406: -- Epic Link: IGNITE-19413 > Sql. Support ALTER TABLE ALTER COLUMN TYPE. > --- > > Key: IGNITE-19406 > URL: https://issues.apache.org/jira/browse/IGNITE-19406 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Fix SQL parser. > Add tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-19413) Ignite 3.0: Change column type feature
Andrey Mashenkov created IGNITE-19413: - Summary: Ignite 3.0: Change column type feature Key: IGNITE-19413 URL: https://issues.apache.org/jira/browse/IGNITE-19413 Project: Ignite Issue Type: Epic Components: sql Reporter: Andrey Mashenkov -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19315) Validate node configuration on node start
[ https://issues.apache.org/jira/browse/IGNITE-19315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Gagarkin reassigned IGNITE-19315: -- Assignee: Ivan Gagarkin > Validate node configuration on node start > - > > Key: IGNITE-19315 > URL: https://issues.apache.org/jira/browse/IGNITE-19315 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Aleksandr >Assignee: Ivan Gagarkin >Priority: Critical > Labels: ignite-3 > > After the changes made in IGNITE-19152, the configuration validation is no > longer performed on node start (see ItSslConfigurationValidationTest). > It's not clear where the validation should be applied, as it could be either > in ConfigurationChanger or LocalFileConfigurationStorage. > Additionally, we need to write more tests to ensure that the validation works > as expected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19293) Validate cluster configuration before cluster initialization
[ https://issues.apache.org/jira/browse/IGNITE-19293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Gagarkin reassigned IGNITE-19293: -- Assignee: Ivan Gagarkin > Validate cluster configuration before cluster initialization > > > Key: IGNITE-19293 > URL: https://issues.apache.org/jira/browse/IGNITE-19293 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Assignee: Ivan Gagarkin >Priority: Major > Labels: ignite-3 > > We need to validate cluster configration before start cluster initialization > process. In case when cluster configration is not valid, initialization > shouldn't start and error with explanation should be returned. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19165) ConfigurationVisitor should know about annotations of configuration fields
[ https://issues.apache.org/jira/browse/IGNITE-19165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Gagarkin reassigned IGNITE-19165: -- Assignee: Ivan Gagarkin > ConfigurationVisitor should know about annotations of configuration fields > -- > > Key: IGNITE-19165 > URL: https://issues.apache.org/jira/browse/IGNITE-19165 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Gagarkin >Assignee: Ivan Gagarkin >Priority: Critical > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > org.apache.ignite.internal.configuration.tree.ConfigurationVisitor#visitLeafNode > knows only about the key and the value of the configuration field. It would > be useful to add information about annotations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19228) Schema validation during tx processing: common framework
[ https://issues.apache.org/jira/browse/IGNITE-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Puchkovskiy reassigned IGNITE-19228: -- Assignee: Roman Puchkovskiy > Schema validation during tx processing: common framework > > > Key: IGNITE-19228 > URL: https://issues.apache.org/jira/browse/IGNITE-19228 > Project: Ignite > Issue Type: Improvement >Reporter: Roman Puchkovskiy >Assignee: Roman Puchkovskiy >Priority: Major > Labels: ignite-3 > > h3. Definitions > When a coordinator initiates a transaction, it takes a timestamp > beginTs=Ts=Now and sends it to all participants. On first access to a table Q > (in this transaction) on a primary replica node, the schema of Q is obtained > for moment Ts; this schema is called ‘initial schema’ and associated with > this transaction on this node. When a commit of the transaction is processed > with commit timestamp Tc, the node obtains the schema of Q again, now at the > moment of Tc; this is the ‘commit schema’. If the commit schema is different > from the initial schema and not compatible with it (using the notion of the > forward compatibility defined below), the commit fails (and the transaction > is aborted). > An initial schema is said to be _forward-compatible_ with a commit schema if, > having a tuple written with the initial schema, it is enough to know the > commit schema to read the tuple. > An initial schema is said to be _backward-compatible_ with a commit schema if > the same is true the other way around: having a tuple written with the commit > schema, we can read it having just the initial schema. > h3. What to do > We need to validate: > * forward schema compatibility on commit > * backward compatibility on reads in RW txs > If a schema change is incompatible, the transaction is aborted. > This task is about the implementation of a common framework allowing to do > validations with just a single validator that considers all schema changes > incompatible, and using this framework while processing transactions. > Real validators will be added in a follow-up task. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-19393) Java thin 3.0: testAccessLockedKeyTimesOut is flaky
[
https://issues.apache.org/jira/browse/IGNITE-19393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718931#comment-17718931
]
Pavel Tupitsyn commented on IGNITE-19393:
-
Actually, it is weird that two different exceptions can be thrown. [~alapin]
can you please have a look, as we discussed privately?
> Java thin 3.0: testAccessLockedKeyTimesOut is flaky
> ---
>
> Key: IGNITE-19393
> URL: https://issues.apache.org/jira/browse/IGNITE-19393
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Alexander Lapin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> {code:java}
> java.lang.AssertionError:
> Expected: a string containing "Replication is timed out"
> but: was "IGN-TX-4 TraceId:d54813d7-793a-4d81-9456-b7140cee2209 IGN-TX-4
> TraceId:d54813d7-793a-4d81-9456-b7140cee2209 IGN-TX-4
> TraceId:d54813d7-793a-4d81-9456-b7140cee2209 Failed to acquire a lock due to
> a conflict [txId=0187-db61-2a99--bb66f319,
> conflictingWaiter=WaiterImpl [txId=0187-db61-2a99--bb66f318,
> intendedLockMode=null, lockMode=X, ex=null, isDone=true]]"
> java.lang.AssertionError:
> Expected: a string containing "Replication is timed out"
> but: was "IGN-TX-4 TraceId:d54813d7-793a-4d81-9456-b7140cee2209 IGN-TX-4
> TraceId:d54813d7-793a-4d81-9456-b7140cee2209 IGN-TX-4
> TraceId:d54813d7-793a-4d81-9456-b7140cee2209 Failed to acquire a lock due to
> a conflict [txId=0187-db61-2a99--bb66f319,
> conflictingWaiter=WaiterImpl [txId=0187-db61-2a99--bb66f318,
> intendedLockMode=null, lockMode=X, ex=null, isDone=true]]"
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
> at
> org.apache.ignite.internal.runner.app.client.ItThinClientTransactionsTest.testAccessLockedKeyTimesOut(ItThinClientTransactionsTest.java:200)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:727)
> at
> org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at
> org.junit.jupiter.engine.extension.SameThreadTimeoutInvocation.proceed(SameThreadTimeoutInvocation.java:45)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:156)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:147)
> at
> org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:86)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(InterceptingExecutableInvoker.java:103)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.lambda$invoke$0(InterceptingExecutableInvoker.java:93)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
> at
> org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:92)
> at
> org.junit.jupiter.engine.execution.InterceptingExecutableInvoker.invoke(InterceptingExecutableInvoker.java:86)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:217)
> at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:213)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:138)
> at
> org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
> at
>
