implements
// @@protoc_insertion_point(builder_implements:google.privacy.dlp.v2.CryptoDeterministicConfig)
com.google.privacy.dlp.v2.CryptoDeterministicConfigOrBuilder {
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() {
return com.google.privacy.dlp.v2.DlpProto
.internal_static_google_privacy_dlp_v2_CryptoDeterministicConfig_descriptor;
}
@java.lang.Override
protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable
internalGetFieldAccessorTable() {
return com.google.privacy.dlp.v2.DlpProto
.internal_static_google_privacy_dlp_v2_CryptoDeterministicConfig_fieldAccessorTable
.ensureFieldAccessorsInitialized(
com.google.privacy.dlp.v2.CryptoDeterministicConfig.class,
com.google.privacy.dlp.v2.CryptoDeterministicConfig.Builder.class);
}
// Construct using com.google.privacy.dlp.v2.CryptoDeterministicConfig.newBuilder()
private Builder() {}
private Builder(com.google.protobuf.GeneratedMessageV3.BuilderParent parent) {
super(parent);
}
@java.lang.Override
public Builder clear() {
super.clear();
bitField0_ = 0;
cryptoKey_ = null;
if (cryptoKeyBuilder_ != null) {
cryptoKeyBuilder_.dispose();
cryptoKeyBuilder_ = null;
}
surrogateInfoType_ = null;
if (surrogateInfoTypeBuilder_ != null) {
surrogateInfoTypeBuilder_.dispose();
surrogateInfoTypeBuilder_ = null;
}
context_ = null;
if (contextBuilder_ != null) {
contextBuilder_.dispose();
contextBuilder_ = null;
}
return this;
}
@java.lang.Override
public com.google.protobuf.Descriptors.Descriptor getDescriptorForType() {
return com.google.privacy.dlp.v2.DlpProto
.internal_static_google_privacy_dlp_v2_CryptoDeterministicConfig_descriptor;
}
@java.lang.Override
public com.google.privacy.dlp.v2.CryptoDeterministicConfig getDefaultInstanceForType() {
return com.google.privacy.dlp.v2.CryptoDeterministicConfig.getDefaultInstance();
}
@java.lang.Override
public com.google.privacy.dlp.v2.CryptoDeterministicConfig build() {
com.google.privacy.dlp.v2.CryptoDeterministicConfig result = buildPartial();
if (!result.isInitialized()) {
throw newUninitializedMessageException(result);
}
return result;
}
@java.lang.Override
public com.google.privacy.dlp.v2.CryptoDeterministicConfig buildPartial() {
com.google.privacy.dlp.v2.CryptoDeterministicConfig result =
new com.google.privacy.dlp.v2.CryptoDeterministicConfig(this);
if (bitField0_ != 0) {
buildPartial0(result);
}
onBuilt();
return result;
}
private void buildPartial0(com.google.privacy.dlp.v2.CryptoDeterministicConfig result) {
int from_bitField0_ = bitField0_;
if (((from_bitField0_ & 0x00000001) != 0)) {
result.cryptoKey_ = cryptoKeyBuilder_ == null ? cryptoKey_ : cryptoKeyBuilder_.build();
}
if (((from_bitField0_ & 0x00000002) != 0)) {
result.surrogateInfoType_ =
surrogateInfoTypeBuilder_ == null
? surrogateInfoType_
: surrogateInfoTypeBuilder_.build();
}
if (((from_bitField0_ & 0x00000004) != 0)) {
result.context_ = contextBuilder_ == null ? context_ : contextBuilder_.build();
}
}
@java.lang.Override
public Builder clone() {
return super.clone();
}
@java.lang.Override
public Builder setField(
com.google.protobuf.Descriptors.FieldDescriptor field, java.lang.Object value) {
return super.setField(field, value);
}
@java.lang.Override
public Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field) {
return super.clearField(field);
}
@java.lang.Override
public Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) {
return super.clearOneof(oneof);
}
@java.lang.Override
public Builder setRepeatedField(
com.google.protobuf.Descriptors.FieldDescriptor field, int index, java.lang.Object value) {
return super.setRepeatedField(field, index, value);
}
@java.lang.Override
public Builder addRepeatedField(
com.google.protobuf.Descriptors.FieldDescriptor field, java.lang.Object value) {
return super.addRepeatedField(field, value);
}
@java.lang.Override
public Builder mergeFrom(com.google.protobuf.Message other) {
if (other instanceof com.google.privacy.dlp.v2.CryptoDeterministicConfig) {
return mergeFrom((com.google.privacy.dlp.v2.CryptoDeterministicConfig) other);
} else {
super.mergeFrom(other);
return this;
}
}
public Builder mergeFrom(com.google.privacy.dlp.v2.CryptoDeterministicConfig other) {
if (other == com.google.privacy.dlp.v2.CryptoDeterministicConfig.getDefaultInstance())
return this;
if (other.hasCryptoKey()) {
mergeCryptoKey(other.getCryptoKey());
}
if (other.hasSurrogateInfoType()) {
mergeSurrogateInfoType(other.getSurrogateInfoType());
}
if (other.hasContext()) {
mergeContext(other.getContext());
}
this.mergeUnknownFields(other.getUnknownFields());
onChanged();
return this;
}
@java.lang.Override
public final boolean isInitialized() {
return true;
}
@java.lang.Override
public Builder mergeFrom(
com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry)
throws java.io.IOException {
if (extensionRegistry == null) {
throw new java.lang.NullPointerException();
}
try {
boolean done = false;
while (!done) {
int tag = input.readTag();
switch (tag) {
case 0:
done = true;
break;
case 10:
{
input.readMessage(getCryptoKeyFieldBuilder().getBuilder(), extensionRegistry);
bitField0_ |= 0x00000001;
break;
} // case 10
case 18:
{
input.readMessage(
getSurrogateInfoTypeFieldBuilder().getBuilder(), extensionRegistry);
bitField0_ |= 0x00000002;
break;
} // case 18
case 26:
{
input.readMessage(getContextFieldBuilder().getBuilder(), extensionRegistry);
bitField0_ |= 0x00000004;
break;
} // case 26
default:
{
if (!super.parseUnknownField(input, extensionRegistry, tag)) {
done = true; // was an endgroup tag
}
break;
} // default:
} // switch (tag)
} // while (!done)
} catch (com.google.protobuf.InvalidProtocolBufferException e) {
throw e.unwrapIOException();
} finally {
onChanged();
} // finally
return this;
}
private int bitField0_;
private com.google.privacy.dlp.v2.CryptoKey cryptoKey_;
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.CryptoKey,
com.google.privacy.dlp.v2.CryptoKey.Builder,
com.google.privacy.dlp.v2.CryptoKeyOrBuilder>
cryptoKeyBuilder_;
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*
* @return Whether the cryptoKey field is set.
*/
public boolean hasCryptoKey() {
return ((bitField0_ & 0x00000001) != 0);
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*
* @return The cryptoKey.
*/
public com.google.privacy.dlp.v2.CryptoKey getCryptoKey() {
if (cryptoKeyBuilder_ == null) {
return cryptoKey_ == null
? com.google.privacy.dlp.v2.CryptoKey.getDefaultInstance()
: cryptoKey_;
} else {
return cryptoKeyBuilder_.getMessage();
}
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public Builder setCryptoKey(com.google.privacy.dlp.v2.CryptoKey value) {
if (cryptoKeyBuilder_ == null) {
if (value == null) {
throw new NullPointerException();
}
cryptoKey_ = value;
} else {
cryptoKeyBuilder_.setMessage(value);
}
bitField0_ |= 0x00000001;
onChanged();
return this;
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public Builder setCryptoKey(com.google.privacy.dlp.v2.CryptoKey.Builder builderForValue) {
if (cryptoKeyBuilder_ == null) {
cryptoKey_ = builderForValue.build();
} else {
cryptoKeyBuilder_.setMessage(builderForValue.build());
}
bitField0_ |= 0x00000001;
onChanged();
return this;
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public Builder mergeCryptoKey(com.google.privacy.dlp.v2.CryptoKey value) {
if (cryptoKeyBuilder_ == null) {
if (((bitField0_ & 0x00000001) != 0)
&& cryptoKey_ != null
&& cryptoKey_ != com.google.privacy.dlp.v2.CryptoKey.getDefaultInstance()) {
getCryptoKeyBuilder().mergeFrom(value);
} else {
cryptoKey_ = value;
}
} else {
cryptoKeyBuilder_.mergeFrom(value);
}
bitField0_ |= 0x00000001;
onChanged();
return this;
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public Builder clearCryptoKey() {
bitField0_ = (bitField0_ & ~0x00000001);
cryptoKey_ = null;
if (cryptoKeyBuilder_ != null) {
cryptoKeyBuilder_.dispose();
cryptoKeyBuilder_ = null;
}
onChanged();
return this;
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public com.google.privacy.dlp.v2.CryptoKey.Builder getCryptoKeyBuilder() {
bitField0_ |= 0x00000001;
onChanged();
return getCryptoKeyFieldBuilder().getBuilder();
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
public com.google.privacy.dlp.v2.CryptoKeyOrBuilder getCryptoKeyOrBuilder() {
if (cryptoKeyBuilder_ != null) {
return cryptoKeyBuilder_.getMessageOrBuilder();
} else {
return cryptoKey_ == null
? com.google.privacy.dlp.v2.CryptoKey.getDefaultInstance()
: cryptoKey_;
}
}
/**
*
*
*
* The key used by the encryption function. For deterministic encryption
* using AES-SIV, the provided key is internally expanded to 64 bytes prior to
* use.
*
*
* .google.privacy.dlp.v2.CryptoKey crypto_key = 1;
*/
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.CryptoKey,
com.google.privacy.dlp.v2.CryptoKey.Builder,
com.google.privacy.dlp.v2.CryptoKeyOrBuilder>
getCryptoKeyFieldBuilder() {
if (cryptoKeyBuilder_ == null) {
cryptoKeyBuilder_ =
new com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.CryptoKey,
com.google.privacy.dlp.v2.CryptoKey.Builder,
com.google.privacy.dlp.v2.CryptoKeyOrBuilder>(
getCryptoKey(), getParentForChildren(), isClean());
cryptoKey_ = null;
}
return cryptoKeyBuilder_;
}
private com.google.privacy.dlp.v2.InfoType surrogateInfoType_;
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.InfoType,
com.google.privacy.dlp.v2.InfoType.Builder,
com.google.privacy.dlp.v2.InfoTypeOrBuilder>
surrogateInfoTypeBuilder_;
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*
* @return Whether the surrogateInfoType field is set.
*/
public boolean hasSurrogateInfoType() {
return ((bitField0_ & 0x00000002) != 0);
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*
* @return The surrogateInfoType.
*/
public com.google.privacy.dlp.v2.InfoType getSurrogateInfoType() {
if (surrogateInfoTypeBuilder_ == null) {
return surrogateInfoType_ == null
? com.google.privacy.dlp.v2.InfoType.getDefaultInstance()
: surrogateInfoType_;
} else {
return surrogateInfoTypeBuilder_.getMessage();
}
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public Builder setSurrogateInfoType(com.google.privacy.dlp.v2.InfoType value) {
if (surrogateInfoTypeBuilder_ == null) {
if (value == null) {
throw new NullPointerException();
}
surrogateInfoType_ = value;
} else {
surrogateInfoTypeBuilder_.setMessage(value);
}
bitField0_ |= 0x00000002;
onChanged();
return this;
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public Builder setSurrogateInfoType(
com.google.privacy.dlp.v2.InfoType.Builder builderForValue) {
if (surrogateInfoTypeBuilder_ == null) {
surrogateInfoType_ = builderForValue.build();
} else {
surrogateInfoTypeBuilder_.setMessage(builderForValue.build());
}
bitField0_ |= 0x00000002;
onChanged();
return this;
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public Builder mergeSurrogateInfoType(com.google.privacy.dlp.v2.InfoType value) {
if (surrogateInfoTypeBuilder_ == null) {
if (((bitField0_ & 0x00000002) != 0)
&& surrogateInfoType_ != null
&& surrogateInfoType_ != com.google.privacy.dlp.v2.InfoType.getDefaultInstance()) {
getSurrogateInfoTypeBuilder().mergeFrom(value);
} else {
surrogateInfoType_ = value;
}
} else {
surrogateInfoTypeBuilder_.mergeFrom(value);
}
bitField0_ |= 0x00000002;
onChanged();
return this;
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public Builder clearSurrogateInfoType() {
bitField0_ = (bitField0_ & ~0x00000002);
surrogateInfoType_ = null;
if (surrogateInfoTypeBuilder_ != null) {
surrogateInfoTypeBuilder_.dispose();
surrogateInfoTypeBuilder_ = null;
}
onChanged();
return this;
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public com.google.privacy.dlp.v2.InfoType.Builder getSurrogateInfoTypeBuilder() {
bitField0_ |= 0x00000002;
onChanged();
return getSurrogateInfoTypeFieldBuilder().getBuilder();
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
public com.google.privacy.dlp.v2.InfoTypeOrBuilder getSurrogateInfoTypeOrBuilder() {
if (surrogateInfoTypeBuilder_ != null) {
return surrogateInfoTypeBuilder_.getMessageOrBuilder();
} else {
return surrogateInfoType_ == null
? com.google.privacy.dlp.v2.InfoType.getDefaultInstance()
: surrogateInfoType_;
}
}
/**
*
*
*
* The custom info type to annotate the surrogate with.
* This annotation will be applied to the surrogate by prefixing it with
* the name of the custom info type followed by the number of
* characters comprising the surrogate. The following scheme defines the
* format: {info type name}({surrogate character count}):{surrogate}
* For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and
* the surrogate is 'abc', the full replacement value
* will be: 'MY_TOKEN_INFO_TYPE(3):abc'
* This annotation identifies the surrogate when inspecting content using the
* custom info type 'Surrogate'. This facilitates reversal of the
* surrogate when it occurs in free text.
* Note: For record transformations where the entire cell in a table is being
* transformed, surrogates are not mandatory. Surrogates are used to denote
* the location of the token and are necessary for re-identification in free
* form text.
* In order for inspection to work properly, the name of this info type must
* not occur naturally anywhere in your data; otherwise, inspection may either
* - reverse a surrogate that does not correspond to an actual identifier
* - be unable to parse the surrogate and result in an error
* Therefore, choose your custom info type name carefully after considering
* what your data looks like. One way to select a name that has a high chance
* of yielding reliable detection is to include one or more unicode characters
* that are highly improbable to exist in your data.
* For example, assuming your data is entered from a regular ASCII keyboard,
* the symbol with the hex code point 29DD might be used like so:
* ⧝MY_TOKEN_TYPE.
*
*
* .google.privacy.dlp.v2.InfoType surrogate_info_type = 2;
*/
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.InfoType,
com.google.privacy.dlp.v2.InfoType.Builder,
com.google.privacy.dlp.v2.InfoTypeOrBuilder>
getSurrogateInfoTypeFieldBuilder() {
if (surrogateInfoTypeBuilder_ == null) {
surrogateInfoTypeBuilder_ =
new com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.InfoType,
com.google.privacy.dlp.v2.InfoType.Builder,
com.google.privacy.dlp.v2.InfoTypeOrBuilder>(
getSurrogateInfoType(), getParentForChildren(), isClean());
surrogateInfoType_ = null;
}
return surrogateInfoTypeBuilder_;
}
private com.google.privacy.dlp.v2.FieldId context_;
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.FieldId,
com.google.privacy.dlp.v2.FieldId.Builder,
com.google.privacy.dlp.v2.FieldIdOrBuilder>
contextBuilder_;
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*
* @return Whether the context field is set.
*/
public boolean hasContext() {
return ((bitField0_ & 0x00000004) != 0);
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*
* @return The context.
*/
public com.google.privacy.dlp.v2.FieldId getContext() {
if (contextBuilder_ == null) {
return context_ == null ? com.google.privacy.dlp.v2.FieldId.getDefaultInstance() : context_;
} else {
return contextBuilder_.getMessage();
}
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public Builder setContext(com.google.privacy.dlp.v2.FieldId value) {
if (contextBuilder_ == null) {
if (value == null) {
throw new NullPointerException();
}
context_ = value;
} else {
contextBuilder_.setMessage(value);
}
bitField0_ |= 0x00000004;
onChanged();
return this;
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public Builder setContext(com.google.privacy.dlp.v2.FieldId.Builder builderForValue) {
if (contextBuilder_ == null) {
context_ = builderForValue.build();
} else {
contextBuilder_.setMessage(builderForValue.build());
}
bitField0_ |= 0x00000004;
onChanged();
return this;
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public Builder mergeContext(com.google.privacy.dlp.v2.FieldId value) {
if (contextBuilder_ == null) {
if (((bitField0_ & 0x00000004) != 0)
&& context_ != null
&& context_ != com.google.privacy.dlp.v2.FieldId.getDefaultInstance()) {
getContextBuilder().mergeFrom(value);
} else {
context_ = value;
}
} else {
contextBuilder_.mergeFrom(value);
}
bitField0_ |= 0x00000004;
onChanged();
return this;
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public Builder clearContext() {
bitField0_ = (bitField0_ & ~0x00000004);
context_ = null;
if (contextBuilder_ != null) {
contextBuilder_.dispose();
contextBuilder_ = null;
}
onChanged();
return this;
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public com.google.privacy.dlp.v2.FieldId.Builder getContextBuilder() {
bitField0_ |= 0x00000004;
onChanged();
return getContextFieldBuilder().getBuilder();
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
public com.google.privacy.dlp.v2.FieldIdOrBuilder getContextOrBuilder() {
if (contextBuilder_ != null) {
return contextBuilder_.getMessageOrBuilder();
} else {
return context_ == null ? com.google.privacy.dlp.v2.FieldId.getDefaultInstance() : context_;
}
}
/**
*
*
*
* A context may be used for higher security and maintaining
* referential integrity such that the same identifier in two different
* contexts will be given a distinct surrogate. The context is appended to
* plaintext value being encrypted. On decryption the provided context is
* validated against the value used during encryption. If a context was
* provided during encryption, same context must be provided during decryption
* as well.
* If the context is not set, plaintext would be used as is for encryption.
* If the context is set but:
* 1. there is no record present when transforming a given value or
* 2. the field is not present when transforming a given value,
* plaintext would be used as is for encryption.
* Note that case (1) is expected when an `InfoTypeTransformation` is
* applied to both structured and unstructured `ContentItem`s.
*
*
* .google.privacy.dlp.v2.FieldId context = 3;
*/
private com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.FieldId,
com.google.privacy.dlp.v2.FieldId.Builder,
com.google.privacy.dlp.v2.FieldIdOrBuilder>
getContextFieldBuilder() {
if (contextBuilder_ == null) {
contextBuilder_ =
new com.google.protobuf.SingleFieldBuilderV3<
com.google.privacy.dlp.v2.FieldId,
com.google.privacy.dlp.v2.FieldId.Builder,
com.google.privacy.dlp.v2.FieldIdOrBuilder>(
getContext(), getParentForChildren(), isClean());
context_ = null;
}
return contextBuilder_;
}
@java.lang.Override
public final Builder setUnknownFields(final com.google.protobuf.UnknownFieldSet unknownFields) {
return super.setUnknownFields(unknownFields);
}
@java.lang.Override
public final Builder mergeUnknownFields(
final com.google.protobuf.UnknownFieldSet unknownFields) {
return super.mergeUnknownFields(unknownFields);
}
// @@protoc_insertion_point(builder_scope:google.privacy.dlp.v2.CryptoDeterministicConfig)
}
// @@protoc_insertion_point(class_scope:google.privacy.dlp.v2.CryptoDeterministicConfig)
private static final com.google.privacy.dlp.v2.CryptoDeterministicConfig DEFAULT_INSTANCE;
static {
DEFAULT_INSTANCE = new com.google.privacy.dlp.v2.CryptoDeterministicConfig();
}
public static com.google.privacy.dlp.v2.CryptoDeterministicConfig getDefaultInstance() {
return DEFAULT_INSTANCE;
}
private static final com.google.protobuf.Parser PARSER =
new com.google.protobuf.AbstractParser() {
@java.lang.Override
public CryptoDeterministicConfig parsePartialFrom(
com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry)
throws com.google.protobuf.InvalidProtocolBufferException {
Builder builder = newBuilder();
try {
builder.mergeFrom(input, extensionRegistry);
} catch (com.google.protobuf.InvalidProtocolBufferException e) {
throw e.setUnfinishedMessage(builder.buildPartial());
} catch (com.google.protobuf.UninitializedMessageException e) {
throw e.asInvalidProtocolBufferException().setUnfinishedMessage(builder.buildPartial());
} catch (java.io.IOException e) {
throw new com.google.protobuf.InvalidProtocolBufferException(e)
.setUnfinishedMessage(builder.buildPartial());
}
return builder.buildPartial();
}
};
public static com.google.protobuf.Parser parser() {
return PARSER;
}
@java.lang.Override
public com.google.protobuf.Parser getParserForType() {
return PARSER;
}
@java.lang.Override
public com.google.privacy.dlp.v2.CryptoDeterministicConfig getDefaultInstanceForType() {
return DEFAULT_INSTANCE;
}
}