Open tyrasd opened 3 years ago
Some initial comments:
Solution 1 has the downside that it only works for "well behaved" regexes which don't match too many tags: it would be problematic when used with unspecific filters like .osmTag("name", Pattern.compile("^[a-z]"))
as the amount of tags this translates to could be enormous.
Solution 2 can also optionally have an optimized path which uses solution 1 in cases where it is known that the regex does not produce too many results. But IMHO that would be low priority, because in such cases end users can already choose to use to use an "expanded" non-regex variant of their query.
There's already some functionality in the OSHDB to filter by OSM tags using regular expressions. But the current implementation does not work on distributed backends (Ignite) because of the non-serializable nature of connections to the keytables database.
I see two possible ways to go forward: