When I first read your post I thought this example had something to do with
"pipe", but now I realize that "::PIPE::" is simply a symbolic
representation of what we software people call a "pipe", namely the
vertical bar character used as a field separator. Usually, terms and tokens
are all of the same type and for a single field, but your use case seems to
be a set of discrete fields that have been mashed into a single field with
"pipe" separators.

My suggestion is that either you fix the problem upstream, so that separate
fields are sent to Solr, or maybe use a Solr update processor to pull the
string apart and store the individual pieces as separate fields.

As always, the first question is not how to store your data, but how your
users intend to access your data. Post some sample queries. I imagine that
any sane user would like to reference individual fields by name.


-- Jack Krupansky

On Fri, Jan 23, 2015 at 11:58 PM, Arumugam, Suresh <suresh.arumu...@emc.com>
wrote:

> Hi All,
>
>
>
> We have indexed the documents to Solr & not able to query using the Regex.
>
>
>
> Our data looks like as below in a Text Field, which is indexed using the
> ClassicTokenizer.
>
>
>
> *                1b ::PIPE:: 04/14/2014 ::PIPE:: 01:32:48 ::PIPE:: BMC
> Power/Reset action  ::PIPE:: Delayed shutdown timer disabled ::PIPE::
> Asserted*
>
>
>
>                 We tried lookup this string with the Regex.
>
> *PIPE*[0-9]{2}\/[0-9}{2}\/[0-9]{4}*Delayed shutdown*Asserted*
>
>
>
>                 Since the analyzer tokenized the data, the regex match is
> happening on the terms & it’s not working as we expect.
>
>
>
> Can you please help us in finding an equivalent way to query this in Solr
> ?
>
>
>
> The following are the details about our environment.
>
>
>
> 1.       Solr 4.10.3 as well as Solr 4.8
>
> 2.       JDK 1.7_51
>
> 3.       SolrConfig.xml & Schema.xml attached.
>
>
>
> The regex query as below is working
>
> msg:/[0-9]{2}/
>
>
>
> But when we want to match more than one terms the regex doesn't seems to
> be working.
>
> Please help us in resolving this issue.
>
>
>
> Thanks in advance.
>
>
>
> Regards,
>
> Suresh.A
>

Reply via email to