May be this wont work, but just a thought...Cant you use
PathHierarchyTokenizerFactory and configure as below?
In this example however we see the oposite configuration, so that a query
for Books/NonFic/Science/Physics would match documents containing
Books/NonFic, Books/NonFic/Science, or Books/No
Separate fields for URL as string and URL as keywords makes sense. You can
also use the URL classifier update processor or a regex filter to have a
third field to match solely the domain name, if that is needed.
-- Jack Krupansky
-Original Message-
From: Furkan KAMACI
Sent: Friday, J
