Skip to content

Conversation

@mdumandag
Copy link
Contributor

@mdumandag mdumandag commented Sep 21, 2020

Depends on #218

This PR replaces Java-style ClientConfig class with keyword-arguments.
It also updates README, code samples, and tests with the new configuration
style. The full list of supported keyword arguments can be seen in the
hazelcast.config._Config class. Documentation for the keyword arguments will be added in a latter PR when we switch to the Google style docstrings(#221 ).

Apart from them,

  • enums are changed to EnumName.ITEM_NAME format.
  • IDEs now show the possible values of enums.
  • All config options now assume time units in seconds.
  • cloud_config.enabled is removed. Cloud discovery is enabled once the
    discovery token is set.
  • Extra tests are added for _IndexConfig and _IndexUtil.
  • Load balancers are moved to the util, similar to the Java client.
  • Aliases SSLProtocol.SSL and SSLProtocol.TLS are removed. One has to give the exact version to be used now

This PR replaces Java-style `ClientConfig` class with keyword-arguments.
It also updates README, code samples and tests with the new configuration
style. The full list of supported keyword arguments can be seen on the
`hazelcast.config._Config` class. Apart from them,

- `enum`s are changed to `EnumName.ITEM_NAME` format.
- IDEs now show the possible values of `enum`s.
- All config options now assume time unit in seconds.
- `cloud_config.enabled` is removed. Cloud discovery is enabled once the
discovery token is set.
- Extra tests are added for `_IndexConfig` and `_IndexUtil`.
- Load balancers are moved to the `util`, similar to the Java client.
@mdumandag mdumandag merged commit 78bd689 into hazelcast:master Oct 9, 2020
@mdumandag mdumandag deleted the config-update branch October 9, 2020 09:26
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 11, 2020
We forget to update the code that sets socket options while doing hazelcast#219.

The code now handles the given socket options tuple correctly. Also,
added some tests that verifies this.
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 11, 2020
We forget to update the code that sets socket options while doing hazelcast#219.

The code now handles the given socket options tuple correctly. Also,
added some tests that verifies this.
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 11, 2020
We forget to update the code that sets socket options while doing hazelcast#219.

The code now handles the given socket options tuple correctly. Also,
added some tests that verifies this.
mdumandag added a commit to mdumandag/hazelcast-python-client that referenced this pull request Dec 11, 2020
We forget to update the code that sets socket options while doing hazelcast#219.

The code now handles the given socket options tuple correctly. Also,
added some tests that verifies this.
mdumandag added a commit that referenced this pull request Dec 11, 2020
We forget to update the code that sets socket options while doing #219.

The code now handles the given socket options tuple correctly. Also,
added some tests that verifies this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants