Open pietercolpaert opened 2 years ago
Agreed that we should have a fallback mechanism.
Looking at the substring bucketizer, in addition to the other pages, the root page will also contain a link to a page (e.g. 0.ttl
) that contains members that could not be bucketized? And if that page (0.ttl
) is full, we create another page 1.ttl
for example. Does root.ttl
then contain a link to 1.ttl
or should it be 0.ttl
?
And what with the subject page bucketizer? Each page is independent of the others, and basically, no relations exist between these pages. So what could be the strategy here?
Current situation:
When the property path doesn’t resolve for a member it throws an error
To-be situation:
When the property path doesn’t resolve, it should use an approach similar to the basic bucketizer for bucketizing all the members that cannot be bucketized by this bucketizer
Test-case: https://github.com/pietercolpaert/coghent-substrings/runs/4107613037?check_suite_focus=true