feat(ingest/snowflake): support for more operation types

[mayurinehate]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[treff7es]

lgtm

[asikowitz]

Saw this just got merged, but a couple question

[asikowitz]

I see that putting CUSTOM allows us to show the customOperationType, but for other sources we try to label these:

(unity)

    QueryStatementType.COPY: OperationTypeClass.INSERT,
    QueryStatementType.UPDATE: OperationTypeClass.UPDATE,
    QueryStatementType.MERGE: OperationTypeClass.UPDATE,
    QueryStatementType.DELETE: OperationTypeClass.DELETE,
    QueryStatementType.TRUNCATE: OperationTypeClass.DELETE,

(bigquery)

    "MERGE": OperationTypeClass.UPDATE,

[mayurinehate]

MERGE is in fact UPDATE and/or DELETE and/or INSERT, so I was hesitant to mark it as UPDATE. CUSTOM operationType is not great to use. cc: @jjoyce0510 . We could add more operation types in model maybe ? I am proposing addition of more operation types to - MERGE, COPY, TRUNCATE respectively. Does that make sense ?

[asikowitz]

Is there harm in passing this if the operation type class is not CUSTOM, for more info? I know we don't do this elsewhere in the code but could start here

[mayurinehate]

hmm, I thought that myself as well. Then customOperationType just behaves more like "nativeOperationType" . cc - @jjoyce0510 - can you confirm this one as well please ?