Response from Customer

Upsert/Update Operation in S3/Rules Engine

  • 9 February 2017
  • 1 reply
  • 35 views

Userlevel 3
Badge
Currently we have below limitations in update/upsert operation
1) In S3, we can select only 5 keys as identifiers
2) In Rules, we can select only 3 fields as key identifiers per data type.

To overcome these limitations, we can have MD5 option to generate unique 32 bit character string. MD5 takes fields(should be concatenated as a string) as input and it gives unique 32 bit string. This field can be used in update/upsert operations. There is no limitation of number of fields to be used in MD5. We can select any field with any data type in MD5. Moreover, performance will be good if we use one key while updating table instead of having condition on more than one key.

1 reply

Userlevel 7
Badge +2
Hi Krishna,

 

We have started going through all of the unanswered posts. 

Did you try using the S3 ingest via bionic rules? Is this still an issue?

Reply