com.amazonaws.services.timestreamwrite.model

Class RejectedRecord

java.lang.Object

com.amazonaws.services.timestreamwrite.model.RejectedRecord

All Implemented Interfaces:

StructuredPojo, Serializable, Cloneable

@Generated(value="com.amazonaws:aws-java-sdk-code-generator")
public class RejectedRecord
extends Object
implements Serializable, Cloneable, StructuredPojo

Records that were not successfully inserted into Timestream due to data validation issues that must be resolved prior to reinserting time series data into the system.

See Also:

AWS API Documentation, Serialized Form

Constructor Summary

Constructors

Constructor and Description
RejectedRecord()

Method Summary

Modifier and Type	Method and Description
RejectedRecord	clone()
boolean	equals(Object obj)
Long	getExistingVersion() The existing version of the record.
String	getReason() The reason why a record was not successfully inserted into Timestream.
Integer	getRecordIndex() The index of the record in the input request for WriteRecords.
int	hashCode()
void	marshall(ProtocolMarshaller protocolMarshaller)
void	setExistingVersion(Long existingVersion) The existing version of the record.
void	setReason(String reason) The reason why a record was not successfully inserted into Timestream.
void	setRecordIndex(Integer recordIndex) The index of the record in the input request for WriteRecords.
String	toString() Returns a string representation of this object.
RejectedRecord	withExistingVersion(Long existingVersion) The existing version of the record.
RejectedRecord	withReason(String reason) The reason why a record was not successfully inserted into Timestream.
RejectedRecord	withRecordIndex(Integer recordIndex) The index of the record in the input request for WriteRecords.

Methods inherited from class java.lang.Object

finalize, getClass, notify, notifyAll, wait, wait, wait

Constructor Detail

RejectedRecord

public RejectedRecord()

Method Detail

setRecordIndex

public void setRecordIndex(Integer recordIndex)

The index of the record in the input request for WriteRecords. Indexes begin with 0.

Parameters:

recordIndex - The index of the record in the input request for WriteRecords. Indexes begin with 0.

getRecordIndex

public Integer getRecordIndex()

The index of the record in the input request for WriteRecords. Indexes begin with 0.

Returns:

The index of the record in the input request for WriteRecords. Indexes begin with 0.

withRecordIndex

public RejectedRecord withRecordIndex(Integer recordIndex)

The index of the record in the input request for WriteRecords. Indexes begin with 0.

Parameters:

recordIndex - The index of the record in the input request for WriteRecords. Indexes begin with 0.

Returns:

Returns a reference to this object so that method calls can be chained together.

setReason

public void setReason(String reason)

The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

Parameters:

reason - The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

getReason

public String getReason()

The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

Returns:

The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

withReason

public RejectedRecord withReason(String reason)

The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

Parameters:

reason - The reason why a record was not successfully inserted into Timestream. Possible causes of failure include:

• Records with duplicate data where there are multiple records with the same dimensions, timestamps, and measure names but:

  • Measure values are different

  • Version is not present in the request or the value of version in the new record is equal to or lower than the existing value

  If Timestream rejects data for this case, the ExistingVersion field in the RejectedRecords response will indicate the current record’s version. To force an update, you can resend the request with a version for the record set to a value greater than the ExistingVersion.

• Records with timestamps that lie outside the retention duration of the memory store

  When the retention window is updated, you will receive a RejectedRecords exception if you immediately try to ingest data within the new window. To avoid a RejectedRecords exception, wait until the duration of the new window to ingest new data. For further information, see Best Practices for Configuring Timestream and the explanation of how storage works in Timestream.

• Records with dimensions or measures that exceed the Timestream defined limits.

For more information, see Access Management in the Timestream Developer Guide.

Returns:

Returns a reference to this object so that method calls can be chained together.

setExistingVersion

public void setExistingVersion(Long existingVersion)

The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

Parameters:

existingVersion - The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

getExistingVersion

public Long getExistingVersion()

The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

Returns:

The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

withExistingVersion

public RejectedRecord withExistingVersion(Long existingVersion)

The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

Parameters:

existingVersion - The existing version of the record. This value is populated in scenarios where an identical record exists with a higher version than the version in the write request.

Returns:

Returns a reference to this object so that method calls can be chained together.

toString

public String toString()

Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be redacted from this string using a placeholder value.

Overrides:

toString in class Object

Returns:

A string representation of this object.

See Also:

Object.toString()

equals

public boolean equals(Object obj)

Overrides:

equals in class Object

hashCode

public int hashCode()

Overrides:

hashCode in class Object

clone

public RejectedRecord clone()

Overrides:

clone in class Object

marshall

public void marshall(ProtocolMarshaller protocolMarshaller)

Specified by:

marshall in interface StructuredPojo