Questions about matchType options and CSV field definitions order in schema setup

Brandon M. · 2024-04-16T20:03:27.890Z

Two questions for you lovely folks: 1. what happens if you do matchType:"EXACT,FUZZY"? 2. Do field definitions array have to be in order of columns of the CSV? I know schema does.

Brandon M.

·Apr 16, 2024 08:03 PM

Two questions for you lovely folks:

1.
what happens if you do matchType:"EXACT,FUZZY"?
2.
Do field definitions array have to be in order of columns of the CSV? I know schema does.

4 comments

· Sorted by Oldest

Sonal G.
·
Exact and fuzzy are kind of contradicting so you wouldn’t want to do that. With each match type, Zingg builds features and multiple match types means multiples of those features. The schema does have to match the field order. Haven’t tried with field defs. Give it a try and let us know
Brandon M.
·
Sometimes the output csv's from zingg have wrong data in wrong fields
Brandon M.
·
and can't figure out why if it's a quoting issue or a config issue.
Sonal G.
·
If your csv is quoted, you can specify that as part of the pipe definition

Sonal G.
·
Exact and fuzzy are kind of contradicting so you wouldn’t want to do that. With each match type, Zingg builds features and multiple match types means multiples of those features. The schema does have to match the field order. Haven’t tried with field defs. Give it a try and let us know
Brandon M.
·
Sometimes the output csv's from zingg have wrong data in wrong fields
Brandon M.
·
and can't figure out why if it's a quoting issue or a config issue.
Sonal G.
·
If your csv is quoted, you can specify that as part of the pipe definition