aws-sdk-iotsitewise 1.29.0 → 1.30.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b15c52a1ccd38347eb2aba9df61642c931974473f8cf1dbb75d4138fcc185b0a
-  data.tar.gz: b9057dc2dcac4f3547cd595937c345789ca85aa23439b6148133056e67398e54
+  metadata.gz: 98915b7d9ba277f8000f730d18b7fac03886583cb351dfe6a33c716668e80946
+  data.tar.gz: 178b1336e0b35362e53127dc1a48d70d73a09cf453d37d47a50e8070a1d9f678
 SHA512:
-  metadata.gz: 4e44df64d007dcb9bfa2c0dd6727a11a607201e94a058ee713e4ae438fd7c56eeb7a12f4f9769e513f34aae72687dc7f950609399341118150518e085b3cb27c
-  data.tar.gz: 90c043ed03ff2b66aad3cc968c26c4f8d55e31a6315672664f8ffc8a5385091926a781c21cc3c3327d630631672d4032a26d7a70ed7901df1ef157b4ac045adc
+  metadata.gz: b26cad8029eda4e60a68a01105323cd2f1786b26a20e3fa94894a0db11cff2761695fbe217ad1364cdcfdf7e89fe5cf24434671b3edf5edeeb4ac9f352bad903
+  data.tar.gz: b7c08bf25c4b9ea93a2840022059a79835f4a61e8fc5ea904608e3f1b5fb79d4017bf93e6484424c89d63772eb4f99b06a55bbc9d603d25ba08c2e493c8961cf

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.30.0 (2021-08-16)
+------------------
+
+* Feature - AWS IoT SiteWise added query window for the interpolation interval. AWS IoT SiteWise computes each interpolated value by using data points from the timestamp of each interval minus the window to the timestamp of each interval plus the window.
+
 1.29.0 (2021-08-03)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.29.0
+1.30.0

data/lib/aws-sdk-iotsitewise.rb

@@ -49,6 +49,6 @@ require_relative 'aws-sdk-iotsitewise/customizations'
 # @!group service
 module Aws::IoTSiteWise
 
-  GEM_VERSION = '1.29.0'
+  GEM_VERSION = '1.30.0'
 
 end

data/lib/aws-sdk-iotsitewise/client.rb

@@ -2522,7 +2522,45 @@ module Aws::IoTSiteWise
     # @option params [required, String] :type
     #   The interpolation type.
     #
-    #   Valid values: `LINEAR_INTERPOLATION`
+    #   Valid values: `LINEAR_INTERPOLATION | LOCF_INTERPOLATION`
+    #
+    #   For the `LOCF_INTERPOLATION` interpolation, if no data point is found
+    #   for an interval, IoT SiteWise returns the same interpolated value
+    #   calculated for the previous interval and carries forward this
+    #   interpolated value until a new data point is found.
+    #
+    #   For example, you can get the interpolated temperature values for a
+    #   wind turbine every 24 hours over a duration of 7 days. If the
+    #   `LOCF_INTERPOLATION` interpolation starts on July 1, 2021, at 9 AM,
+    #   IoT SiteWise uses the data points from July 1, 2021, at 9 AM to July
+    #   2, 2021, at 9 AM to compute the first interpolated value. If no data
+    #   points is found after 9 A.M. on July 2, 2021, IoT SiteWise uses the
+    #   same interpolated value for the rest of the days.
+    #
+    # @option params [Integer] :interval_window_in_seconds
+    #   The query interval for the window in seconds. IoT SiteWise computes
+    #   each interpolated value by using data points from the timestamp of
+    #   each interval minus the window to the timestamp of each interval plus
+    #   the window. If not specified, the window is between the start time
+    #   minus the interval and the end time plus the interval.
+    #
+    #   <note markdown="1"> * If you specify a value for the `intervalWindowInSeconds` parameter,
+    #     the `type` parameter must be `LINEAR_INTERPOLATION`.
+    #
+    #   * If no data point is found during the specified query window, IoT
+    #     SiteWise won't return an interpolated value for the interval. This
+    #     indicates that there's a gap in the ingested data points.
+    #
+    #    </note>
+    #
+    #   For example, you can get the interpolated temperature values for a
+    #   wind turbine every 24 hours over a duration of 7 days. If the
+    #   interpolation starts on July 1, 2021, at 9 AM with a window of 2
+    #   hours, IoT SiteWise uses the data points from 7 AM (9 AM - 2 hours) to
+    #   11 AM (9 AM + 2 hours) on July 2, 2021 to compute the first
+    #   interpolated value, uses the data points from 7 AM (9 AM - 2 hours) to
+    #   11 AM (9 AM + 2 hours) on July 3, 2021 to compute the second
+    #   interpolated value, and so on.
     #
     # @return [Types::GetInterpolatedAssetPropertyValuesResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
