how it works out for you. Your use-case would benefit
>>>>a
>>>>lot from an improved prefix tree implementation.
>>>>
>>>>I don't gather how a 3rd dimension would play into this. Support for
>>>>multi-dimensional spatial
ply a
>>>> slower index time? Or will I get inaccurate results?
>>>> I have tried it on a very small sample of documents, and it seemed to
>>>> work. I could spend some time this week trying to get a more robust
>>>>(and
>>>> accurate) da
user might want to know what genes overlap a point on a specific
>>> chromosome. Unless I can use 3 dimensional coordinates (which gave an
>>> error when I tried it), I'll need to multiply the coordinates by some
>>> offset for each chromosome to be able to normalise the data (at both
>
gt;>to
>>>think spatially.
>>>
>>>You mentioned that these numeric ranges extend upwards of 10 billion or
>>>so.
>>>Unfortunately, the current "prefix tree" implementation under the hood
>>>for
>>>non-geodetic spatial, the Qua
://wiki.apache.org/solr/SpatialForTimeDurations
>>Using PointType is *not* going to work because your durations are
>>multi-valued per document.
>>
>>It would be useful to create a custom field type that wraps the capability
>>outlined on the wiki to make i
to work because your durations are
>multi-valued per document.
>
>It would be useful to create a custom field type that wraps the capability
>outlined on the wiki to make it easier to use without requiring the user
>to
>think spatially.
>
>You mentioned that these numeric
Like Hoss said, you're going to have to solve this using
http://wiki.apache.org/solr/SpatialForTimeDurations
Using PointType is *not* going to work because your durations are
multi-valued per document.
It would be useful to create a custom field type that wraps the capability
outlined on the
Thank you for the links, they really helped me understand. I see how the
spatial solution works now. I think this could work as a good backup if I
cannot get the custom field type working. The custom field would ideally be a
bit more robust than what I mentioned before, because a region really
}
________
From: Kevin Stone
Sent: Saturday, July 20, 2013 8:24 AM
To: solr-user@lucene.apache.org
Subject: RE: custom field type plugin
Thank you for the links, they really helped me understand. I see how the
spatial solution works now. I think this could
: I can try again this weekend to get a clean environment. However, the
: order I did things in was the reverse of what you suggest. I got the
Hmmm... then i'm kind of at a loss to explain what you're describing.
need to see more details of the configs, dir structure, jar
structure, etc...
From: Chris Hostetter [hossman_luc...@fucit.org]
Sent: Friday, July 19, 2013 3:15 PM
To: solr-user@lucene.apache.org
Subject: Re: custom field type plugin
: a chromosome (or gene, or other object types). All that really boils
: down to is being able to give a number
: a chromosome (or gene, or other object types). All that really boils
: down to is being able to give a number, e.g. 10234, and return documents
: that have regions containing the number. So you'd have a document with a
: list like ["1:16090","400:8000","40123:43564"], and it should come
I have a particular use case that I think might require a custom field type,
however I am having trouble getting the plugin to work.
My use case has to do with genetics data, and we are running into several
situations were we need to be able to query multiple regions of a chromosome
(or gene
: But actually, something like that only works for text field types that
: you can specify an analyzer for. To sort by the integer value, you
: need an integer field.
we should really fix that so any FieldType can have an analyzer and treat
Tokens produced just like multivalued fields are right
On Thu, Mar 5, 2009 at 4:50 AM, Fouad Mardini wrote:
> Thanks for your help, but I am not really sure I follow.
> It is possible to use the PatternTokenizerFactory with pattern = (\d+) and
> group = 0 to tokenize the input correctly
> But I don't see how to use the copyField to achieve sorting
>
Hello Yonik,
Thanks for your help, but I am not really sure I follow.
It is possible to use the PatternTokenizerFactory with pattern = (\d+) and
group = 0 to tokenize the input correctly
But I don't see how to use the copyField to achieve sorting
I read the documentation and this does not seem
On Wed, Mar 4, 2009 at 12:24 PM, Fouad Mardini wrote:
> I have a multivalued field in my schema of type text_ws, values are of the
> form #int #int
> I need to be able to query on the first and sort on the second, this does
> not seem to be enabled out of the box
Can you put the two numbers in se
field type and implement this logic in the getSortField
method
But since the field is multivalued, I need to sort by the value i am
searching for, so i need access to the current query being executed.
Also, i can't seem to figure out the correct -classpath to give to javac for
it to fin
: I wish to index well formed xml documents as they are without escaping
: all the tags with lt;s and gt;s. I searched this mailing list's archive
: and found someone who suggested that you can make a new field type
: having a file something like:
in the thread in question...
http://www.nabble.c
I wish to index well formed xml documents as they are without escaping
all the tags with lt;s and gt;s. I searched this mailing list's archive
and found someone who suggested that you can make a new field type
having a file something like:
import org.apache.solr.schema.TextField;
import org.ap
20 matches
Mail list logo
