Class RejectedRecord

java.lang.Object
software.amazon.awssdk.services.timestreamwrite.model.RejectedRecord
All Implemented Interfaces:
Serializable, SdkPojo, ToCopyableBuilder<RejectedRecord.Builder,RejectedRecord>
@Generated("software.amazon.awssdk:codegen") public final class RejectedRecord extends Object implements SdkPojo, Serializable, ToCopyableBuilder<RejectedRecord.Builder,RejectedRecord>

Represents records that were not successfully inserted into Timestream due to data validation issues that must be resolved before reinserting time-series data into the system.

See Also:

  • Method Details

    • recordIndex

      public final Integer recordIndex()

      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.

    • reason

      public final 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.

      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.

    • existingVersion

      public final 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.

      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.

    • toBuilder

      public RejectedRecord.Builder toBuilder()
      Description copied from interface: ToCopyableBuilder
      Take this object and create a builder that contains all of the current property values of this object.
      Specified by:
      toBuilder in interface ToCopyableBuilder<RejectedRecord.Builder,RejectedRecord>
      Returns:
      a builder for type T

    • builder

      public static RejectedRecord.Builder builder()

    • serializableBuilderClass

      public static Class<? extends RejectedRecord.Builder> serializableBuilderClass()

    • hashCode

      public final int hashCode()
      Overrides:
      hashCode in class Object

    • equals

      public final boolean equals(Object obj)
      Overrides:
      equals in class Object

    • equalsBySdkFields

      public final boolean equalsBySdkFields(Object obj)
      Description copied from interface: SdkPojo
      Indicates whether some other object is "equal to" this one by SDK fields. An SDK field is a modeled, non-inherited field in an SdkPojo class, and is generated based on a service model.

      If an SdkPojo class does not have any inherited fields, equalsBySdkFields and equals are essentially the same.

      Specified by:
      equalsBySdkFields in interface SdkPojo
      Parameters:
      obj - the object to be compared with
      Returns:
      true if the other object equals to this object by sdk fields, false otherwise.

    • toString

      public final 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

    • getValueForField

      public final <T> Optional<T> getValueForField(String fieldName, Class<T> clazz)

    • sdkFields

      public final List<SdkField<?>> sdkFields()
      Specified by:
      sdkFields in interface SdkPojo
      Returns:
      List of SdkField in this POJO. May be empty list but should never be null.