@@ -2546,6 +2584,7 @@ module Aws::IoTSiteWise
     #     next_token: "NextToken",
     #     max_results: 1,
     #     type: "InterpolationType", # required
+    #     interval_window_in_seconds: 1,
     #   })
     #
     # @example Response structure
@@ -4056,7 +4095,7 @@ module Aws::IoTSiteWise
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-iotsitewise'
-      context[:gem_version] = '1.29.0'
+      context[:gem_version] = '1.30.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-iotsitewise/client_api.rb

@@ -199,6 +199,7 @@ module Aws::IoTSiteWise
     InterpolationType = Shapes::StringShape.new(name: 'InterpolationType')
     Interval = Shapes::StringShape.new(name: 'Interval')
     IntervalInSeconds = Shapes::IntegerShape.new(name: 'IntervalInSeconds')
+    IntervalWindowInSeconds = Shapes::IntegerShape.new(name: 'IntervalWindowInSeconds')
     InvalidRequestException = Shapes::StructureShape.new(name: 'InvalidRequestException')
     KmsKeyId = Shapes::StringShape.new(name: 'KmsKeyId')
     LimitExceededException = Shapes::StructureShape.new(name: 'LimitExceededException')
@@ -947,6 +948,7 @@ module Aws::IoTSiteWise
     GetInterpolatedAssetPropertyValuesRequest.add_member(:next_token, Shapes::ShapeRef.new(shape: NextToken, location: "querystring", location_name: "nextToken"))
     GetInterpolatedAssetPropertyValuesRequest.add_member(:max_results, Shapes::ShapeRef.new(shape: MaxInterpolatedResults, location: "querystring", location_name: "maxResults"))
     GetInterpolatedAssetPropertyValuesRequest.add_member(:type, Shapes::ShapeRef.new(shape: InterpolationType, required: true, location: "querystring", location_name: "type"))
+    GetInterpolatedAssetPropertyValuesRequest.add_member(:interval_window_in_seconds, Shapes::ShapeRef.new(shape: IntervalWindowInSeconds, location: "querystring", location_name: "intervalWindowInSeconds"))
     GetInterpolatedAssetPropertyValuesRequest.struct_class = Types::GetInterpolatedAssetPropertyValuesRequest
 
     GetInterpolatedAssetPropertyValuesResponse.add_member(:interpolated_asset_property_values, Shapes::ShapeRef.new(shape: InterpolatedAssetPropertyValues, required: true, location_name: "interpolatedAssetPropertyValues"))

data/lib/aws-sdk-iotsitewise/types.rb

@@ -3778,6 +3778,7 @@ module Aws::IoTSiteWise
     #         next_token: "NextToken",
     #         max_results: 1,
     #         type: "InterpolationType", # required
+    #         interval_window_in_seconds: 1,
     #       }
     #
     # @!attribute [rw] asset_id
@@ -3841,9 +3842,48 @@ module Aws::IoTSiteWise
     # @!attribute [rw] type
     #   The interpolation type.
     #
-    #   Valid values: `LINEAR_INTERPOLATION`
+    #   Valid values: `LINEAR_INTERPOLATION | LOCF_INTERPOLATION`
+    #
+    #   For the `LOCF_INTERPOLATION` interpolation, if no data point is
+    #   found for an interval, IoT SiteWise returns the same interpolated
+    #   value calculated for the previous interval and carries forward this
+    #   interpolated value until a new data point is found.
+    #
+    #   For example, you can get the interpolated temperature values for a
+    #   wind turbine every 24 hours over a duration of 7 days. If the
+    #   `LOCF_INTERPOLATION` interpolation starts on July 1, 2021, at 9 AM,
+    #   IoT SiteWise uses the data points from July 1, 2021, at 9 AM to July
+    #   2, 2021, at 9 AM to compute the first interpolated value. If no data
+    #   points is found after 9 A.M. on July 2, 2021, IoT SiteWise uses the
+    #   same interpolated value for the rest of the days.
     #   @return [String]
     #
