Re: [DISCUSSION] Improvement in control.sh configuration.
I'm currently working on ticket https://issues.apache.org/jira/browse/IGNITE-12832 It's not exactly what had been suggested but it will allow to pass some custom properties to the client configuration and to pass parameters without length limitations using .properties file. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: [DISCUSSION] Improvement in control.sh configuration.
Nikolay, specified ticket only describes the mentioned feature. It's not a ticket of the current proposal. On 16.03.2020 12:14, Dmitrii Ryabov wrote: Hello! Nikolay, yes, but currently, we can't declare user attributes through control.sh. пн, 16 мар. 2020 г., 12:06 Nikolay Izhikov : Hello, Mikhail. Can you, please, double-check link to the ticket? For now it’s a IGNITE-12049 Add user attributes to thin clients which is resolved. 16 марта 2020 г., в 12:04, Mikhail Petrov написал(а): Hello, Igniters. I'd like to propose a small improvement in control.sh configuration, which is to add the ability to pass parameters needed for cluster connection via a special properties file located in the same directory as control.sh script. The connection parameters in the proposed properties file can be considered as defaults and overwritten by those that are specified via the command line (current approach). The proposal can help to avoid unnecessary repeating of cluster connection configuration. Also, some connection parameters (e.g. user attributes [1]) cannot be passed through the command line due to its limited length. WDYT? [1] https://issues.apache.org/jira/browse/IGNITE-12049
Re: [DISCUSSION] Improvement in control.sh configuration.
Hello! Nikolay, yes, but currently, we can't declare user attributes through control.sh. пн, 16 мар. 2020 г., 12:06 Nikolay Izhikov : > Hello, Mikhail. > > Can you, please, double-check link to the ticket? > > For now it’s a IGNITE-12049 Add user attributes to thin clients which is > resolved. > > > 16 марта 2020 г., в 12:04, Mikhail Petrov > написал(а): > > > > Hello, Igniters. > > > > I'd like to propose a small improvement in control.sh configuration, > which is to add the ability to pass parameters needed for cluster > connection via a special properties file located in the same directory as > control.sh script. > > > > The connection parameters in the proposed properties file can be > considered as defaults and overwritten by those that are specified via the > command line (current approach). > > > > The proposal can help to avoid unnecessary repeating of cluster > connection configuration. Also, some connection parameters (e.g. user > attributes [1]) cannot be passed through the command line due to its > limited length. > > > > WDYT? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12049 > > > >
Re: [DISCUSSION] Improvement in control.sh configuration.
Hello, Mikhail. Can you, please, double-check link to the ticket? For now it’s a IGNITE-12049 Add user attributes to thin clients which is resolved. > 16 марта 2020 г., в 12:04, Mikhail Petrov написал(а): > > Hello, Igniters. > > I'd like to propose a small improvement in control.sh configuration, which is > to add the ability to pass parameters needed for cluster connection via a > special properties file located in the same directory as control.sh script. > > The connection parameters in the proposed properties file can be considered > as defaults and overwritten by those that are specified via the command line > (current approach). > > The proposal can help to avoid unnecessary repeating of cluster connection > configuration. Also, some connection parameters (e.g. user attributes [1]) > cannot be passed through the command line due to its limited length. > > WDYT? > > [1] https://issues.apache.org/jira/browse/IGNITE-12049 >
[DISCUSSION] Improvement in control.sh configuration.
Hello, Igniters. I'd like to propose a small improvement in control.sh configuration, which is to add the ability to pass parameters needed for cluster connection via a special properties file located in the same directory as control.sh script. The connection parameters in the proposed properties file can be considered as defaults and overwritten by those that are specified via the command line (current approach). The proposal can help to avoid unnecessary repeating of cluster connection configuration. Also, some connection parameters (e.g. user attributes [1]) cannot be passed through the command line due to its limited length. WDYT? [1] https://issues.apache.org/jira/browse/IGNITE-12049
