ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn Wiebe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11157) Web Console Cluster Configuration Incomplete
Date Thu, 31 Jan 2019 14:54:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757317#comment-16757317

Glenn Wiebe commented on IGNITE-11157:

Note, I was running MongoDB version 4.0.5 Community when receiving this issue.
Having turned off my separate instance, and using the embedded MongoDB 3.4.7 Community edition,
I have not had this issue.

Whether this issue should be closed is dependent on whether more recent MongoDB instances
are to be supported.
I can work around.


> Web Console Cluster Configuration Incomplete
> --------------------------------------------
>                 Key: IGNITE-11157
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11157
>             Project: Ignite
>          Issue Type: Bug
>          Components: wizards
>    Affects Versions: 2.7
>            Reporter: Glenn Wiebe
>            Assignee: Vasiliy Sisko
>            Priority: Minor
> This may be an artifact of configuring in both Basic and Advanced settings, but...
> Alteration of a cache's config settings from the Basic tab destroys the configuration
settings about the particular cache (all fields, queries, indexes, etc. are now gone for the
altered cache).
> Replicate Error:
> 1. Create a new config by Importing from database (e.g. pick two or more tables);
> 2. Open Config (note the advanced settings for one of the tables)
> 3. Go back to Basic settings and change one of the caches from PARTITIONED to REPLICATED.
> 4. Save & Download the configuration
> <=== Note, one may have trouble with downloading as an error may be flashed on screen.
> 4. (alternate) go to list of configurations, select it and under action, choose Download.
> Note the particular cache that was changed now has lost virtually all of its definition.
> Regards,
>   Glenn

This message was sent by Atlassian JIRA

View raw message