public static final class RedisProxy.ConnPoolSettings.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder> implements RedisProxy.ConnPoolSettingsOrBuilder
Redis connection pool settings.Protobuf type
envoy.config.filter.network.redis_proxy.v2.RedisProxy.ConnPoolSettings| Modifier and Type | Method and Description |
|---|---|
RedisProxy.ConnPoolSettings.Builder |
addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
RedisProxy.ConnPoolSettings |
build() |
RedisProxy.ConnPoolSettings |
buildPartial() |
RedisProxy.ConnPoolSettings.Builder |
clear() |
RedisProxy.ConnPoolSettings.Builder |
clearEnableHashtagging()
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream.
|
RedisProxy.ConnPoolSettings.Builder |
clearField(com.google.protobuf.Descriptors.FieldDescriptor field) |
RedisProxy.ConnPoolSettings.Builder |
clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) |
RedisProxy.ConnPoolSettings.Builder |
clearOpTimeout()
Per-operation timeout in milliseconds.
|
RedisProxy.ConnPoolSettings.Builder |
clone() |
RedisProxy.ConnPoolSettings |
getDefaultInstanceForType() |
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
com.google.protobuf.Descriptors.Descriptor |
getDescriptorForType() |
boolean |
getEnableHashtagging()
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream.
|
com.google.protobuf.Duration |
getOpTimeout()
Per-operation timeout in milliseconds.
|
com.google.protobuf.Duration.Builder |
getOpTimeoutBuilder()
Per-operation timeout in milliseconds.
|
com.google.protobuf.DurationOrBuilder |
getOpTimeoutOrBuilder()
Per-operation timeout in milliseconds.
|
boolean |
hasOpTimeout()
Per-operation timeout in milliseconds.
|
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
RedisProxy.ConnPoolSettings.Builder |
mergeFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
RedisProxy.ConnPoolSettings.Builder |
mergeFrom(com.google.protobuf.Message other) |
RedisProxy.ConnPoolSettings.Builder |
mergeFrom(RedisProxy.ConnPoolSettings other) |
RedisProxy.ConnPoolSettings.Builder |
mergeOpTimeout(com.google.protobuf.Duration value)
Per-operation timeout in milliseconds.
|
RedisProxy.ConnPoolSettings.Builder |
mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
RedisProxy.ConnPoolSettings.Builder |
setEnableHashtagging(boolean value)
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream.
|
RedisProxy.ConnPoolSettings.Builder |
setField(com.google.protobuf.Descriptors.FieldDescriptor field,
Object value) |
RedisProxy.ConnPoolSettings.Builder |
setOpTimeout(com.google.protobuf.Duration.Builder builderForValue)
Per-operation timeout in milliseconds.
|
RedisProxy.ConnPoolSettings.Builder |
setOpTimeout(com.google.protobuf.Duration value)
Per-operation timeout in milliseconds.
|
RedisProxy.ConnPoolSettings.Builder |
setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field,
int index,
Object value) |
RedisProxy.ConnPoolSettings.Builder |
setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) |
getAllFields, getField, getFieldBuilder, getOneofFieldDescriptor, getParentForChildren, getRepeatedField, getRepeatedFieldBuilder, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, internalGetMapField, internalGetMutableMapField, isClean, markClean, newBuilderForField, onBuilt, onChanged, setUnknownFieldsProto3findInitializationErrors, getInitializationErrorString, internalMergeFrom, mergeDelimitedFrom, mergeDelimitedFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, mergeFrom, newUninitializedMessageException, toStringaddAll, addAll, mergeFrom, newUninitializedMessageExceptionequals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitpublic static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder clear()
clear in interface com.google.protobuf.Message.Builderclear in interface com.google.protobuf.MessageLite.Builderclear in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
getDescriptorForType in interface com.google.protobuf.Message.BuildergetDescriptorForType in interface com.google.protobuf.MessageOrBuildergetDescriptorForType in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderpublic RedisProxy.ConnPoolSettings build()
build in interface com.google.protobuf.Message.Builderbuild in interface com.google.protobuf.MessageLite.Builderpublic RedisProxy.ConnPoolSettings buildPartial()
buildPartial in interface com.google.protobuf.Message.BuilderbuildPartial in interface com.google.protobuf.MessageLite.Builderpublic RedisProxy.ConnPoolSettings.Builder clone()
clone in interface com.google.protobuf.Message.Builderclone in interface com.google.protobuf.MessageLite.Builderclone in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
setField in interface com.google.protobuf.Message.BuildersetField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
clearField in interface com.google.protobuf.Message.BuilderclearField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
clearOneof in interface com.google.protobuf.Message.BuilderclearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
setRepeatedField in interface com.google.protobuf.Message.BuildersetRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
addRepeatedField in interface com.google.protobuf.Message.BuilderaddRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder mergeFrom(com.google.protobuf.Message other)
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder mergeFrom(RedisProxy.ConnPoolSettings other)
public final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public RedisProxy.ConnPoolSettings.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
mergeFrom in interface com.google.protobuf.Message.BuildermergeFrom in interface com.google.protobuf.MessageLite.BuildermergeFrom in class com.google.protobuf.AbstractMessage.Builder<RedisProxy.ConnPoolSettings.Builder>IOExceptionpublic boolean hasOpTimeout()
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }hasOpTimeout in interface RedisProxy.ConnPoolSettingsOrBuilderpublic com.google.protobuf.Duration getOpTimeout()
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }getOpTimeout in interface RedisProxy.ConnPoolSettingsOrBuilderpublic RedisProxy.ConnPoolSettings.Builder setOpTimeout(com.google.protobuf.Duration value)
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }public RedisProxy.ConnPoolSettings.Builder setOpTimeout(com.google.protobuf.Duration.Builder builderForValue)
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }public RedisProxy.ConnPoolSettings.Builder mergeOpTimeout(com.google.protobuf.Duration value)
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }public RedisProxy.ConnPoolSettings.Builder clearOpTimeout()
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }public com.google.protobuf.Duration.Builder getOpTimeoutBuilder()
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }public com.google.protobuf.DurationOrBuilder getOpTimeoutOrBuilder()
Per-operation timeout in milliseconds. The timer starts when the first command of a pipeline is written to the backend connection. Each response received from Redis resets the timer since it signifies that the next command is being processed by the backend. The only exception to this behavior is when a connection to a backend is not yet established. In that case, the connect timeout on the cluster will govern the timeout until the connection is ready.
.google.protobuf.Duration op_timeout = 1 [(.gogoproto.stdduration) = true, (.validate.rules) = { ... }getOpTimeoutOrBuilder in interface RedisProxy.ConnPoolSettingsOrBuilderpublic boolean getEnableHashtagging()
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream. The hash key used for determining the upstream in a
consistent hash ring configuration will be computed from the hash tagged key instead of the
whole key. The algorithm used to compute the hash tag is identical to the `redis-cluster
implementation <https://redis.io/topics/cluster-spec#keys-hash-tags>`_.
Examples:
* '{user1000}.following' and '{user1000}.followers' **will** be sent to the same upstream
* '{user1000}.following' and '{user1001}.following' **might** be sent to the same upstream
bool enable_hashtagging = 2;getEnableHashtagging in interface RedisProxy.ConnPoolSettingsOrBuilderpublic RedisProxy.ConnPoolSettings.Builder setEnableHashtagging(boolean value)
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream. The hash key used for determining the upstream in a
consistent hash ring configuration will be computed from the hash tagged key instead of the
whole key. The algorithm used to compute the hash tag is identical to the `redis-cluster
implementation <https://redis.io/topics/cluster-spec#keys-hash-tags>`_.
Examples:
* '{user1000}.following' and '{user1000}.followers' **will** be sent to the same upstream
* '{user1000}.following' and '{user1001}.following' **might** be sent to the same upstream
bool enable_hashtagging = 2;public RedisProxy.ConnPoolSettings.Builder clearEnableHashtagging()
Use hash tagging on every redis key to guarantee that keys with the same hash tag will be
forwarded to the same upstream. The hash key used for determining the upstream in a
consistent hash ring configuration will be computed from the hash tagged key instead of the
whole key. The algorithm used to compute the hash tag is identical to the `redis-cluster
implementation <https://redis.io/topics/cluster-spec#keys-hash-tags>`_.
Examples:
* '{user1000}.following' and '{user1000}.followers' **will** be sent to the same upstream
* '{user1000}.following' and '{user1001}.following' **might** be sent to the same upstream
bool enable_hashtagging = 2;public final RedisProxy.ConnPoolSettings.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
setUnknownFields in interface com.google.protobuf.Message.BuildersetUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>public final RedisProxy.ConnPoolSettings.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
mergeUnknownFields in interface com.google.protobuf.Message.BuildermergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<RedisProxy.ConnPoolSettings.Builder>Copyright © 2018–2019 The Envoy Project. All rights reserved.