@Generated(value="software.amazon.awssdk:codegen") @ThreadSafe public interface EvidentlyAsyncClient extends SdkClient
builder() method.
You can use Amazon CloudWatch Evidently to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to your users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
You can also conduct A/B experiments to make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it using statistical methods. It also provides clear recommendations about which variations perform better. You can test both user-facing features and backend features.
| Modifier and Type | Field and Description |
|---|---|
static String |
SERVICE_METADATA_ID
Value for looking up the service's metadata from the
ServiceMetadataProvider. |
static String |
SERVICE_NAME |
| Modifier and Type | Method and Description |
|---|---|
default CompletableFuture<BatchEvaluateFeatureResponse> |
batchEvaluateFeature(BatchEvaluateFeatureRequest batchEvaluateFeatureRequest)
This operation assigns feature variation to user sessions.
|
default CompletableFuture<BatchEvaluateFeatureResponse> |
batchEvaluateFeature(Consumer<BatchEvaluateFeatureRequest.Builder> batchEvaluateFeatureRequest)
This operation assigns feature variation to user sessions.
|
static EvidentlyAsyncClientBuilder |
builder()
Create a builder that can be used to configure and create a
EvidentlyAsyncClient. |
static EvidentlyAsyncClient |
create()
Create a
EvidentlyAsyncClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider. |
default CompletableFuture<CreateExperimentResponse> |
createExperiment(Consumer<CreateExperimentRequest.Builder> createExperimentRequest)
Creates an Evidently experiment.
|
default CompletableFuture<CreateExperimentResponse> |
createExperiment(CreateExperimentRequest createExperimentRequest)
Creates an Evidently experiment.
|
default CompletableFuture<CreateFeatureResponse> |
createFeature(Consumer<CreateFeatureRequest.Builder> createFeatureRequest)
Creates an Evidently feature that you want to launch or test.
|
default CompletableFuture<CreateFeatureResponse> |
createFeature(CreateFeatureRequest createFeatureRequest)
Creates an Evidently feature that you want to launch or test.
|
default CompletableFuture<CreateLaunchResponse> |
createLaunch(Consumer<CreateLaunchRequest.Builder> createLaunchRequest)
Creates a launch of a given feature.
|
default CompletableFuture<CreateLaunchResponse> |
createLaunch(CreateLaunchRequest createLaunchRequest)
Creates a launch of a given feature.
|
default CompletableFuture<CreateProjectResponse> |
createProject(Consumer<CreateProjectRequest.Builder> createProjectRequest)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments.
|
default CompletableFuture<CreateProjectResponse> |
createProject(CreateProjectRequest createProjectRequest)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments.
|
default CompletableFuture<CreateSegmentResponse> |
createSegment(Consumer<CreateSegmentRequest.Builder> createSegmentRequest)
Use this operation to define a segment of your audience.
|
default CompletableFuture<CreateSegmentResponse> |
createSegment(CreateSegmentRequest createSegmentRequest)
Use this operation to define a segment of your audience.
|
default CompletableFuture<DeleteExperimentResponse> |
deleteExperiment(Consumer<DeleteExperimentRequest.Builder> deleteExperimentRequest)
Deletes an Evidently experiment.
|
default CompletableFuture<DeleteExperimentResponse> |
deleteExperiment(DeleteExperimentRequest deleteExperimentRequest)
Deletes an Evidently experiment.
|
default CompletableFuture<DeleteFeatureResponse> |
deleteFeature(Consumer<DeleteFeatureRequest.Builder> deleteFeatureRequest)
Deletes an Evidently feature.
|
default CompletableFuture<DeleteFeatureResponse> |
deleteFeature(DeleteFeatureRequest deleteFeatureRequest)
Deletes an Evidently feature.
|
default CompletableFuture<DeleteLaunchResponse> |
deleteLaunch(Consumer<DeleteLaunchRequest.Builder> deleteLaunchRequest)
Deletes an Evidently launch.
|
default CompletableFuture<DeleteLaunchResponse> |
deleteLaunch(DeleteLaunchRequest deleteLaunchRequest)
Deletes an Evidently launch.
|
default CompletableFuture<DeleteProjectResponse> |
deleteProject(Consumer<DeleteProjectRequest.Builder> deleteProjectRequest)
Deletes an Evidently project.
|
default CompletableFuture<DeleteProjectResponse> |
deleteProject(DeleteProjectRequest deleteProjectRequest)
Deletes an Evidently project.
|
default CompletableFuture<DeleteSegmentResponse> |
deleteSegment(Consumer<DeleteSegmentRequest.Builder> deleteSegmentRequest)
Deletes a segment.
|
default CompletableFuture<DeleteSegmentResponse> |
deleteSegment(DeleteSegmentRequest deleteSegmentRequest)
Deletes a segment.
|
default CompletableFuture<EvaluateFeatureResponse> |
evaluateFeature(Consumer<EvaluateFeatureRequest.Builder> evaluateFeatureRequest)
This operation assigns a feature variation to one given user session.
|
default CompletableFuture<EvaluateFeatureResponse> |
evaluateFeature(EvaluateFeatureRequest evaluateFeatureRequest)
This operation assigns a feature variation to one given user session.
|
default CompletableFuture<GetExperimentResponse> |
getExperiment(Consumer<GetExperimentRequest.Builder> getExperimentRequest)
Returns the details about one experiment.
|
default CompletableFuture<GetExperimentResponse> |
getExperiment(GetExperimentRequest getExperimentRequest)
Returns the details about one experiment.
|
default CompletableFuture<GetExperimentResultsResponse> |
getExperimentResults(Consumer<GetExperimentResultsRequest.Builder> getExperimentResultsRequest)
Retrieves the results of a running or completed experiment.
|
default CompletableFuture<GetExperimentResultsResponse> |
getExperimentResults(GetExperimentResultsRequest getExperimentResultsRequest)
Retrieves the results of a running or completed experiment.
|
default CompletableFuture<GetFeatureResponse> |
getFeature(Consumer<GetFeatureRequest.Builder> getFeatureRequest)
Returns the details about one feature.
|
default CompletableFuture<GetFeatureResponse> |
getFeature(GetFeatureRequest getFeatureRequest)
Returns the details about one feature.
|
default CompletableFuture<GetLaunchResponse> |
getLaunch(Consumer<GetLaunchRequest.Builder> getLaunchRequest)
Returns the details about one launch.
|
default CompletableFuture<GetLaunchResponse> |
getLaunch(GetLaunchRequest getLaunchRequest)
Returns the details about one launch.
|
default CompletableFuture<GetProjectResponse> |
getProject(Consumer<GetProjectRequest.Builder> getProjectRequest)
Returns the details about one launch.
|
default CompletableFuture<GetProjectResponse> |
getProject(GetProjectRequest getProjectRequest)
Returns the details about one launch.
|
default CompletableFuture<GetSegmentResponse> |
getSegment(Consumer<GetSegmentRequest.Builder> getSegmentRequest)
Returns information about the specified segment.
|
default CompletableFuture<GetSegmentResponse> |
getSegment(GetSegmentRequest getSegmentRequest)
Returns information about the specified segment.
|
default CompletableFuture<ListExperimentsResponse> |
listExperiments(Consumer<ListExperimentsRequest.Builder> listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
|
default CompletableFuture<ListExperimentsResponse> |
listExperiments(ListExperimentsRequest listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
|
default ListExperimentsPublisher |
listExperimentsPaginator(Consumer<ListExperimentsRequest.Builder> listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
|
default ListExperimentsPublisher |
listExperimentsPaginator(ListExperimentsRequest listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
|
default CompletableFuture<ListFeaturesResponse> |
listFeatures(Consumer<ListFeaturesRequest.Builder> listFeaturesRequest)
Returns configuration details about all the features in the specified project.
|
default CompletableFuture<ListFeaturesResponse> |
listFeatures(ListFeaturesRequest listFeaturesRequest)
Returns configuration details about all the features in the specified project.
|
default ListFeaturesPublisher |
listFeaturesPaginator(Consumer<ListFeaturesRequest.Builder> listFeaturesRequest)
Returns configuration details about all the features in the specified project.
|
default ListFeaturesPublisher |
listFeaturesPaginator(ListFeaturesRequest listFeaturesRequest)
Returns configuration details about all the features in the specified project.
|
default CompletableFuture<ListLaunchesResponse> |
listLaunches(Consumer<ListLaunchesRequest.Builder> listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
|
default CompletableFuture<ListLaunchesResponse> |
listLaunches(ListLaunchesRequest listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
|
default ListLaunchesPublisher |
listLaunchesPaginator(Consumer<ListLaunchesRequest.Builder> listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
|
default ListLaunchesPublisher |
listLaunchesPaginator(ListLaunchesRequest listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
|
default CompletableFuture<ListProjectsResponse> |
listProjects(Consumer<ListProjectsRequest.Builder> listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
|
default CompletableFuture<ListProjectsResponse> |
listProjects(ListProjectsRequest listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
|
default ListProjectsPublisher |
listProjectsPaginator(Consumer<ListProjectsRequest.Builder> listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
|
default ListProjectsPublisher |
listProjectsPaginator(ListProjectsRequest listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
|
default CompletableFuture<ListSegmentReferencesResponse> |
listSegmentReferences(Consumer<ListSegmentReferencesRequest.Builder> listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
|
default CompletableFuture<ListSegmentReferencesResponse> |
listSegmentReferences(ListSegmentReferencesRequest listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
|
default ListSegmentReferencesPublisher |
listSegmentReferencesPaginator(Consumer<ListSegmentReferencesRequest.Builder> listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
|
default ListSegmentReferencesPublisher |
listSegmentReferencesPaginator(ListSegmentReferencesRequest listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
|
default CompletableFuture<ListSegmentsResponse> |
listSegments(Consumer<ListSegmentsRequest.Builder> listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
|
default CompletableFuture<ListSegmentsResponse> |
listSegments(ListSegmentsRequest listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
|
default ListSegmentsPublisher |
listSegmentsPaginator(Consumer<ListSegmentsRequest.Builder> listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
|
default ListSegmentsPublisher |
listSegmentsPaginator(ListSegmentsRequest listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
|
default CompletableFuture<ListTagsForResourceResponse> |
listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)
Displays the tags associated with an Evidently resource.
|
default CompletableFuture<ListTagsForResourceResponse> |
listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)
Displays the tags associated with an Evidently resource.
|
default CompletableFuture<PutProjectEventsResponse> |
putProjectEvents(Consumer<PutProjectEventsRequest.Builder> putProjectEventsRequest)
Sends performance events to Evidently.
|
default CompletableFuture<PutProjectEventsResponse> |
putProjectEvents(PutProjectEventsRequest putProjectEventsRequest)
Sends performance events to Evidently.
|
default CompletableFuture<StartExperimentResponse> |
startExperiment(Consumer<StartExperimentRequest.Builder> startExperimentRequest)
Starts an existing experiment.
|
default CompletableFuture<StartExperimentResponse> |
startExperiment(StartExperimentRequest startExperimentRequest)
Starts an existing experiment.
|
default CompletableFuture<StartLaunchResponse> |
startLaunch(Consumer<StartLaunchRequest.Builder> startLaunchRequest)
Starts an existing launch.
|
default CompletableFuture<StartLaunchResponse> |
startLaunch(StartLaunchRequest startLaunchRequest)
Starts an existing launch.
|
default CompletableFuture<StopExperimentResponse> |
stopExperiment(Consumer<StopExperimentRequest.Builder> stopExperimentRequest)
Stops an experiment that is currently running.
|
default CompletableFuture<StopExperimentResponse> |
stopExperiment(StopExperimentRequest stopExperimentRequest)
Stops an experiment that is currently running.
|
default CompletableFuture<StopLaunchResponse> |
stopLaunch(Consumer<StopLaunchRequest.Builder> stopLaunchRequest)
Stops a launch that is currently running.
|
default CompletableFuture<StopLaunchResponse> |
stopLaunch(StopLaunchRequest stopLaunchRequest)
Stops a launch that is currently running.
|
default CompletableFuture<TagResourceResponse> |
tagResource(Consumer<TagResourceRequest.Builder> tagResourceRequest)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource.
|
default CompletableFuture<TagResourceResponse> |
tagResource(TagResourceRequest tagResourceRequest)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource.
|
default CompletableFuture<TestSegmentPatternResponse> |
testSegmentPattern(Consumer<TestSegmentPatternRequest.Builder> testSegmentPatternRequest)
Use this operation to test a rules pattern that you plan to use to create an audience segment.
|
default CompletableFuture<TestSegmentPatternResponse> |
testSegmentPattern(TestSegmentPatternRequest testSegmentPatternRequest)
Use this operation to test a rules pattern that you plan to use to create an audience segment.
|
default CompletableFuture<UntagResourceResponse> |
untagResource(Consumer<UntagResourceRequest.Builder> untagResourceRequest)
Removes one or more tags from the specified resource.
|
default CompletableFuture<UntagResourceResponse> |
untagResource(UntagResourceRequest untagResourceRequest)
Removes one or more tags from the specified resource.
|
default CompletableFuture<UpdateExperimentResponse> |
updateExperiment(Consumer<UpdateExperimentRequest.Builder> updateExperimentRequest)
Updates an Evidently experiment.
|
default CompletableFuture<UpdateExperimentResponse> |
updateExperiment(UpdateExperimentRequest updateExperimentRequest)
Updates an Evidently experiment.
|
default CompletableFuture<UpdateFeatureResponse> |
updateFeature(Consumer<UpdateFeatureRequest.Builder> updateFeatureRequest)
Updates an existing feature.
|
default CompletableFuture<UpdateFeatureResponse> |
updateFeature(UpdateFeatureRequest updateFeatureRequest)
Updates an existing feature.
|
default CompletableFuture<UpdateLaunchResponse> |
updateLaunch(Consumer<UpdateLaunchRequest.Builder> updateLaunchRequest)
Updates a launch of a given feature.
|
default CompletableFuture<UpdateLaunchResponse> |
updateLaunch(UpdateLaunchRequest updateLaunchRequest)
Updates a launch of a given feature.
|
default CompletableFuture<UpdateProjectResponse> |
updateProject(Consumer<UpdateProjectRequest.Builder> updateProjectRequest)
Updates the description of an existing project.
|
default CompletableFuture<UpdateProjectResponse> |
updateProject(UpdateProjectRequest updateProjectRequest)
Updates the description of an existing project.
|
default CompletableFuture<UpdateProjectDataDeliveryResponse> |
updateProjectDataDelivery(Consumer<UpdateProjectDataDeliveryRequest.Builder> updateProjectDataDeliveryRequest)
Updates the data storage options for this project.
|
default CompletableFuture<UpdateProjectDataDeliveryResponse> |
updateProjectDataDelivery(UpdateProjectDataDeliveryRequest updateProjectDataDeliveryRequest)
Updates the data storage options for this project.
|
serviceNameclosestatic final String SERVICE_NAME
static final String SERVICE_METADATA_ID
ServiceMetadataProvider.default CompletableFuture<BatchEvaluateFeatureResponse> batchEvaluateFeature(BatchEvaluateFeatureRequest batchEvaluateFeatureRequest)
This operation assigns feature variation to user sessions. For each user session, you pass in an
entityID that represents the user. Evidently then checks the evaluation rules and assigns the
variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
Next, if there is a launch of the feature, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment. If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
batchEvaluateFeatureRequest - default CompletableFuture<BatchEvaluateFeatureResponse> batchEvaluateFeature(Consumer<BatchEvaluateFeatureRequest.Builder> batchEvaluateFeatureRequest)
This operation assigns feature variation to user sessions. For each user session, you pass in an
entityID that represents the user. Evidently then checks the evaluation rules and assigns the
variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
Next, if there is a launch of the feature, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment. If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
This is a convenience which creates an instance of the BatchEvaluateFeatureRequest.Builder avoiding the
need to create one manually via BatchEvaluateFeatureRequest.builder()
batchEvaluateFeatureRequest - A Consumer that will call methods on BatchEvaluateFeatureRequest.Builder to create a
request.default CompletableFuture<CreateExperimentResponse> createExperiment(CreateExperimentRequest createExperimentRequest)
Creates an Evidently experiment. Before you create an experiment, you must create the feature to use for the experiment.
An experiment helps you make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it by statistical methods, and provides clear recommendations about which variations perform better.
You can optionally specify a segment to have the experiment consider only certain audience types in
the experiment, such as using only user sessions from a certain location or who use a certain internet browser.
Don't use this operation to update an existing experiment. Instead, use UpdateExperiment.
createExperimentRequest - default CompletableFuture<CreateExperimentResponse> createExperiment(Consumer<CreateExperimentRequest.Builder> createExperimentRequest)
Creates an Evidently experiment. Before you create an experiment, you must create the feature to use for the experiment.
An experiment helps you make feature design decisions based on evidence and data. An experiment can test as many as five variations at once. Evidently collects experiment data and analyzes it by statistical methods, and provides clear recommendations about which variations perform better.
You can optionally specify a segment to have the experiment consider only certain audience types in
the experiment, such as using only user sessions from a certain location or who use a certain internet browser.
Don't use this operation to update an existing experiment. Instead, use UpdateExperiment.
This is a convenience which creates an instance of the CreateExperimentRequest.Builder avoiding the need
to create one manually via CreateExperimentRequest.builder()
createExperimentRequest - A Consumer that will call methods on CreateExperimentRequest.Builder to create a request.default CompletableFuture<CreateFeatureResponse> createFeature(CreateFeatureRequest createFeatureRequest)
Creates an Evidently feature that you want to launch or test. You can define up to five variations of a feature, and use these variations in your launches and experiments. A feature must be created in a project. For information about creating a project, see CreateProject.
Don't use this operation to update an existing feature. Instead, use UpdateFeature.
createFeatureRequest - default CompletableFuture<CreateFeatureResponse> createFeature(Consumer<CreateFeatureRequest.Builder> createFeatureRequest)
Creates an Evidently feature that you want to launch or test. You can define up to five variations of a feature, and use these variations in your launches and experiments. A feature must be created in a project. For information about creating a project, see CreateProject.
Don't use this operation to update an existing feature. Instead, use UpdateFeature.
This is a convenience which creates an instance of the CreateFeatureRequest.Builder avoiding the need to
create one manually via CreateFeatureRequest.builder()
createFeatureRequest - A Consumer that will call methods on CreateFeatureRequest.Builder to create a request.default CompletableFuture<CreateLaunchResponse> createLaunch(CreateLaunchRequest createLaunchRequest)
Creates a launch of a given feature. Before you create a launch, you must create the feature to use for the launch.
You can use a launch to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to more users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
Don't use this operation to update an existing launch. Instead, use UpdateLaunch.
createLaunchRequest - default CompletableFuture<CreateLaunchResponse> createLaunch(Consumer<CreateLaunchRequest.Builder> createLaunchRequest)
Creates a launch of a given feature. Before you create a launch, you must create the feature to use for the launch.
You can use a launch to safely validate new features by serving them to a specified percentage of your users while you roll out the feature. You can monitor the performance of the new feature to help you decide when to ramp up traffic to more users. This helps you reduce risk and identify unintended consequences before you fully launch the feature.
Don't use this operation to update an existing launch. Instead, use UpdateLaunch.
This is a convenience which creates an instance of the CreateLaunchRequest.Builder avoiding the need to
create one manually via CreateLaunchRequest.builder()
createLaunchRequest - A Consumer that will call methods on CreateLaunchRequest.Builder to create a request.default CompletableFuture<CreateProjectResponse> createProject(CreateProjectRequest createProjectRequest)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments. Use projects to group similar features together.
To update an existing project, use UpdateProject.
createProjectRequest - default CompletableFuture<CreateProjectResponse> createProject(Consumer<CreateProjectRequest.Builder> createProjectRequest)
Creates a project, which is the logical object in Evidently that can contain features, launches, and experiments. Use projects to group similar features together.
To update an existing project, use UpdateProject.
This is a convenience which creates an instance of the CreateProjectRequest.Builder avoiding the need to
create one manually via CreateProjectRequest.builder()
createProjectRequest - A Consumer that will call methods on CreateProjectRequest.Builder to create a request.default CompletableFuture<CreateSegmentResponse> createSegment(CreateSegmentRequest createSegmentRequest)
Use this operation to define a segment of your audience. A segment is a portion of your audience that share one or more characteristics. Examples could be Chrome browser users, users in Europe, or Firefox browser users in Europe who also fit other criteria that your application collects, such as age.
Using a segment in an experiment limits that experiment to evaluate only the users who match the segment criteria. Using one or more segments in a launch allows you to define different traffic splits for the different audience segments.
For more information about segment pattern syntax, see Segment rule pattern syntax.
The pattern that you define for a segment is matched against the value of evaluationContext, which
is passed into Evidently in the EvaluateFeature operation, when Evidently assigns a feature variation to a user.
createSegmentRequest - default CompletableFuture<CreateSegmentResponse> createSegment(Consumer<CreateSegmentRequest.Builder> createSegmentRequest)
Use this operation to define a segment of your audience. A segment is a portion of your audience that share one or more characteristics. Examples could be Chrome browser users, users in Europe, or Firefox browser users in Europe who also fit other criteria that your application collects, such as age.
Using a segment in an experiment limits that experiment to evaluate only the users who match the segment criteria. Using one or more segments in a launch allows you to define different traffic splits for the different audience segments.
For more information about segment pattern syntax, see Segment rule pattern syntax.
The pattern that you define for a segment is matched against the value of evaluationContext, which
is passed into Evidently in the EvaluateFeature operation, when Evidently assigns a feature variation to a user.
This is a convenience which creates an instance of the CreateSegmentRequest.Builder avoiding the need to
create one manually via CreateSegmentRequest.builder()
createSegmentRequest - A Consumer that will call methods on CreateSegmentRequest.Builder to create a request.default CompletableFuture<DeleteExperimentResponse> deleteExperiment(DeleteExperimentRequest deleteExperimentRequest)
Deletes an Evidently experiment. The feature used for the experiment is not deleted.
To stop an experiment without deleting it, use StopExperiment.
deleteExperimentRequest - default CompletableFuture<DeleteExperimentResponse> deleteExperiment(Consumer<DeleteExperimentRequest.Builder> deleteExperimentRequest)
Deletes an Evidently experiment. The feature used for the experiment is not deleted.
To stop an experiment without deleting it, use StopExperiment.
This is a convenience which creates an instance of the DeleteExperimentRequest.Builder avoiding the need
to create one manually via DeleteExperimentRequest.builder()
deleteExperimentRequest - A Consumer that will call methods on DeleteExperimentRequest.Builder to create a request.default CompletableFuture<DeleteFeatureResponse> deleteFeature(DeleteFeatureRequest deleteFeatureRequest)
Deletes an Evidently feature.
deleteFeatureRequest - default CompletableFuture<DeleteFeatureResponse> deleteFeature(Consumer<DeleteFeatureRequest.Builder> deleteFeatureRequest)
Deletes an Evidently feature.
This is a convenience which creates an instance of the DeleteFeatureRequest.Builder avoiding the need to
create one manually via DeleteFeatureRequest.builder()
deleteFeatureRequest - A Consumer that will call methods on DeleteFeatureRequest.Builder to create a request.default CompletableFuture<DeleteLaunchResponse> deleteLaunch(DeleteLaunchRequest deleteLaunchRequest)
Deletes an Evidently launch. The feature used for the launch is not deleted.
To stop a launch without deleting it, use StopLaunch.
deleteLaunchRequest - default CompletableFuture<DeleteLaunchResponse> deleteLaunch(Consumer<DeleteLaunchRequest.Builder> deleteLaunchRequest)
Deletes an Evidently launch. The feature used for the launch is not deleted.
To stop a launch without deleting it, use StopLaunch.
This is a convenience which creates an instance of the DeleteLaunchRequest.Builder avoiding the need to
create one manually via DeleteLaunchRequest.builder()
deleteLaunchRequest - A Consumer that will call methods on DeleteLaunchRequest.Builder to create a request.default CompletableFuture<DeleteProjectResponse> deleteProject(DeleteProjectRequest deleteProjectRequest)
Deletes an Evidently project. Before you can delete a project, you must delete all the features that the project contains. To delete a feature, use DeleteFeature.
deleteProjectRequest - default CompletableFuture<DeleteProjectResponse> deleteProject(Consumer<DeleteProjectRequest.Builder> deleteProjectRequest)
Deletes an Evidently project. Before you can delete a project, you must delete all the features that the project contains. To delete a feature, use DeleteFeature.
This is a convenience which creates an instance of the DeleteProjectRequest.Builder avoiding the need to
create one manually via DeleteProjectRequest.builder()
deleteProjectRequest - A Consumer that will call methods on DeleteProjectRequest.Builder to create a request.default CompletableFuture<DeleteSegmentResponse> deleteSegment(DeleteSegmentRequest deleteSegmentRequest)
Deletes a segment. You can't delete a segment that is being used in a launch or experiment, even if that launch or experiment is not currently running.
deleteSegmentRequest - default CompletableFuture<DeleteSegmentResponse> deleteSegment(Consumer<DeleteSegmentRequest.Builder> deleteSegmentRequest)
Deletes a segment. You can't delete a segment that is being used in a launch or experiment, even if that launch or experiment is not currently running.
This is a convenience which creates an instance of the DeleteSegmentRequest.Builder avoiding the need to
create one manually via DeleteSegmentRequest.builder()
deleteSegmentRequest - A Consumer that will call methods on DeleteSegmentRequest.Builder to create a request.default CompletableFuture<EvaluateFeatureResponse> evaluateFeature(EvaluateFeatureRequest evaluateFeatureRequest)
This operation assigns a feature variation to one given user session. You pass in an entityID that
represents the user. Evidently then checks the evaluation rules and assigns the variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
If there is a current launch with this feature that uses segment overrides, and if the user session's
evaluationContext matches a segment rule defined in a segment override, the configuration in the
segment overrides is used. For more information about segments, see CreateSegment and Use
segments to focus your audience.
If there is a launch with no segment overrides, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment.
If the experiment uses a segment, then only user sessions with evaluationContext values that match
the segment rule are used in the experiment.
If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
evaluateFeatureRequest - default CompletableFuture<EvaluateFeatureResponse> evaluateFeature(Consumer<EvaluateFeatureRequest.Builder> evaluateFeatureRequest)
This operation assigns a feature variation to one given user session. You pass in an entityID that
represents the user. Evidently then checks the evaluation rules and assigns the variation.
The first rules that are evaluated are the override rules. If the user's entityID matches an
override rule, the user is served the variation specified by that rule.
If there is a current launch with this feature that uses segment overrides, and if the user session's
evaluationContext matches a segment rule defined in a segment override, the configuration in the
segment overrides is used. For more information about segments, see CreateSegment and Use
segments to focus your audience.
If there is a launch with no segment overrides, the user might be assigned to a variation in the launch. The chance of this depends on the percentage of users that are allocated to that launch. If the user is enrolled in the launch, the variation they are served depends on the allocation of the various feature variations used for the launch.
If the user is not assigned to a launch, and there is an ongoing experiment for this feature, the user might be assigned to a variation in the experiment. The chance of this depends on the percentage of users that are allocated to that experiment.
If the experiment uses a segment, then only user sessions with evaluationContext values that match
the segment rule are used in the experiment.
If the user is enrolled in the experiment, the variation they are served depends on the allocation of the various feature variations used for the experiment.
If the user is not assigned to a launch or experiment, they are served the default variation.
This is a convenience which creates an instance of the EvaluateFeatureRequest.Builder avoiding the need
to create one manually via EvaluateFeatureRequest.builder()
evaluateFeatureRequest - A Consumer that will call methods on EvaluateFeatureRequest.Builder to create a request.default CompletableFuture<GetExperimentResponse> getExperiment(GetExperimentRequest getExperimentRequest)
Returns the details about one experiment. You must already know the experiment name. To retrieve a list of experiments in your account, use ListExperiments.
getExperimentRequest - default CompletableFuture<GetExperimentResponse> getExperiment(Consumer<GetExperimentRequest.Builder> getExperimentRequest)
Returns the details about one experiment. You must already know the experiment name. To retrieve a list of experiments in your account, use ListExperiments.
This is a convenience which creates an instance of the GetExperimentRequest.Builder avoiding the need to
create one manually via GetExperimentRequest.builder()
getExperimentRequest - A Consumer that will call methods on GetExperimentRequest.Builder to create a request.default CompletableFuture<GetExperimentResultsResponse> getExperimentResults(GetExperimentResultsRequest getExperimentResultsRequest)
Retrieves the results of a running or completed experiment. No results are available until there have been 100 events for each variation and at least 10 minutes have passed since the start of the experiment. To increase the statistical power, Evidently performs an additional offline p-value analysis at the end of the experiment. Offline p-value analysis can detect statistical significance in some cases where the anytime p-values used during the experiment do not find statistical significance.
Experiment results are available up to 63 days after the start of the experiment. They are not available after that because of CloudWatch data retention policies.
getExperimentResultsRequest - default CompletableFuture<GetExperimentResultsResponse> getExperimentResults(Consumer<GetExperimentResultsRequest.Builder> getExperimentResultsRequest)
Retrieves the results of a running or completed experiment. No results are available until there have been 100 events for each variation and at least 10 minutes have passed since the start of the experiment. To increase the statistical power, Evidently performs an additional offline p-value analysis at the end of the experiment. Offline p-value analysis can detect statistical significance in some cases where the anytime p-values used during the experiment do not find statistical significance.
Experiment results are available up to 63 days after the start of the experiment. They are not available after that because of CloudWatch data retention policies.
This is a convenience which creates an instance of the GetExperimentResultsRequest.Builder avoiding the
need to create one manually via GetExperimentResultsRequest.builder()
getExperimentResultsRequest - A Consumer that will call methods on GetExperimentResultsRequest.Builder to create a
request.default CompletableFuture<GetFeatureResponse> getFeature(GetFeatureRequest getFeatureRequest)
Returns the details about one feature. You must already know the feature name. To retrieve a list of features in your account, use ListFeatures.
getFeatureRequest - default CompletableFuture<GetFeatureResponse> getFeature(Consumer<GetFeatureRequest.Builder> getFeatureRequest)
Returns the details about one feature. You must already know the feature name. To retrieve a list of features in your account, use ListFeatures.
This is a convenience which creates an instance of the GetFeatureRequest.Builder avoiding the need to
create one manually via GetFeatureRequest.builder()
getFeatureRequest - A Consumer that will call methods on GetFeatureRequest.Builder to create a request.default CompletableFuture<GetLaunchResponse> getLaunch(GetLaunchRequest getLaunchRequest)
Returns the details about one launch. You must already know the launch name. To retrieve a list of launches in your account, use ListLaunches.
getLaunchRequest - default CompletableFuture<GetLaunchResponse> getLaunch(Consumer<GetLaunchRequest.Builder> getLaunchRequest)
Returns the details about one launch. You must already know the launch name. To retrieve a list of launches in your account, use ListLaunches.
This is a convenience which creates an instance of the GetLaunchRequest.Builder avoiding the need to
create one manually via GetLaunchRequest.builder()
getLaunchRequest - A Consumer that will call methods on GetLaunchRequest.Builder to create a request.default CompletableFuture<GetProjectResponse> getProject(GetProjectRequest getProjectRequest)
Returns the details about one launch. You must already know the project name. To retrieve a list of projects in your account, use ListProjects.
getProjectRequest - default CompletableFuture<GetProjectResponse> getProject(Consumer<GetProjectRequest.Builder> getProjectRequest)
Returns the details about one launch. You must already know the project name. To retrieve a list of projects in your account, use ListProjects.
This is a convenience which creates an instance of the GetProjectRequest.Builder avoiding the need to
create one manually via GetProjectRequest.builder()
getProjectRequest - A Consumer that will call methods on GetProjectRequest.Builder to create a request.default CompletableFuture<GetSegmentResponse> getSegment(GetSegmentRequest getSegmentRequest)
Returns information about the specified segment. Specify the segment you want to view by specifying its ARN.
getSegmentRequest - default CompletableFuture<GetSegmentResponse> getSegment(Consumer<GetSegmentRequest.Builder> getSegmentRequest)
Returns information about the specified segment. Specify the segment you want to view by specifying its ARN.
This is a convenience which creates an instance of the GetSegmentRequest.Builder avoiding the need to
create one manually via GetSegmentRequest.builder()
getSegmentRequest - A Consumer that will call methods on GetSegmentRequest.Builder to create a request.default CompletableFuture<ListExperimentsResponse> listExperiments(ListExperimentsRequest listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
listExperimentsRequest - default CompletableFuture<ListExperimentsResponse> listExperiments(Consumer<ListExperimentsRequest.Builder> listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
This is a convenience which creates an instance of the ListExperimentsRequest.Builder avoiding the need
to create one manually via ListExperimentsRequest.builder()
listExperimentsRequest - A Consumer that will call methods on ListExperimentsRequest.Builder to create a request.default ListExperimentsPublisher listExperimentsPaginator(ListExperimentsRequest listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
This is a variant of
listExperiments(software.amazon.awssdk.services.evidently.model.ListExperimentsRequest) operation. The
return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will
internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListExperimentsPublisher publisher = client.listExperimentsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListExperimentsPublisher publisher = client.listExperimentsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListExperimentsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListExperimentsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listExperiments(software.amazon.awssdk.services.evidently.model.ListExperimentsRequest) operation.
listExperimentsRequest - default ListExperimentsPublisher listExperimentsPaginator(Consumer<ListExperimentsRequest.Builder> listExperimentsRequest)
Returns configuration details about all the experiments in the specified project.
This is a variant of
listExperiments(software.amazon.awssdk.services.evidently.model.ListExperimentsRequest) operation. The
return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will
internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListExperimentsPublisher publisher = client.listExperimentsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListExperimentsPublisher publisher = client.listExperimentsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListExperimentsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListExperimentsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listExperiments(software.amazon.awssdk.services.evidently.model.ListExperimentsRequest) operation.
This is a convenience which creates an instance of the ListExperimentsRequest.Builder avoiding the need
to create one manually via ListExperimentsRequest.builder()
listExperimentsRequest - A Consumer that will call methods on ListExperimentsRequest.Builder to create a request.default CompletableFuture<ListFeaturesResponse> listFeatures(ListFeaturesRequest listFeaturesRequest)
Returns configuration details about all the features in the specified project.
listFeaturesRequest - default CompletableFuture<ListFeaturesResponse> listFeatures(Consumer<ListFeaturesRequest.Builder> listFeaturesRequest)
Returns configuration details about all the features in the specified project.
This is a convenience which creates an instance of the ListFeaturesRequest.Builder avoiding the need to
create one manually via ListFeaturesRequest.builder()
listFeaturesRequest - A Consumer that will call methods on ListFeaturesRequest.Builder to create a request.default ListFeaturesPublisher listFeaturesPaginator(ListFeaturesRequest listFeaturesRequest)
Returns configuration details about all the features in the specified project.
This is a variant of listFeatures(software.amazon.awssdk.services.evidently.model.ListFeaturesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListFeaturesPublisher publisher = client.listFeaturesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListFeaturesPublisher publisher = client.listFeaturesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListFeaturesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListFeaturesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listFeatures(software.amazon.awssdk.services.evidently.model.ListFeaturesRequest) operation.
listFeaturesRequest - default ListFeaturesPublisher listFeaturesPaginator(Consumer<ListFeaturesRequest.Builder> listFeaturesRequest)
Returns configuration details about all the features in the specified project.
This is a variant of listFeatures(software.amazon.awssdk.services.evidently.model.ListFeaturesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListFeaturesPublisher publisher = client.listFeaturesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListFeaturesPublisher publisher = client.listFeaturesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListFeaturesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListFeaturesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listFeatures(software.amazon.awssdk.services.evidently.model.ListFeaturesRequest) operation.
This is a convenience which creates an instance of the ListFeaturesRequest.Builder avoiding the need to
create one manually via ListFeaturesRequest.builder()
listFeaturesRequest - A Consumer that will call methods on ListFeaturesRequest.Builder to create a request.default CompletableFuture<ListLaunchesResponse> listLaunches(ListLaunchesRequest listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
listLaunchesRequest - default CompletableFuture<ListLaunchesResponse> listLaunches(Consumer<ListLaunchesRequest.Builder> listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
This is a convenience which creates an instance of the ListLaunchesRequest.Builder avoiding the need to
create one manually via ListLaunchesRequest.builder()
listLaunchesRequest - A Consumer that will call methods on ListLaunchesRequest.Builder to create a request.default ListLaunchesPublisher listLaunchesPaginator(ListLaunchesRequest listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
This is a variant of listLaunches(software.amazon.awssdk.services.evidently.model.ListLaunchesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListLaunchesPublisher publisher = client.listLaunchesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListLaunchesPublisher publisher = client.listLaunchesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListLaunchesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListLaunchesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listLaunches(software.amazon.awssdk.services.evidently.model.ListLaunchesRequest) operation.
listLaunchesRequest - default ListLaunchesPublisher listLaunchesPaginator(Consumer<ListLaunchesRequest.Builder> listLaunchesRequest)
Returns configuration details about all the launches in the specified project.
This is a variant of listLaunches(software.amazon.awssdk.services.evidently.model.ListLaunchesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListLaunchesPublisher publisher = client.listLaunchesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListLaunchesPublisher publisher = client.listLaunchesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListLaunchesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListLaunchesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listLaunches(software.amazon.awssdk.services.evidently.model.ListLaunchesRequest) operation.
This is a convenience which creates an instance of the ListLaunchesRequest.Builder avoiding the need to
create one manually via ListLaunchesRequest.builder()
listLaunchesRequest - A Consumer that will call methods on ListLaunchesRequest.Builder to create a request.default CompletableFuture<ListProjectsResponse> listProjects(ListProjectsRequest listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
listProjectsRequest - default CompletableFuture<ListProjectsResponse> listProjects(Consumer<ListProjectsRequest.Builder> listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
This is a convenience which creates an instance of the ListProjectsRequest.Builder avoiding the need to
create one manually via ListProjectsRequest.builder()
listProjectsRequest - A Consumer that will call methods on ListProjectsRequest.Builder to create a request.default ListProjectsPublisher listProjectsPaginator(ListProjectsRequest listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
This is a variant of listProjects(software.amazon.awssdk.services.evidently.model.ListProjectsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListProjectsPublisher publisher = client.listProjectsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListProjectsPublisher publisher = client.listProjectsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListProjectsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListProjectsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listProjects(software.amazon.awssdk.services.evidently.model.ListProjectsRequest) operation.
listProjectsRequest - default ListProjectsPublisher listProjectsPaginator(Consumer<ListProjectsRequest.Builder> listProjectsRequest)
Returns configuration details about all the projects in the current Region in your account.
This is a variant of listProjects(software.amazon.awssdk.services.evidently.model.ListProjectsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListProjectsPublisher publisher = client.listProjectsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListProjectsPublisher publisher = client.listProjectsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListProjectsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListProjectsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listProjects(software.amazon.awssdk.services.evidently.model.ListProjectsRequest) operation.
This is a convenience which creates an instance of the ListProjectsRequest.Builder avoiding the need to
create one manually via ListProjectsRequest.builder()
listProjectsRequest - A Consumer that will call methods on ListProjectsRequest.Builder to create a request.default CompletableFuture<ListSegmentReferencesResponse> listSegmentReferences(ListSegmentReferencesRequest listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
listSegmentReferencesRequest - default CompletableFuture<ListSegmentReferencesResponse> listSegmentReferences(Consumer<ListSegmentReferencesRequest.Builder> listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
This is a convenience which creates an instance of the ListSegmentReferencesRequest.Builder avoiding the
need to create one manually via ListSegmentReferencesRequest.builder()
listSegmentReferencesRequest - A Consumer that will call methods on ListSegmentReferencesRequest.Builder to create a
request.default ListSegmentReferencesPublisher listSegmentReferencesPaginator(ListSegmentReferencesRequest listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
This is a variant of
listSegmentReferences(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListSegmentReferencesPublisher publisher = client.listSegmentReferencesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListSegmentReferencesPublisher publisher = client.listSegmentReferencesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListSegmentReferencesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listSegmentReferences(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesRequest)
operation.
listSegmentReferencesRequest - default ListSegmentReferencesPublisher listSegmentReferencesPaginator(Consumer<ListSegmentReferencesRequest.Builder> listSegmentReferencesRequest)
Use this operation to find which experiments or launches are using a specified segment.
This is a variant of
listSegmentReferences(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListSegmentReferencesPublisher publisher = client.listSegmentReferencesPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListSegmentReferencesPublisher publisher = client.listSegmentReferencesPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListSegmentReferencesResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listSegmentReferences(software.amazon.awssdk.services.evidently.model.ListSegmentReferencesRequest)
operation.
This is a convenience which creates an instance of the ListSegmentReferencesRequest.Builder avoiding the
need to create one manually via ListSegmentReferencesRequest.builder()
listSegmentReferencesRequest - A Consumer that will call methods on ListSegmentReferencesRequest.Builder to create a
request.default CompletableFuture<ListSegmentsResponse> listSegments(ListSegmentsRequest listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
listSegmentsRequest - default CompletableFuture<ListSegmentsResponse> listSegments(Consumer<ListSegmentsRequest.Builder> listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
This is a convenience which creates an instance of the ListSegmentsRequest.Builder avoiding the need to
create one manually via ListSegmentsRequest.builder()
listSegmentsRequest - A Consumer that will call methods on ListSegmentsRequest.Builder to create a request.default ListSegmentsPublisher listSegmentsPaginator(ListSegmentsRequest listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
This is a variant of listSegments(software.amazon.awssdk.services.evidently.model.ListSegmentsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListSegmentsPublisher publisher = client.listSegmentsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListSegmentsPublisher publisher = client.listSegmentsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListSegmentsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListSegmentsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listSegments(software.amazon.awssdk.services.evidently.model.ListSegmentsRequest) operation.
listSegmentsRequest - default ListSegmentsPublisher listSegmentsPaginator(Consumer<ListSegmentsRequest.Builder> listSegmentsRequest)
Returns a list of audience segments that you have created in your account in this Region.
This is a variant of listSegments(software.amazon.awssdk.services.evidently.model.ListSegmentsRequest)
operation. The return type is a custom publisher that can be subscribed to request a stream of response pages.
SDK will internally handle making service calls for you.
When the operation is called, an instance of this class is returned. At this point, no service calls are made yet
and so there is no guarantee that the request is valid. If there are errors in your request, you will see the
failures only after you start streaming the data. The subscribe method should be called as a request to start
streaming data. For more info, see
Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe
method will result in a new Subscription i.e., a new contract to stream data from the
starting request.
The following are few ways to use the response class:
1) Using the subscribe helper method
software.amazon.awssdk.services.evidently.paginators.ListSegmentsPublisher publisher = client.listSegmentsPaginator(request);
CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
future.get();
2) Using a custom subscriber
software.amazon.awssdk.services.evidently.paginators.ListSegmentsPublisher publisher = client.listSegmentsPaginator(request);
publisher.subscribe(new Subscriber<software.amazon.awssdk.services.evidently.model.ListSegmentsResponse>() {
public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
public void onNext(software.amazon.awssdk.services.evidently.model.ListSegmentsResponse response) { //... };
});
As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.
Please notice that the configuration of maxResults won't limit the number of results you get with the paginator. It only limits the number of results in each page.
Note: If you prefer to have control on service calls, use the
listSegments(software.amazon.awssdk.services.evidently.model.ListSegmentsRequest) operation.
This is a convenience which creates an instance of the ListSegmentsRequest.Builder avoiding the need to
create one manually via ListSegmentsRequest.builder()
listSegmentsRequest - A Consumer that will call methods on ListSegmentsRequest.Builder to create a request.default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)
Displays the tags associated with an Evidently resource.
listTagsForResourceRequest - default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)
Displays the tags associated with an Evidently resource.
This is a convenience which creates an instance of the ListTagsForResourceRequest.Builder avoiding the
need to create one manually via ListTagsForResourceRequest.builder()
listTagsForResourceRequest - A Consumer that will call methods on ListTagsForResourceRequest.Builder to create a
request.default CompletableFuture<PutProjectEventsResponse> putProjectEvents(PutProjectEventsRequest putProjectEventsRequest)
Sends performance events to Evidently. These events can be used to evaluate a launch or an experiment.
putProjectEventsRequest - default CompletableFuture<PutProjectEventsResponse> putProjectEvents(Consumer<PutProjectEventsRequest.Builder> putProjectEventsRequest)
Sends performance events to Evidently. These events can be used to evaluate a launch or an experiment.
This is a convenience which creates an instance of the PutProjectEventsRequest.Builder avoiding the need
to create one manually via PutProjectEventsRequest.builder()
putProjectEventsRequest - A Consumer that will call methods on PutProjectEventsRequest.Builder to create a request.default CompletableFuture<StartExperimentResponse> startExperiment(StartExperimentRequest startExperimentRequest)
Starts an existing experiment. To create an experiment, use CreateExperiment.
startExperimentRequest - default CompletableFuture<StartExperimentResponse> startExperiment(Consumer<StartExperimentRequest.Builder> startExperimentRequest)
Starts an existing experiment. To create an experiment, use CreateExperiment.
This is a convenience which creates an instance of the StartExperimentRequest.Builder avoiding the need
to create one manually via StartExperimentRequest.builder()
startExperimentRequest - A Consumer that will call methods on StartExperimentRequest.Builder to create a request.default CompletableFuture<StartLaunchResponse> startLaunch(StartLaunchRequest startLaunchRequest)
Starts an existing launch. To create a launch, use CreateLaunch.
startLaunchRequest - default CompletableFuture<StartLaunchResponse> startLaunch(Consumer<StartLaunchRequest.Builder> startLaunchRequest)
Starts an existing launch. To create a launch, use CreateLaunch.
This is a convenience which creates an instance of the StartLaunchRequest.Builder avoiding the need to
create one manually via StartLaunchRequest.builder()
startLaunchRequest - A Consumer that will call methods on StartLaunchRequest.Builder to create a request.default CompletableFuture<StopExperimentResponse> stopExperiment(StopExperimentRequest stopExperimentRequest)
Stops an experiment that is currently running. If you stop an experiment, you can't resume it or restart it.
stopExperimentRequest - default CompletableFuture<StopExperimentResponse> stopExperiment(Consumer<StopExperimentRequest.Builder> stopExperimentRequest)
Stops an experiment that is currently running. If you stop an experiment, you can't resume it or restart it.
This is a convenience which creates an instance of the StopExperimentRequest.Builder avoiding the need to
create one manually via StopExperimentRequest.builder()
stopExperimentRequest - A Consumer that will call methods on StopExperimentRequest.Builder to create a request.default CompletableFuture<StopLaunchResponse> stopLaunch(StopLaunchRequest stopLaunchRequest)
Stops a launch that is currently running. After you stop a launch, you will not be able to resume it or restart it. Also, it will not be evaluated as a rule for traffic allocation, and the traffic that was allocated to the launch will instead be available to the feature's experiment, if there is one. Otherwise, all traffic will be served the default variation after the launch is stopped.
stopLaunchRequest - default CompletableFuture<StopLaunchResponse> stopLaunch(Consumer<StopLaunchRequest.Builder> stopLaunchRequest)
Stops a launch that is currently running. After you stop a launch, you will not be able to resume it or restart it. Also, it will not be evaluated as a rule for traffic allocation, and the traffic that was allocated to the launch will instead be available to the feature's experiment, if there is one. Otherwise, all traffic will be served the default variation after the launch is stopped.
This is a convenience which creates an instance of the StopLaunchRequest.Builder avoiding the need to
create one manually via StopLaunchRequest.builder()
stopLaunchRequest - A Consumer that will call methods on StopLaunchRequest.Builder to create a request.default CompletableFuture<TagResourceResponse> tagResource(TagResourceRequest tagResourceRequest)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource. Projects, features, launches, and experiments can be tagged.
Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.
Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.
You can use the TagResource action with a resource that already has tags. If you specify a new tag
key for the resource, this tag is appended to the list of tags associated with the alarm. If you specify a tag
key that is already associated with the resource, the new tag value that you specify replaces the previous value
for that tag.
You can associate as many as 50 tags with a resource.
For more information, see Tagging Amazon Web Services resources.
tagResourceRequest - default CompletableFuture<TagResourceResponse> tagResource(Consumer<TagResourceRequest.Builder> tagResourceRequest)
Assigns one or more tags (key-value pairs) to the specified CloudWatch Evidently resource. Projects, features, launches, and experiments can be tagged.
Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.
Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.
You can use the TagResource action with a resource that already has tags. If you specify a new tag
key for the resource, this tag is appended to the list of tags associated with the alarm. If you specify a tag
key that is already associated with the resource, the new tag value that you specify replaces the previous value
for that tag.
You can associate as many as 50 tags with a resource.
For more information, see Tagging Amazon Web Services resources.
This is a convenience which creates an instance of the TagResourceRequest.Builder avoiding the need to
create one manually via TagResourceRequest.builder()
tagResourceRequest - A Consumer that will call methods on TagResourceRequest.Builder to create a request.default CompletableFuture<TestSegmentPatternResponse> testSegmentPattern(TestSegmentPatternRequest testSegmentPatternRequest)
Use this operation to test a rules pattern that you plan to use to create an audience segment. For more information about segments, see CreateSegment.
testSegmentPatternRequest - default CompletableFuture<TestSegmentPatternResponse> testSegmentPattern(Consumer<TestSegmentPatternRequest.Builder> testSegmentPatternRequest)
Use this operation to test a rules pattern that you plan to use to create an audience segment. For more information about segments, see CreateSegment.
This is a convenience which creates an instance of the TestSegmentPatternRequest.Builder avoiding the
need to create one manually via TestSegmentPatternRequest.builder()
testSegmentPatternRequest - A Consumer that will call methods on TestSegmentPatternRequest.Builder to create a
request.default CompletableFuture<UntagResourceResponse> untagResource(UntagResourceRequest untagResourceRequest)
Removes one or more tags from the specified resource.
untagResourceRequest - default CompletableFuture<UntagResourceResponse> untagResource(Consumer<UntagResourceRequest.Builder> untagResourceRequest)
Removes one or more tags from the specified resource.
This is a convenience which creates an instance of the UntagResourceRequest.Builder avoiding the need to
create one manually via UntagResourceRequest.builder()
untagResourceRequest - A Consumer that will call methods on UntagResourceRequest.Builder to create a request.default CompletableFuture<UpdateExperimentResponse> updateExperiment(UpdateExperimentRequest updateExperimentRequest)
Updates an Evidently experiment.
Don't use this operation to update an experiment's tag. Instead, use TagResource.
updateExperimentRequest - default CompletableFuture<UpdateExperimentResponse> updateExperiment(Consumer<UpdateExperimentRequest.Builder> updateExperimentRequest)
Updates an Evidently experiment.
Don't use this operation to update an experiment's tag. Instead, use TagResource.
This is a convenience which creates an instance of the UpdateExperimentRequest.Builder avoiding the need
to create one manually via UpdateExperimentRequest.builder()
updateExperimentRequest - A Consumer that will call methods on UpdateExperimentRequest.Builder to create a request.default CompletableFuture<UpdateFeatureResponse> updateFeature(UpdateFeatureRequest updateFeatureRequest)
Updates an existing feature.
You can't use this operation to update the tags of an existing feature. Instead, use TagResource.
updateFeatureRequest - default CompletableFuture<UpdateFeatureResponse> updateFeature(Consumer<UpdateFeatureRequest.Builder> updateFeatureRequest)
Updates an existing feature.
You can't use this operation to update the tags of an existing feature. Instead, use TagResource.
This is a convenience which creates an instance of the UpdateFeatureRequest.Builder avoiding the need to
create one manually via UpdateFeatureRequest.builder()
updateFeatureRequest - A Consumer that will call methods on UpdateFeatureRequest.Builder to create a request.default CompletableFuture<UpdateLaunchResponse> updateLaunch(UpdateLaunchRequest updateLaunchRequest)
Updates a launch of a given feature.
Don't use this operation to update the tags of an existing launch. Instead, use TagResource.
updateLaunchRequest - default CompletableFuture<UpdateLaunchResponse> updateLaunch(Consumer<UpdateLaunchRequest.Builder> updateLaunchRequest)
Updates a launch of a given feature.
Don't use this operation to update the tags of an existing launch. Instead, use TagResource.
This is a convenience which creates an instance of the UpdateLaunchRequest.Builder avoiding the need to
create one manually via UpdateLaunchRequest.builder()
updateLaunchRequest - A Consumer that will call methods on UpdateLaunchRequest.Builder to create a request.default CompletableFuture<UpdateProjectResponse> updateProject(UpdateProjectRequest updateProjectRequest)
Updates the description of an existing project.
To create a new project, use CreateProject.
Don't use this operation to update the data storage options of a project. Instead, use UpdateProjectDataDelivery.
Don't use this operation to update the tags of a project. Instead, use TagResource.
updateProjectRequest - default CompletableFuture<UpdateProjectResponse> updateProject(Consumer<UpdateProjectRequest.Builder> updateProjectRequest)
Updates the description of an existing project.
To create a new project, use CreateProject.
Don't use this operation to update the data storage options of a project. Instead, use UpdateProjectDataDelivery.
Don't use this operation to update the tags of a project. Instead, use TagResource.
This is a convenience which creates an instance of the UpdateProjectRequest.Builder avoiding the need to
create one manually via UpdateProjectRequest.builder()
updateProjectRequest - A Consumer that will call methods on UpdateProjectRequest.Builder to create a request.default CompletableFuture<UpdateProjectDataDeliveryResponse> updateProjectDataDelivery(UpdateProjectDataDeliveryRequest updateProjectDataDeliveryRequest)
Updates the data storage options for this project. If you store evaluation events, you an keep them and analyze them on your own. If you choose not to store evaluation events, Evidently deletes them after using them to produce metrics and other experiment results that you can view.
You can't specify both cloudWatchLogs and s3Destination in the same operation.
updateProjectDataDeliveryRequest - default CompletableFuture<UpdateProjectDataDeliveryResponse> updateProjectDataDelivery(Consumer<UpdateProjectDataDeliveryRequest.Builder> updateProjectDataDeliveryRequest)
Updates the data storage options for this project. If you store evaluation events, you an keep them and analyze them on your own. If you choose not to store evaluation events, Evidently deletes them after using them to produce metrics and other experiment results that you can view.
You can't specify both cloudWatchLogs and s3Destination in the same operation.
This is a convenience which creates an instance of the UpdateProjectDataDeliveryRequest.Builder avoiding
the need to create one manually via UpdateProjectDataDeliveryRequest.builder()
updateProjectDataDeliveryRequest - A Consumer that will call methods on UpdateProjectDataDeliveryRequest.Builder to create a
request.static EvidentlyAsyncClient create()
EvidentlyAsyncClient with the region loaded from the
DefaultAwsRegionProviderChain and credentials loaded from the
DefaultCredentialsProvider.static EvidentlyAsyncClientBuilder builder()
EvidentlyAsyncClient.Copyright © 2023. All rights reserved.