Hi,
Lets finalize our decision.
1. All distributed properties are published. - It's clear.
2. Do we add the description for the property (add method to the
interface DistributedProperty)?
If yes: is the description is persisted or hard-coded?
3. Permission:
- add one permission to modify
Hello, Anton.
> 1) Publish distributed property
I propose to use SystemView API to accomplish this.
Actually, there is PR for it, already [1]
Distributed property will be available via SQL - «SELECT * FROM
SYS.DISTRIBUTED_METASTORAGE»
Or via JMX in the corresponding bean.
> 2) Permission for
Hi everyone,
I think I agree with Nikolay that we should make available all our property not
only some of them. Also maybe it makes sense to split this task into two tasks
in the following way: Publish all distributed property through public
interfaces(control.sh, jmx, etc.), Giving
Hello, Taras.
One more thing:
> --property list - prints list of the available properties with description,
> e.g.:
We have a convenient API to show Ignite internal objects - System Views [1]
Any system view available via SQL and JMX.
It seems we should have METASTORAGE view instead of this
Hello, Taras.
> I guess some properties (may be future properties) shouldn't be published
> through generic cmd line interface.
With marker interface user have to wait for a new release to fix not published
property.
New release is a very long way for fixing one tiny configuration value.
Hi,
> Why do we want to restrict property management somehow?
I guess some properties (may be future properties) shouldn't be
published through generic cmd line interface.
May be its require separate more complex cmd line commands, some
properties may have dependencies and require complex
Hello, Taras.
It a shame we don’t have a well-written guide for the development of the Ignite
management interfaces at the moment.
For now, we have dozen of some management APIs - java, JMX, SQL, control.sh,
visorcmd.sh, REST
I think we should support 3 manage interfaces for each new command:
Hi,
Motivation: we have to manage SQL distributed property by command line
and introduce common approach to manage distributed properties.
Issue: IGNITE-13186 (see [1])
My proposal is:
Property classes & DistributedConfigurationProcessor changes (see PR [2]):
- introduce PublicProperty
