Describe the bug
When defining a view with getResourceKey(), the resourcekey has the form: Communication/1000741880/_history/1
To Reproduce
See repro in history_suffix.py from https://github.com/MartinBernstorff/pathling-history-suffix/
Expected behavior
I'm curious about the design choice here, and might simply be lacking context!
When using delta-lake, I would expect that we're merging onto the resourceKey. But that's definitely not the case (see history_suffix_repeat_import.py). Why do you map getResourceKey() to id_versioned instead of id? :-)
Describe the bug
When defining a view with
getResourceKey(), the resourcekey has the form:Communication/1000741880/_history/1To Reproduce
See repro in
history_suffix.pyfrom https://github.com/MartinBernstorff/pathling-history-suffix/Expected behavior
I'm curious about the design choice here, and might simply be lacking context!
When using delta-lake, I would expect that we're merging onto the resourceKey. But that's definitely not the case (see
history_suffix_repeat_import.py). Why do you mapgetResourceKey()toid_versionedinstead ofid? :-)