Aws lambda Kinesis创建具有相同序列号的多个记录

Aws lambda Kinesis创建具有相同序列号的多个记录,aws-lambda,amazon-kinesis,amazon-kinesis-kpl,Aws Lambda,Amazon Kinesis,Amazon Kinesis Kpl,根据Kinesis文档,序列号应该是唯一的,但是我们看到在多个记录中重复使用相同的值。我们的事件生成器是内部使用KPL的Spring引导应用程序,使用者是AWS lambdas。在测试期间,我们已经执行了几次重新切分。下面您可以看到多次重复使用的样本序列号。这怎么可能呢 "Records": [{ "kinesis": { "kinesisSchemaVersion": "1.0", "partitionKey": "00000000000000002",

根据Kinesis文档,序列号应该是唯一的,但是我们看到在多个记录中重复使用相同的值。我们的事件生成器是内部使用KPL的Spring引导应用程序,使用者是AWS lambdas。在测试期间,我们已经执行了几次重新切分。下面您可以看到多次重复使用的样本序列号。这怎么可能呢

"Records": [{
    "kinesis": {
        "kinesisSchemaVersion": "1.0",
        "partitionKey": "00000000000000002",
        "sequenceNumber": "49596124085897508159438713510240079964989152308217511954",
        "data": "************************",
        "approximateArrivalTimestamp": 1558991793.009
    },
    "eventSource": "aws:kinesis",
    "eventVersion": "1.0",
    "eventID": "shardId-000000000001:49596124085897508159438713510240079964989152308217511954",
    "eventName": "aws:kinesis:record",
    "invokeIdentityArn": "-----------------",
    "awsRegion": "us-east-1",
    "eventSourceARN": "-----------------"
}, {
    "kinesis": {
        "kinesisSchemaVersion": "1.0",
        "partitionKey": "00000000000000003",
        "sequenceNumber": "49596124085897508159438713510240079964989152308217511954",
        "data": ""************************",",
        "approximateArrivalTimestamp": 1558991793.009
    },
    "eventSource": "aws:kinesis",
    "eventVersion": "1.0",
    "eventID": "shardId-000000000001:49596124085897508159438713510240079964989152308217511954",
    "eventName": "aws:kinesis:record",
    "invokeIdentityArn": "-----------------",
    "awsRegion": "us-east-1",
    "eventSourceARN": "-----------------"
}, {
    "kinesis": {
        "kinesisSchemaVersion": "1.0",
        "partitionKey": "00000000000000004",
        "sequenceNumber": "49596124085897508159438713510240079964989152308217511954",
        "data": ""************************",",
        "approximateArrivalTimestamp": 1558991793.009
    },
    "eventSource": "aws:kinesis",
    "eventVersion": "1.0",
    "eventID": "shardId-000000000001:49596124085897508159438713510240079964989152308217511954",
    "eventName": "aws:kinesis:record",
    "invokeIdentityArn": "-----------------",
    "awsRegion": "us-east-1",
    "eventSourceARN": "-----------------"
}]

当Kinesis流编写器将KPL与用户记录聚合一起使用时(请参阅),用户记录将被批处理在一起,并作为单个Kinesis记录交付给常规Kinesis使用者。在这种情况下,运动记录序列号是唯一的,但我们需要实现反聚集

但是,如果为lambda启用了增强的扇出功能,则用户记录将作为单独的运动记录交付(不需要反聚集),并且它们共享相同的序列号

因此,运动记录序列号并不总是唯一的