Sounds good. Thank you for the synonym (definitely will work on this) and
padding suggestions.
- Todd
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-Regex-Searching-with-Decimal-Fields-tp4206015p4206421.html
Sent from the Solr - User mailing list archive at Nabble
Then it seems like you can just index the raw strings as a string
field and suggest with that but fire the actual query against the
numeric type.
Best,
Erick
On Tue, May 19, 2015 at 3:25 PM, Todd Long wrote:
> Erick Erickson wrote
>> But I _really_ have to go back to one of my original quest
Erick Erickson wrote
> But I _really_ have to go back to one of my original questions: What's
> the use-case?
The use-case is with autocompleting fields. The user might know a frequency
starts with 2 so we want to limit those results (e.g. 2, 23, 214, etc.). We
would still index/store the numeric-
No cleaner ways that spring to mind. Although you might get some
mileage out of normalizing
_everything_ rather than indexing different forms. Perhaps all numbers
are stored left-padded
with zeros to 16 places to the left of the decimal point and
right-padded 16 places to the right
of the decimal p
I see what you're saying and that should do the trick. I could index 123 with
an index synonym 123.0. Then my regex query "/123/" should hit along with a
boolean query "123.0 OR 123.00*". Is there a cleaner approach to breaking
apart the boolean query in this case? Right now, outside of Solr, I'm j
I really have in mind an index-time filter, not necessarily a
query-time Filter. So at index time you have something like 123.4000.
You index synonyms 123.4 and 123 (or whatever) and now your _queries_
should "just work" since the forms you need are in the index already
and whether it's a regex or
Erick Erickson wrote
> No, not using SynonymFilterFactory. Rather take that as a base for a
> custom Filter that
> doesn't use any input file.
OK, I just wanted to make sure I wasn't missing something that could be done
with the SynonymFilterFactory itself. At one time, I started going down this
p
No, not using SynonymFilterFactory. Rather take that as a base for a
custom Filter that
doesn't use any input file. Rather it would normalize any numeric
tokens and inject
as many variants on the spot as you desire.
Best,
Erick
On Mon, May 18, 2015 at 9:56 AM, Todd Long wrote:
> Essentially, we
Essentially, we have a grid of data (i.e. frequencies, baud rates, data
rates, etc.) and we allow wildcard filtering on the various columns. As the
user provides input, in a specific column, we simply filter the overall data
by an implicit "starts with" query (i.e. 23 becomes 23*). In most cases,
y
This feels like an XY problem. Either you're working with numbers or
you're not. It's hard for me to imagine what purpose is served by a
query on numerical data that would match 2.5, 20.5, 299.5,
299.5 etc, much less regexes. That may just be my limited
imagination however.
You could s
Maybe you should first disclose the nature of the business problem you are
trying to solve.
To be clear, patterns and wildcards are string processing operations, not
numeric operations. Usually one searches for ranges of numeric values. So,
again, what operation are you really trying to perform th
11 matches
Mail list logo