+    # @!attribute [rw] interval_window_in_seconds
+    #   The query interval for the window in seconds. IoT SiteWise computes
+    #   each interpolated value by using data points from the timestamp of
+    #   each interval minus the window to the timestamp of each interval
+    #   plus the window. If not specified, the window is between the start
+    #   time minus the interval and the end time plus the interval.
+    #
+    #   <note markdown="1"> * If you specify a value for the `intervalWindowInSeconds`
+    #     parameter, the `type` parameter must be `LINEAR_INTERPOLATION`.
+    #
+    #   * If no data point is found during the specified query window, IoT
+    #     SiteWise won't return an interpolated value for the interval.
+    #     This indicates that there's a gap in the ingested data points.
+    #
+    #    </note>
+    #
+    #   For example, you can get the interpolated temperature values for a
+    #   wind turbine every 24 hours over a duration of 7 days. If the
+    #   interpolation starts on July 1, 2021, at 9 AM with a window of 2
+    #   hours, IoT SiteWise uses the data points from 7 AM (9 AM - 2 hours)
+    #   to 11 AM (9 AM + 2 hours) on July 2, 2021 to compute the first
+    #   interpolated value, uses the data points from 7 AM (9 AM - 2 hours)
+    #   to 11 AM (9 AM + 2 hours) on July 3, 2021 to compute the second
+    #   interpolated value, and so on.
+    #   @return [Integer]
+    #
     class GetInterpolatedAssetPropertyValuesRequest < Struct.new(
       :asset_id,
       :property_id,
@@ -3856,7 +3896,8 @@ module Aws::IoTSiteWise
       :interval_in_seconds,
       :next_token,
       :max_results,
-      :type)
+      :type,
+      :interval_window_in_seconds)
       SENSITIVE = []
       include Aws::Structure
     end
@@ -5897,12 +5938,12 @@ module Aws::IoTSiteWise
     #     `interval`, IoT SiteWise aggregates data in one of the following
     #     ways:
     #
-    #     * If you create the metric before or at 6:00 p.m. (UTC), you get
-    #       the first aggregation result at 6 p.m. (UTC) on the day when you
+    #     * If you create the metric before or at 6:00 PM (UTC), you get the
+    #       first aggregation result at 6 PM (UTC) on the day when you
     #       create the metric.
     #
-    #     * If you create the metric after 6:00 p.m. (UTC), you get the
-    #       first aggregation result at 6 p.m. (UTC) the next day.
+    #     * If you create the metric after 6:00 PM (UTC), you get the first
+    #       aggregation result at 6 PM (UTC) the next day.
     #
     #   * The ISO 8601 format.
     #
@@ -5910,19 +5951,19 @@ module Aws::IoTSiteWise
     #     `interval`, IoT SiteWise aggregates data in one of the following
     #     ways:
     #
-    #     * If you create the metric before or at 6:00 p.m. (UTC), you get
-    #       the first aggregation result at 6 p.m. (UTC) on the day when you
+    #     * If you create the metric before or at 6:00 PM (UTC), you get the
+    #       first aggregation result at 6 PM (UTC) on the day when you
     #       create the metric.
     #
-    #     * If you create the metric after 6:00 p.m. (UTC), you get the
-    #       first aggregation result at 6 p.m. (UTC) the next day.
+    #     * If you create the metric after 6:00 PM (UTC), you get the first
+    #       aggregation result at 6 PM (UTC) the next day.
     #
     #   * The 24-hour clock.
     #
     #     For example, if you specify `00:03:00` for `offset` and `5m` for
-    #     `interval`, and you create the metric at 2 p.m. (UTC), you get the
-    #     first aggregation result at 2:03 p.m. (UTC). You get the second
-    #     aggregation result at 2:08 p.m. (UTC).
+    #     `interval`, and you create the metric at 2 PM (UTC), you get the
+    #     first aggregation result at 2:03 PM (UTC). You get the second
+    #     aggregation result at 2:08 PM (UTC).
     #
     #   * The offset time zone.
     #
@@ -5930,12 +5971,12 @@ module Aws::IoTSiteWise
     #     `1d` for `interval`, IoT SiteWise aggregates data in one of the
     #     following ways:
     #
-    #     * If you create the metric before or at 6:00 p.m. (PST), you get
-    #       the first aggregation result at 6 p.m. (PST) on the day when you
+    #     * If you create the metric before or at 6:00 PM (PST), you get the
+    #       first aggregation result at 6 PM (PST) on the day when you
     #       create the metric.
     #
-    #     * If you create the metric after 6:00 p.m. (PST), you get the
-    #       first aggregation result at 6 p.m. (PST) the next day.
+    #     * If you create the metric after 6:00 PM (PST), you get the first
+    #       aggregation result at 6 PM (PST) the next day.
     #   @return [String]
     #
     class TumblingWindow < Struct.new(

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-iotsitewise
 version: !ruby/object:Gem::Version
-  version: 1.29.0
+  version: 1.30.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-08-03 00:00:00.000000000 Z
+date: 2021-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core