@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public interface AmazonTimestreamWriteAsync extends AmazonTimestreamWrite
AsyncHandler can be used to receive
notification when an asynchronous operation completes.
Note: Do not directly implement this interface, new methods are added to it regularly. Extend from
AbstractAmazonTimestreamWriteAsync instead.
Amazon Timestream is a fast, scalable, fully managed time series database service that makes it easy to store and analyze trillions of time series data points per day. With Timestream, you can easily store and analyze IoT sensor data to derive insights from your IoT applications. You can analyze industrial telemetry to streamline equipment management and maintenance. You can also store and analyze log data and metrics to improve the performance and availability of your applications. Timestream is built from the ground up to effectively ingest, process, and store time series data. It organizes data to optimize query processing. It automatically scales based on the volume of data ingested and on the query volume to ensure you receive optimal performance while inserting and querying data. As your data grows over time, Timestream’s adaptive query processing engine spans across storage tiers to provide fast analysis while reducing costs.
ENDPOINT_PREFIX| Modifier and Type | Method and Description |
|---|---|
Future<CreateDatabaseResult> |
createDatabaseAsync(CreateDatabaseRequest createDatabaseRequest)
Creates a new Timestream database.
|
Future<CreateDatabaseResult> |
createDatabaseAsync(CreateDatabaseRequest createDatabaseRequest,
AsyncHandler<CreateDatabaseRequest,CreateDatabaseResult> asyncHandler)
Creates a new Timestream database.
|
Future<CreateTableResult> |
createTableAsync(CreateTableRequest createTableRequest)
The CreateTable operation adds a new table to an existing database in your account.
|
Future<CreateTableResult> |
createTableAsync(CreateTableRequest createTableRequest,
AsyncHandler<CreateTableRequest,CreateTableResult> asyncHandler)
The CreateTable operation adds a new table to an existing database in your account.
|
Future<DeleteDatabaseResult> |
deleteDatabaseAsync(DeleteDatabaseRequest deleteDatabaseRequest)
Deletes a given Timestream database.
|
Future<DeleteDatabaseResult> |
deleteDatabaseAsync(DeleteDatabaseRequest deleteDatabaseRequest,
AsyncHandler<DeleteDatabaseRequest,DeleteDatabaseResult> asyncHandler)
Deletes a given Timestream database.
|
Future<DeleteTableResult> |
deleteTableAsync(DeleteTableRequest deleteTableRequest)
Deletes a given Timestream table.
|
Future<DeleteTableResult> |
deleteTableAsync(DeleteTableRequest deleteTableRequest,
AsyncHandler<DeleteTableRequest,DeleteTableResult> asyncHandler)
Deletes a given Timestream table.
|
Future<DescribeDatabaseResult> |
describeDatabaseAsync(DescribeDatabaseRequest describeDatabaseRequest)
Returns information about the database, including the database name, time that the database was created, and the
total number of tables found within the database.
|
Future<DescribeDatabaseResult> |
describeDatabaseAsync(DescribeDatabaseRequest describeDatabaseRequest,
AsyncHandler<DescribeDatabaseRequest,DescribeDatabaseResult> asyncHandler)
Returns information about the database, including the database name, time that the database was created, and the
total number of tables found within the database.
|
Future<DescribeEndpointsResult> |
describeEndpointsAsync(DescribeEndpointsRequest describeEndpointsRequest)
DescribeEndpoints returns a list of available endpoints to make Timestream API calls against.
|
Future<DescribeEndpointsResult> |
describeEndpointsAsync(DescribeEndpointsRequest describeEndpointsRequest,
AsyncHandler<DescribeEndpointsRequest,DescribeEndpointsResult> asyncHandler)
DescribeEndpoints returns a list of available endpoints to make Timestream API calls against.
|
Future<DescribeTableResult> |
describeTableAsync(DescribeTableRequest describeTableRequest)
Returns information about the table, including the table name, database name, retention duration of the memory
store and the magnetic store.
|
Future<DescribeTableResult> |
describeTableAsync(DescribeTableRequest describeTableRequest,
AsyncHandler<DescribeTableRequest,DescribeTableResult> asyncHandler)
Returns information about the table, including the table name, database name, retention duration of the memory
store and the magnetic store.
|
Future<ListDatabasesResult> |
listDatabasesAsync(ListDatabasesRequest listDatabasesRequest)
Returns a list of your Timestream databases.
|
Future<ListDatabasesResult> |
listDatabasesAsync(ListDatabasesRequest listDatabasesRequest,
AsyncHandler<ListDatabasesRequest,ListDatabasesResult> asyncHandler)
Returns a list of your Timestream databases.
|
Future<ListTablesResult> |
listTablesAsync(ListTablesRequest listTablesRequest)
A list of tables, along with the name, status and retention properties of each table.
|
Future<ListTablesResult> |
listTablesAsync(ListTablesRequest listTablesRequest,
AsyncHandler<ListTablesRequest,ListTablesResult> asyncHandler)
A list of tables, along with the name, status and retention properties of each table.
|
Future<ListTagsForResourceResult> |
listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest)
List all tags on a Timestream resource.
|
Future<ListTagsForResourceResult> |
listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest,
AsyncHandler<ListTagsForResourceRequest,ListTagsForResourceResult> asyncHandler)
List all tags on a Timestream resource.
|
Future<TagResourceResult> |
tagResourceAsync(TagResourceRequest tagResourceRequest)
Associate a set of tags with a Timestream resource.
|
Future<TagResourceResult> |
tagResourceAsync(TagResourceRequest tagResourceRequest,
AsyncHandler<TagResourceRequest,TagResourceResult> asyncHandler)
Associate a set of tags with a Timestream resource.
|
Future<UntagResourceResult> |
untagResourceAsync(UntagResourceRequest untagResourceRequest)
Removes the association of tags from a Timestream resource.
|
Future<UntagResourceResult> |
untagResourceAsync(UntagResourceRequest untagResourceRequest,
AsyncHandler<UntagResourceRequest,UntagResourceResult> asyncHandler)
Removes the association of tags from a Timestream resource.
|
Future<UpdateDatabaseResult> |
updateDatabaseAsync(UpdateDatabaseRequest updateDatabaseRequest)
Modifies the KMS key for an existing database.
|
Future<UpdateDatabaseResult> |
updateDatabaseAsync(UpdateDatabaseRequest updateDatabaseRequest,
AsyncHandler<UpdateDatabaseRequest,UpdateDatabaseResult> asyncHandler)
Modifies the KMS key for an existing database.
|
Future<UpdateTableResult> |
updateTableAsync(UpdateTableRequest updateTableRequest)
Modifies the retention duration of the memory store and magnetic store for your Timestream table.
|
Future<UpdateTableResult> |
updateTableAsync(UpdateTableRequest updateTableRequest,
AsyncHandler<UpdateTableRequest,UpdateTableResult> asyncHandler)
Modifies the retention duration of the memory store and magnetic store for your Timestream table.
|
Future<WriteRecordsResult> |
writeRecordsAsync(WriteRecordsRequest writeRecordsRequest)
The WriteRecords operation enables you to write your time series data into Timestream.
|
Future<WriteRecordsResult> |
writeRecordsAsync(WriteRecordsRequest writeRecordsRequest,
AsyncHandler<WriteRecordsRequest,WriteRecordsResult> asyncHandler)
The WriteRecords operation enables you to write your time series data into Timestream.
|
createDatabase, createTable, deleteDatabase, deleteTable, describeDatabase, describeEndpoints, describeTable, getCachedResponseMetadata, listDatabases, listTables, listTagsForResource, shutdown, tagResource, untagResource, updateDatabase, updateTable, writeRecordsFuture<CreateDatabaseResult> createDatabaseAsync(CreateDatabaseRequest createDatabaseRequest)
Creates a new Timestream database. If the KMS key is not specified, the database will be encrypted with a Timestream managed KMS key located in your account. Refer to Amazon Web Services managed KMS keys for more info. Service quotas apply. See code sample for details.
createDatabaseRequest - Future<CreateDatabaseResult> createDatabaseAsync(CreateDatabaseRequest createDatabaseRequest, AsyncHandler<CreateDatabaseRequest,CreateDatabaseResult> asyncHandler)
Creates a new Timestream database. If the KMS key is not specified, the database will be encrypted with a Timestream managed KMS key located in your account. Refer to Amazon Web Services managed KMS keys for more info. Service quotas apply. See code sample for details.
createDatabaseRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<CreateTableResult> createTableAsync(CreateTableRequest createTableRequest)
The CreateTable operation adds a new table to an existing database in your account. In an Amazon Web Services account, table names must be at least unique within each Region if they are in the same database. You may have identical table names in the same Region if the tables are in separate databases. While creating the table, you must specify the table name, database name, and the retention properties. Service quotas apply. See code sample for details.
createTableRequest - Future<CreateTableResult> createTableAsync(CreateTableRequest createTableRequest, AsyncHandler<CreateTableRequest,CreateTableResult> asyncHandler)
The CreateTable operation adds a new table to an existing database in your account. In an Amazon Web Services account, table names must be at least unique within each Region if they are in the same database. You may have identical table names in the same Region if the tables are in separate databases. While creating the table, you must specify the table name, database name, and the retention properties. Service quotas apply. See code sample for details.
createTableRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteDatabaseResult> deleteDatabaseAsync(DeleteDatabaseRequest deleteDatabaseRequest)
Deletes a given Timestream database. This is an irreversible operation. After a database is deleted, the time series data from its tables cannot be recovered.
All tables in the database must be deleted first, or a ValidationException error will be thrown.
Due to the nature of distributed retries, the operation can return either success or a ResourceNotFoundException. Clients should consider them equivalent.
See code sample for details.
deleteDatabaseRequest - Future<DeleteDatabaseResult> deleteDatabaseAsync(DeleteDatabaseRequest deleteDatabaseRequest, AsyncHandler<DeleteDatabaseRequest,DeleteDatabaseResult> asyncHandler)
Deletes a given Timestream database. This is an irreversible operation. After a database is deleted, the time series data from its tables cannot be recovered.
All tables in the database must be deleted first, or a ValidationException error will be thrown.
Due to the nature of distributed retries, the operation can return either success or a ResourceNotFoundException. Clients should consider them equivalent.
See code sample for details.
deleteDatabaseRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DeleteTableResult> deleteTableAsync(DeleteTableRequest deleteTableRequest)
Deletes a given Timestream table. This is an irreversible operation. After a Timestream database table is deleted, the time series data stored in the table cannot be recovered.
Due to the nature of distributed retries, the operation can return either success or a ResourceNotFoundException. Clients should consider them equivalent.
See code sample for details.
deleteTableRequest - Future<DeleteTableResult> deleteTableAsync(DeleteTableRequest deleteTableRequest, AsyncHandler<DeleteTableRequest,DeleteTableResult> asyncHandler)
Deletes a given Timestream table. This is an irreversible operation. After a Timestream database table is deleted, the time series data stored in the table cannot be recovered.
Due to the nature of distributed retries, the operation can return either success or a ResourceNotFoundException. Clients should consider them equivalent.
See code sample for details.
deleteTableRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DescribeDatabaseResult> describeDatabaseAsync(DescribeDatabaseRequest describeDatabaseRequest)
Returns information about the database, including the database name, time that the database was created, and the total number of tables found within the database. Service quotas apply. See code sample for details.
describeDatabaseRequest - Future<DescribeDatabaseResult> describeDatabaseAsync(DescribeDatabaseRequest describeDatabaseRequest, AsyncHandler<DescribeDatabaseRequest,DescribeDatabaseResult> asyncHandler)
Returns information about the database, including the database name, time that the database was created, and the total number of tables found within the database. Service quotas apply. See code sample for details.
describeDatabaseRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DescribeEndpointsResult> describeEndpointsAsync(DescribeEndpointsRequest describeEndpointsRequest)
DescribeEndpoints returns a list of available endpoints to make Timestream API calls against. This API is available through both Write and Query.
Because the Timestream SDKs are designed to transparently work with the service’s architecture, including the management and mapping of the service endpoints, it is not recommended that you use this API unless:
You are using VPC endpoints (Amazon Web Services PrivateLink) with Timestream
Your application uses a programming language that does not yet have SDK support
You require better control over the client-side implementation
For detailed information on how and when to use and implement DescribeEndpoints, see The Endpoint Discovery Pattern.
describeEndpointsRequest - Future<DescribeEndpointsResult> describeEndpointsAsync(DescribeEndpointsRequest describeEndpointsRequest, AsyncHandler<DescribeEndpointsRequest,DescribeEndpointsResult> asyncHandler)
DescribeEndpoints returns a list of available endpoints to make Timestream API calls against. This API is available through both Write and Query.
Because the Timestream SDKs are designed to transparently work with the service’s architecture, including the management and mapping of the service endpoints, it is not recommended that you use this API unless:
You are using VPC endpoints (Amazon Web Services PrivateLink) with Timestream
Your application uses a programming language that does not yet have SDK support
You require better control over the client-side implementation
For detailed information on how and when to use and implement DescribeEndpoints, see The Endpoint Discovery Pattern.
describeEndpointsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<DescribeTableResult> describeTableAsync(DescribeTableRequest describeTableRequest)
Returns information about the table, including the table name, database name, retention duration of the memory store and the magnetic store. Service quotas apply. See code sample for details.
describeTableRequest - Future<DescribeTableResult> describeTableAsync(DescribeTableRequest describeTableRequest, AsyncHandler<DescribeTableRequest,DescribeTableResult> asyncHandler)
Returns information about the table, including the table name, database name, retention duration of the memory store and the magnetic store. Service quotas apply. See code sample for details.
describeTableRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListDatabasesResult> listDatabasesAsync(ListDatabasesRequest listDatabasesRequest)
Returns a list of your Timestream databases. Service quotas apply. See code sample for details.
listDatabasesRequest - Future<ListDatabasesResult> listDatabasesAsync(ListDatabasesRequest listDatabasesRequest, AsyncHandler<ListDatabasesRequest,ListDatabasesResult> asyncHandler)
Returns a list of your Timestream databases. Service quotas apply. See code sample for details.
listDatabasesRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListTablesResult> listTablesAsync(ListTablesRequest listTablesRequest)
A list of tables, along with the name, status and retention properties of each table. See code sample for details.
listTablesRequest - Future<ListTablesResult> listTablesAsync(ListTablesRequest listTablesRequest, AsyncHandler<ListTablesRequest,ListTablesResult> asyncHandler)
A list of tables, along with the name, status and retention properties of each table. See code sample for details.
listTablesRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest)
List all tags on a Timestream resource.
listTagsForResourceRequest - Future<ListTagsForResourceResult> listTagsForResourceAsync(ListTagsForResourceRequest listTagsForResourceRequest, AsyncHandler<ListTagsForResourceRequest,ListTagsForResourceResult> asyncHandler)
List all tags on a Timestream resource.
listTagsForResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<TagResourceResult> tagResourceAsync(TagResourceRequest tagResourceRequest)
Associate a set of tags with a Timestream resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking.
tagResourceRequest - Future<TagResourceResult> tagResourceAsync(TagResourceRequest tagResourceRequest, AsyncHandler<TagResourceRequest,TagResourceResult> asyncHandler)
Associate a set of tags with a Timestream resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking.
tagResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest untagResourceRequest)
Removes the association of tags from a Timestream resource.
untagResourceRequest - Future<UntagResourceResult> untagResourceAsync(UntagResourceRequest untagResourceRequest, AsyncHandler<UntagResourceRequest,UntagResourceResult> asyncHandler)
Removes the association of tags from a Timestream resource.
untagResourceRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateDatabaseResult> updateDatabaseAsync(UpdateDatabaseRequest updateDatabaseRequest)
Modifies the KMS key for an existing database. While updating the database, you must specify the database name
and the identifier of the new KMS key to be used (KmsKeyId). If there are any concurrent
UpdateDatabase requests, first writer wins.
See code sample for details.
updateDatabaseRequest - Future<UpdateDatabaseResult> updateDatabaseAsync(UpdateDatabaseRequest updateDatabaseRequest, AsyncHandler<UpdateDatabaseRequest,UpdateDatabaseResult> asyncHandler)
Modifies the KMS key for an existing database. While updating the database, you must specify the database name
and the identifier of the new KMS key to be used (KmsKeyId). If there are any concurrent
UpdateDatabase requests, first writer wins.
See code sample for details.
updateDatabaseRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<UpdateTableResult> updateTableAsync(UpdateTableRequest updateTableRequest)
Modifies the retention duration of the memory store and magnetic store for your Timestream table. Note that the change in retention duration takes effect immediately. For example, if the retention period of the memory store was initially set to 2 hours and then changed to 24 hours, the memory store will be capable of holding 24 hours of data, but will be populated with 24 hours of data 22 hours after this change was made. Timestream does not retrieve data from the magnetic store to populate the memory store.
See code sample for details.
updateTableRequest - Future<UpdateTableResult> updateTableAsync(UpdateTableRequest updateTableRequest, AsyncHandler<UpdateTableRequest,UpdateTableResult> asyncHandler)
Modifies the retention duration of the memory store and magnetic store for your Timestream table. Note that the change in retention duration takes effect immediately. For example, if the retention period of the memory store was initially set to 2 hours and then changed to 24 hours, the memory store will be capable of holding 24 hours of data, but will be populated with 24 hours of data 22 hours after this change was made. Timestream does not retrieve data from the magnetic store to populate the memory store.
See code sample for details.
updateTableRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.Future<WriteRecordsResult> writeRecordsAsync(WriteRecordsRequest writeRecordsRequest)
The WriteRecords operation enables you to write your time series data into Timestream. You can specify a single data point or a batch of data points to be inserted into the system. Timestream offers you with a flexible schema that auto detects the column names and data types for your Timestream tables based on the dimension names and data types of the data points you specify when invoking writes into the database. Timestream support eventual consistency read semantics. This means that when you query data immediately after writing a batch of data into Timestream, the query results might not reflect the results of a recently completed write operation. The results may also include some stale data. If you repeat the query request after a short time, the results should return the latest data. Service quotas apply.
See code sample for details.
Upserts
You can use the Version parameter in a WriteRecords request to update data points.
Timestream tracks a version number with each record. Version defaults to 1 when not
specified for the record in the request. Timestream will update an existing record’s measure value along with its
Version upon receiving a write request with a higher Version number for that record.
Upon receiving an update request where the measure value is the same as that of the existing record, Timestream
still updates Version, if it is greater than the existing value of Version. You can
update a data point as many times as desired, as long as the value of Version continuously
increases.
For example, suppose you write a new record without indicating Version in the request. Timestream
will store this record, and set Version to 1. Now, suppose you try to update this
record with a WriteRecords request of the same record with a different measure value but, like
before, do not provide Version. In this case, Timestream will reject this update with a
RejectedRecordsException since the updated record’s version is not greater than the existing value
of Version. However, if you were to resend the update request with Version set to 2,
Timestream would then succeed in updating the record’s value, and the Version would be set to
2. Next, suppose you sent a WriteRecords request with this same record and an identical
measure value, but with Version set to 3. In this case, Timestream would only update
Version to 3. Any further updates would need to send a version number greater than
3, or the update requests would receive a RejectedRecordsException.
writeRecordsRequest - Future<WriteRecordsResult> writeRecordsAsync(WriteRecordsRequest writeRecordsRequest, AsyncHandler<WriteRecordsRequest,WriteRecordsResult> asyncHandler)
The WriteRecords operation enables you to write your time series data into Timestream. You can specify a single data point or a batch of data points to be inserted into the system. Timestream offers you with a flexible schema that auto detects the column names and data types for your Timestream tables based on the dimension names and data types of the data points you specify when invoking writes into the database. Timestream support eventual consistency read semantics. This means that when you query data immediately after writing a batch of data into Timestream, the query results might not reflect the results of a recently completed write operation. The results may also include some stale data. If you repeat the query request after a short time, the results should return the latest data. Service quotas apply.
See code sample for details.
Upserts
You can use the Version parameter in a WriteRecords request to update data points.
Timestream tracks a version number with each record. Version defaults to 1 when not
specified for the record in the request. Timestream will update an existing record’s measure value along with its
Version upon receiving a write request with a higher Version number for that record.
Upon receiving an update request where the measure value is the same as that of the existing record, Timestream
still updates Version, if it is greater than the existing value of Version. You can
update a data point as many times as desired, as long as the value of Version continuously
increases.
For example, suppose you write a new record without indicating Version in the request. Timestream
will store this record, and set Version to 1. Now, suppose you try to update this
record with a WriteRecords request of the same record with a different measure value but, like
before, do not provide Version. In this case, Timestream will reject this update with a
RejectedRecordsException since the updated record’s version is not greater than the existing value
of Version. However, if you were to resend the update request with Version set to 2,
Timestream would then succeed in updating the record’s value, and the Version would be set to
2. Next, suppose you sent a WriteRecords request with this same record and an identical
measure value, but with Version set to 3. In this case, Timestream would only update
Version to 3. Any further updates would need to send a version number greater than
3, or the update requests would receive a RejectedRecordsException.
writeRecordsRequest - asyncHandler - Asynchronous callback handler for events in the lifecycle of the request. Users can provide an
implementation of the callback methods in this interface to receive notification of successful or
unsuccessful completion of the operation.