Discovery
Upsert/Update Operation in S3/Rules Engine
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) 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.
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.