Github user tony810430 commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3651#discussion_r108848761
  
    --- Diff: docs/dev/connectors/kinesis.md ---
    @@ -121,9 +121,11 @@ one of the following values in the provided 
configuration properties (the naming
     - `LATEST`: read all shards of all streams starting from the latest record.
     - `TRIM_HORIZON`: read all shards of all streams starting from the 
earliest record possible (data may be trimmed by Kinesis depending on the 
retention settings).
     - `AT_TIMESTAMP`: read all shards of all streams starting from a specified 
timestamp. The timestamp must also be specified in the configuration
    -properties by providing a value for 
`ConsumerConfigConstants.STREAM_INITIAL_TIMESTAMP`, either in the date pattern
    -`yyyy-MM-dd'T'HH:mm:ss.SSSXXX` (for example, 
`2016-04-04T19:58:46.480-00:00`), or a non-negative double value representing 
the number of seconds
    -that has elapsed since the Unix epoch (for example, `1459799926.480`).
    +properties by providing a value for 
`ConsumerConfigConstants.STREAM_INITIAL_TIMESTAMP`, in one of the following 
date pattern :
    +    - `yyyy-MM-dd'T'HH:mm:ss.SSSXXX` (for example, 
`2016-04-04T19:58:46.480-00:00`).
    --- End diff --
    
    This format referred to [Kinesis 
API](http://docs.aws.amazon.com/kinesis/latest/APIReference/API_GetShardIterator.html).
 I think it is not bad to use it as default format.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to