aws-sdk-iotsitewise 1.29.0 → 1.33.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b15c52a1ccd38347eb2aba9df61642c931974473f8cf1dbb75d4138fcc185b0a
-  data.tar.gz: b9057dc2dcac4f3547cd595937c345789ca85aa23439b6148133056e67398e54
+  metadata.gz: 7b8056c58e0f38489dfe40b408bf503e3c6e1709067ca160896ee8636ca3a9d4
+  data.tar.gz: 63a49d3ec725ae56eba604e2d2a6fb382381bc3a3d9615ff6188fbf3ebd75cb7
 SHA512:
-  metadata.gz: 4e44df64d007dcb9bfa2c0dd6727a11a607201e94a058ee713e4ae438fd7c56eeb7a12f4f9769e513f34aae72687dc7f950609399341118150518e085b3cb27c
-  data.tar.gz: 90c043ed03ff2b66aad3cc968c26c4f8d55e31a6315672664f8ffc8a5385091926a781c21cc3c3327d630631672d4032a26d7a70ed7901df1ef157b4ac045adc
+  metadata.gz: 53dd92fa9904d3c94106f8910ecda9ef9e91cb86f21a0cead9eb2ac2bde4c80bc8734dda948008526da7b11878c0f108abb40b5a680690be7464fbb4450259bc
+  data.tar.gz: 635b63f2263776db518061c96335ea94ee6198eb9bb190b303756b011e00ee844553d7d596e83794319fc537df11cabc52c7a638c4734893f55b8f65ce05926b

data/CHANGELOG.md

@@ -1,6 +1,26 @@
 Unreleased Changes
 ------------------
 
+1.33.0 (2021-10-18)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
+1.32.0 (2021-09-01)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
+1.31.0 (2021-08-23)
+------------------
+
+* Feature - Documentation updates for AWS IoT SiteWise
+
+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.33.0

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

@@ -2456,9 +2456,13 @@ module Aws::IoTSiteWise
     end
 
     # Get interpolated values for an asset property for a specified time
-    # interval, during a period of time. For example, you can use the this
-    # operation to return the interpolated temperature values for a wind
-    # turbine every 24 hours over a duration of 7 days.
+    # interval, during a period of time. If your time series is missing data
+    # points during the specified time interval, you can use interpolation
+    # to estimate the missing data.
+    #
+    # For example, you can use this operation to return the interpolated
+    # temperature values for a wind turbine every 24 hours over a duration
+    # of 7 days.
     #
     # To identify an asset property, you must specify one of the following:
     #
@@ -2522,7 +2526,61 @@ module Aws::IoTSiteWise
     # @option params [required, String] :type
     #   The interpolation type.
     #
-    #   Valid values: `LINEAR_INTERPOLATION`
+    #   Valid values: `LINEAR_INTERPOLATION | LOCF_INTERPOLATION`
+    #
+    #   * `LINEAR_INTERPOLATION` – Estimates missing data using [linear
+    #     interpolation][1].
+    #
+    #     For example, you can use this operation to return 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, IoT
+    #     SiteWise returns the first interpolated value on July 2, 2021, at 9
+    #     AM, the second interpolated value on July 3, 2021, at 9 AM, and so
+    #     on.
+    #
+    #   * `LOCF_INTERPOLATION` – Estimates missing data using last observation
+    #     carried forward interpolation
+    #
+    #     If no data point is found for an interval, IoT SiteWise returns the
+    #     last observed data point for the previous interval and carries
+    #     forward this interpolated value until a new data point is found.
+    #
+    #     For example, you can get the state of an on-off valve every 24 hours
+    #     over a duration of 7 days. If the interpolation starts on July 1,
+    #     2021, at 9 AM, IoT SiteWise returns the last observed data point
+    #     between July 1, 2021, at 9 AM and July 2, 2021, at 9 AM as the first
+    #     interpolated value. If no data point is found after 9 AM on July 2,
+    #     2021, IoT SiteWise uses the same interpolated value for the rest of
+    #     the days.
+    #
+    #
+    #
+    #   [1]: https://en.wikipedia.org/wiki/Linear_interpolation
+    #
+    # @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 +2604,7 @@ module Aws::IoTSiteWise
     #     next_token: "NextToken",
     #     max_results: 1,
     #     type: "InterpolationType", # required
+    #     interval_window_in_seconds: 1,
     #   })
     #
     # @example Response structure
@@ -4056,7 +4115,7 @@ module Aws::IoTSiteWise
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-iotsitewise'
-      context[:gem_version] = '1.29.0'
+      context[:gem_version] = '1.33.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,64 @@ module Aws::IoTSiteWise
     # @!attribute [rw] type
     #   The interpolation type.
     #
-    #   Valid values: `LINEAR_INTERPOLATION`
+    #   Valid values: `LINEAR_INTERPOLATION | LOCF_INTERPOLATION`
+    #
+    #   * `LINEAR_INTERPOLATION` – Estimates missing data using [linear
+    #     interpolation][1].
+    #
+    #     For example, you can use this operation to return 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, IoT SiteWise returns the first interpolated value on July
+    #     2, 2021, at 9 AM, the second interpolated value on July 3, 2021,
+    #     at 9 AM, and so on.
+    #
+    #   * `LOCF_INTERPOLATION` – Estimates missing data using last
+    #     observation carried forward interpolation
+    #
+    #     If no data point is found for an interval, IoT SiteWise returns
+    #     the last observed data point for the previous interval and carries
+    #     forward this interpolated value until a new data point is found.
+    #
+    #     For example, you can get the state of an on-off valve every 24
+    #     hours over a duration of 7 days. If the interpolation starts on
+    #     July 1, 2021, at 9 AM, IoT SiteWise returns the last observed data
+    #     point between July 1, 2021, at 9 AM and July 2, 2021, at 9 AM as
+    #     the first interpolated value. If no data point is found after 9 AM
+    #     on July 2, 2021, IoT SiteWise uses the same interpolated value for
+    #     the rest of the days.
+    #
+    #
+    #
+    #   [1]: https://en.wikipedia.org/wiki/Linear_interpolation
     #   @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 +3912,8 @@ module Aws::IoTSiteWise
       :interval_in_seconds,
       :next_token,
       :max_results,
-      :type)
+      :type,
+      :interval_window_in_seconds)
       SENSITIVE = []
       include Aws::Structure
     end
@@ -5897,12 +5954,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 +5967,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 +5987,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(

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.33.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-iotsitewise
 version: !ruby/object:Gem::Version
-  version: 1.29.0
+  version: 1.33.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-08-03 00:00:00.000000000 Z
+date: 2021-10-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core
@@ -19,7 +19,7 @@ dependencies:
         version: '3'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.119.0
+        version: 3.121.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -29,7 +29,7 @@ dependencies:
         version: '3'
     - - ">="
       - !ruby/object:Gem::Version
-        version: 3.119.0
+        version: 3.121.2
 - !ruby/object:Gem::Dependency
   name: aws-sigv4
   requirement: !ruby/object:Gem::Requirement
@@ -77,7 +77,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: '2.3'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="