Skip to main content
mmccluregainsightcom
mmccluregainsightcom
Contributor ⭐️⭐️
January 25, 2017

New feature idea for data ingest via S3 connector

  • January 25, 2017
  • 1 reply
  • 56 views
We recently had several suggestions come in with regards to the S3 connector:

1) Duplicate key values should not be loaded into MDA object for S3 Upsert loads - when the records are present in the same file. 
2) Null values should not be allowed for key values used in S3 project. 

I think that the second one in particular would be an excellent feature to help ensure record completion during data uploads. 

      1 reply

      lakshmi_chaitanya
      lakshmi_chaitanya
      Helper ⭐️⭐️⭐️
      January 25, 2017
      Hi Marcus,

      Thanks for the valuable feedback!

      1)Unique Keys: The update keys feature in data management will be enhanced to Unique Keys Feature. Wherein the user can identify a Unique key combination of fields on an MDA object(Which can be a single field or a combination of multiple fields )
      So once the users sets the combination of Unique key values at object level, This will prevent the Duplicate key values to be ingested into the Object

      2) For NULL Values: We are planning to introduce Not NULL constraint check at field level in the object, Where in if the user selects to apply a NOT NULL constraint to a particular field then during ingestion of data 
      a)If a default value is set for the field, That will be ingested
      b)If there is no default value set, And the source field is NULL then that particular row will be rejected(will not be inserted/upserted into the object)
       Thus user can set up the Not Null constraint for the key fields, To avoid null values for key fields

      Both these features are likely to be coming in the spring release, Please reach out for any further information

      Thanks,
      Lakshmi
        Terms & ConditionsAccessibility statement