find-tables: Default value of 1 makes sense for --score-cutoff option #678
Labels
good first issue
Good issue for new DVT contributors
priority: p2
Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup)
type: docs
From
find-tables
tool documentation (https://github.com/GoogleCloudPlatform/professional-services-data-validator#building-matched-table-lists):"
Note that our score cutoff default is a 0.8, which was manually tested to be an accurate value. If no matches occur, reduce this value.
"
I believe the expectation from most end users would for table name matching to be case-insensitive but precise regarding the alphanumeric values used.
I think it would make more sense to --score-cutoff default to 1 and let customers reduce the value if they require non-exact matching.
This is low priority.
The text was updated successfully, but these errors were encountered: