You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Lanke,Aniruddha" <An...@Cerner.com> on 2014/10/08 07:39:06 UTC
eDisMax parser and special characters
We are using a eDisMax parser in our configuration. When we search using the query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
Search term: red yellow
Will give back result ‘red - yellow’
How does eDisMax treat special characters?
What tweaks do we need to do, so when a user enters a ‘-‘ in the query e.g. red - yellow, we
get the appropriate result back?
Thanks,
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: eDisMax parser and special characters
Posted by "Lanke,Aniruddha" <An...@Cerner.com>.
Thanks for a quick response Jack.
Trying to escape it with a backslash, we also need to escape the whitespace. Is that a default behavior while escaping special characters?
eg:
Search query: pcta \- all
No results returned
<str name="parsedquery_toString">+(((name_starts_with:pcta^9.0 | name_parts_starts_with:pcta^6.0 | s_detail:pcta | name:pcta^12.0 | s_detail_starts_with:pcta^3.0 | s_detail_parts_starts_with:pcta^2.0) (name_starts_with:-^9.0 | s_detail_starts_with:-^3.0) (name_starts_with:all^9.0 | name_parts_starts_with:all^6.0 | s_detail:all | name:all^12.0 | s_detail_starts_with:all^3.0 | s_detail_parts_starts_with:all^2.0))~3)</str>
Search query: pcta\ \- all
Results returned
<str name="parsedquery_toString">+(((((name_starts_with:pcta name_starts_with:-)~2^9.0) | name_parts_starts_with:pcta^6.0 | s_detail:pcta | name:pcta^12.0 | ((s_detail_starts_with:pcta s_detail_starts_with:-)~2^3.0) | s_detail_parts_starts_with:pcta^2.0) (name_starts_with:all^9.0 | name_parts_starts_with:all^6.0 | s_detail:all | name:all^12.0 | s_detail_starts_with:all^3.0 | s_detail_parts_starts_with:all^2.0))~2)</str>
Search query: pcta \-\ all
Results returned
<str name="parsedquery_toString">+(((name_starts_with:pcta^9.0 | name_parts_starts_with:pcta^6.0 | s_detail:pcta | name:pcta^12.0 | s_detail_starts_with:pcta^3.0 | s_detail_parts_starts_with:pcta^2.0) (((name_starts_with:- name_starts_with:all)~2^9.0) | name_parts_starts_with:all^6.0 | s_detail:all | name:all^12.0 | ((s_detail_starts_with:- s_detail_starts_with:all)~2^3.0) | s_detail_parts_starts_with:all^2.0))~2)</str>
On Oct 13, 2014, at 10:08 AM, Jack Krupansky <ja...@basetechnology.com>> wrote:
Simply escape it with a backslash or enclose the term in quotes.
Sure, it would be nice to be able to configure various operators to be disabled, but that's not fesible with query parser designed around static grammars and infleexible tools such as JFlex.
-- Jack Krupansky
-----Original Message----- From: Lanke,Aniruddha
Sent: Monday, October 13, 2014 11:03 AM
To: solr-user@lucene.apache.org<ma...@lucene.apache.org>
Subject: Re: eDisMax parser and special characters
Can the default behavior of "-" as a pre-fix operator be changed so it can be searched as a string?
Thanks,
On Oct 9, 2014, at 8:34 AM, Lanke,Aniruddha <An...@Cerner.com>> wrote:
Is there a way to override this default behavior?
— Lanke
On Oct 8, 2014, at 4:55 PM, Jack Krupansky <ja...@basetechnology.com>> wrote:
Hyphen is a "prefix operator" and is normally followed by a term to indicate that the term "must not" be present. So, your query has a syntax error. The two query parsers differ in how they handle various errors. In the case of edismax, it quotes operators and then tries again, so the hyphen gets quoted, and then analyzed to nothing for text fields but is still a string for string fields.
-- Jack Krupansky
-----Original Message----- From: Lanke,Aniruddha
Sent: Wednesday, October 8, 2014 4:38 PM
To: solr-user@lucene.apache.org<ma...@lucene.apache.org>
Subject: Re: eDisMax parser and special characters
Sorry for a delayed reply here is more information -
Schema that we are using - http://pastebin.com/WQAJCCph
Request Handler in config - http://pastebin.com/Y0kP40WF
Some analysis -
Search term: red -
Parser eDismax
No results show up
<str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) DisjunctionMaxQuery((name_starts_with:-^9.0 | s_detail_starts_with:-^3.0)))~2))/no_coord</str>
Search term: red -
Parser dismax
Results are returned
<str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) ())/no_coord</str>
Why do we see the variation in the results between dismax and eDismax?
On Oct 8, 2014, at 8:59 AM, Erick Erickson <er...@gmail.com>> wrote:
There's not much information here.
What's the doc look like?
What is the analyzer chain for it?
What is the output when you add &debug=query?
Details matter. A lot ;)
Best,
Erick
On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner <mi...@newsrx.com>> wrote:
Try escaping special chars with a "\"
On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
We are using a eDisMax parser in our configuration. When we search using
the query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: eDisMax parser and special characters
Posted by Jack Krupansky <ja...@basetechnology.com>.
Simply escape it with a backslash or enclose the term in quotes.
Sure, it would be nice to be able to configure various operators to be
disabled, but that's not fesible with query parser designed around static
grammars and infleexible tools such as JFlex.
-- Jack Krupansky
-----Original Message-----
From: Lanke,Aniruddha
Sent: Monday, October 13, 2014 11:03 AM
To: solr-user@lucene.apache.org
Subject: Re: eDisMax parser and special characters
Can the default behavior of "-" as a pre-fix operator be changed so it can
be searched as a string?
Thanks,
On Oct 9, 2014, at 8:34 AM, Lanke,Aniruddha <An...@Cerner.com>
wrote:
> Is there a way to override this default behavior?
>
> — Lanke
>
> On Oct 8, 2014, at 4:55 PM, Jack Krupansky <ja...@basetechnology.com>
> wrote:
>
>> Hyphen is a "prefix operator" and is normally followed by a term to
>> indicate that the term "must not" be present. So, your query has a syntax
>> error. The two query parsers differ in how they handle various errors. In
>> the case of edismax, it quotes operators and then tries again, so the
>> hyphen gets quoted, and then analyzed to nothing for text fields but is
>> still a string for string fields.
>>
>> -- Jack Krupansky
>>
>> -----Original Message----- From: Lanke,Aniruddha
>> Sent: Wednesday, October 8, 2014 4:38 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: eDisMax parser and special characters
>>
>> Sorry for a delayed reply here is more information -
>>
>> Schema that we are using - http://pastebin.com/WQAJCCph
>> Request Handler in config - http://pastebin.com/Y0kP40WF
>>
>> Some analysis -
>>
>> Search term: red -
>> Parser eDismax
>> No results show up
>> <str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0
>> | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 |
>> s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0))
>> DisjunctionMaxQuery((name_starts_with:-^9.0 |
>> s_detail_starts_with:-^3.0)))~2))/no_coord</str>
>>
>> Search term: red -
>> Parser dismax
>> Results are returned
>> <str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 |
>> name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 |
>> s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0))
>> ())/no_coord</str>
>>
>> Why do we see the variation in the results between dismax and eDismax?
>>
>>
>> On Oct 8, 2014, at 8:59 AM, Erick Erickson
>> <er...@gmail.com>> wrote:
>>
>> There's not much information here.
>> What's the doc look like?
>> What is the analyzer chain for it?
>> What is the output when you add &debug=query?
>>
>> Details matter. A lot ;)
>>
>> Best,
>> Erick
>>
>> On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner
>> <mi...@newsrx.com>> wrote:
>> Try escaping special chars with a "\"
>>
>>
>> On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
>>
>> We are using a eDisMax parser in our configuration. When we search using
>> the query term that has a ‘-‘ we don’t get any results back.
>>
>> Search term: red - yellow
>> This doesn’t return any data back but
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE This message and any included attachments are from
>> Cerner Corporation and are intended only for the addressee. The
>> information contained in this message is confidential and may constitute
>> inside or non-public information under international, federal, or state
>> securities laws. Unauthorized forwarding, printing, copying,
>> distribution, or use of such information is strictly prohibited and may
>> be unlawful. If you are not the addressee, please promptly delete this
>> message and notify the sender of the delivery error by e-mail or you may
>> call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1)
>> (816)221-1024.
>
Re: eDisMax parser and special characters
Posted by "Lanke,Aniruddha" <An...@Cerner.com>.
Can the default behavior of "-" as a pre-fix operator be changed so it can be searched as a string?
Thanks,
On Oct 9, 2014, at 8:34 AM, Lanke,Aniruddha <An...@Cerner.com> wrote:
> Is there a way to override this default behavior?
>
> — Lanke
>
> On Oct 8, 2014, at 4:55 PM, Jack Krupansky <ja...@basetechnology.com> wrote:
>
>> Hyphen is a "prefix operator" and is normally followed by a term to indicate that the term "must not" be present. So, your query has a syntax error. The two query parsers differ in how they handle various errors. In the case of edismax, it quotes operators and then tries again, so the hyphen gets quoted, and then analyzed to nothing for text fields but is still a string for string fields.
>>
>> -- Jack Krupansky
>>
>> -----Original Message----- From: Lanke,Aniruddha
>> Sent: Wednesday, October 8, 2014 4:38 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: eDisMax parser and special characters
>>
>> Sorry for a delayed reply here is more information -
>>
>> Schema that we are using - http://pastebin.com/WQAJCCph
>> Request Handler in config - http://pastebin.com/Y0kP40WF
>>
>> Some analysis -
>>
>> Search term: red -
>> Parser eDismax
>> No results show up
>> <str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) DisjunctionMaxQuery((name_starts_with:-^9.0 | s_detail_starts_with:-^3.0)))~2))/no_coord</str>
>>
>> Search term: red -
>> Parser dismax
>> Results are returned
>> <str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) ())/no_coord</str>
>>
>> Why do we see the variation in the results between dismax and eDismax?
>>
>>
>> On Oct 8, 2014, at 8:59 AM, Erick Erickson <er...@gmail.com>> wrote:
>>
>> There's not much information here.
>> What's the doc look like?
>> What is the analyzer chain for it?
>> What is the output when you add &debug=query?
>>
>> Details matter. A lot ;)
>>
>> Best,
>> Erick
>>
>> On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner <mi...@newsrx.com>> wrote:
>> Try escaping special chars with a "\"
>>
>>
>> On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
>>
>> We are using a eDisMax parser in our configuration. When we search using
>> the query term that has a ‘-‘ we don’t get any results back.
>>
>> Search term: red - yellow
>> This doesn’t return any data back but
>>
>>
>>
>>
>> CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>
Re: eDisMax parser and special characters
Posted by "Lanke,Aniruddha" <An...@Cerner.com>.
Is there a way to override this default behavior?
— Lanke
On Oct 8, 2014, at 4:55 PM, Jack Krupansky <ja...@basetechnology.com> wrote:
> Hyphen is a "prefix operator" and is normally followed by a term to indicate that the term "must not" be present. So, your query has a syntax error. The two query parsers differ in how they handle various errors. In the case of edismax, it quotes operators and then tries again, so the hyphen gets quoted, and then analyzed to nothing for text fields but is still a string for string fields.
>
> -- Jack Krupansky
>
> -----Original Message----- From: Lanke,Aniruddha
> Sent: Wednesday, October 8, 2014 4:38 PM
> To: solr-user@lucene.apache.org
> Subject: Re: eDisMax parser and special characters
>
> Sorry for a delayed reply here is more information -
>
> Schema that we are using - http://pastebin.com/WQAJCCph
> Request Handler in config - http://pastebin.com/Y0kP40WF
>
> Some analysis -
>
> Search term: red -
> Parser eDismax
> No results show up
> <str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) DisjunctionMaxQuery((name_starts_with:-^9.0 | s_detail_starts_with:-^3.0)))~2))/no_coord</str>
>
> Search term: red -
> Parser dismax
> Results are returned
> <str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) ())/no_coord</str>
>
> Why do we see the variation in the results between dismax and eDismax?
>
>
> On Oct 8, 2014, at 8:59 AM, Erick Erickson <er...@gmail.com>> wrote:
>
> There's not much information here.
> What's the doc look like?
> What is the analyzer chain for it?
> What is the output when you add &debug=query?
>
> Details matter. A lot ;)
>
> Best,
> Erick
>
> On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner <mi...@newsrx.com>> wrote:
> Try escaping special chars with a "\"
>
>
> On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
>
> We are using a eDisMax parser in our configuration. When we search using
> the query term that has a ‘-‘ we don’t get any results back.
>
> Search term: red - yellow
> This doesn’t return any data back but
>
>
>
>
> CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: eDisMax parser and special characters
Posted by Jack Krupansky <ja...@basetechnology.com>.
Hyphen is a "prefix operator" and is normally followed by a term to indicate
that the term "must not" be present. So, your query has a syntax error. The
two query parsers differ in how they handle various errors. In the case of
edismax, it quotes operators and then tries again, so the hyphen gets
quoted, and then analyzed to nothing for text fields but is still a string
for string fields.
-- Jack Krupansky
-----Original Message-----
From: Lanke,Aniruddha
Sent: Wednesday, October 8, 2014 4:38 PM
To: solr-user@lucene.apache.org
Subject: Re: eDisMax parser and special characters
Sorry for a delayed reply here is more information -
Schema that we are using - http://pastebin.com/WQAJCCph
Request Handler in config - http://pastebin.com/Y0kP40WF
Some analysis -
Search term: red -
Parser eDismax
No results show up
<str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0 |
name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 |
s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0))
DisjunctionMaxQuery((name_starts_with:-^9.0 |
s_detail_starts_with:-^3.0)))~2))/no_coord</str>
Search term: red -
Parser dismax
Results are returned
<str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 |
name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 |
s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0))
())/no_coord</str>
Why do we see the variation in the results between dismax and eDismax?
On Oct 8, 2014, at 8:59 AM, Erick Erickson
<er...@gmail.com>> wrote:
There's not much information here.
What's the doc look like?
What is the analyzer chain for it?
What is the output when you add &debug=query?
Details matter. A lot ;)
Best,
Erick
On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner
<mi...@newsrx.com>> wrote:
Try escaping special chars with a "\"
On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
We are using a eDisMax parser in our configuration. When we search using
the query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
CONFIDENTIALITY NOTICE This message and any included attachments are from
Cerner Corporation and are intended only for the addressee. The information
contained in this message is confidential and may constitute inside or
non-public information under international, federal, or state securities
laws. Unauthorized forwarding, printing, copying, distribution, or use of
such information is strictly prohibited and may be unlawful. If you are not
the addressee, please promptly delete this message and notify the sender of
the delivery error by e-mail or you may call Cerner's corporate offices in
Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: eDisMax parser and special characters
Posted by "Lanke,Aniruddha" <An...@Cerner.com>.
Sorry for a delayed reply here is more information -
Schema that we are using - http://pastebin.com/WQAJCCph
Request Handler in config - http://pastebin.com/Y0kP40WF
Some analysis -
Search term: red -
Parser eDismax
No results show up
<str name="parsedquery">(+((DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) DisjunctionMaxQuery((name_starts_with:-^9.0 | s_detail_starts_with:-^3.0)))~2))/no_coord</str>
Search term: red -
Parser dismax
Results are returned
<str name="parsedquery">(+DisjunctionMaxQuery((name_starts_with:red^9.0 | name_parts_starts_with:red^6.0 | s_detail:red | name:red^12.0 | s_detail_starts_with:red^3.0 | s_detail_parts_starts_with:red^2.0)) ())/no_coord</str>
Why do we see the variation in the results between dismax and eDismax?
On Oct 8, 2014, at 8:59 AM, Erick Erickson <er...@gmail.com>> wrote:
There's not much information here.
What's the doc look like?
What is the analyzer chain for it?
What is the output when you add &debug=query?
Details matter. A lot ;)
Best,
Erick
On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner <mi...@newsrx.com>> wrote:
Try escaping special chars with a "\"
On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
We are using a eDisMax parser in our configuration. When we search using
the query term that has a ‘-‘ we don’t get any results back.
Search term: red - yellow
This doesn’t return any data back but
CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: eDisMax parser and special characters
Posted by Erick Erickson <er...@gmail.com>.
There's not much information here.
What's the doc look like?
What is the analyzer chain for it?
What is the output when you add &debug=query?
Details matter. A lot ;)
Best,
Erick
On Wed, Oct 8, 2014 at 6:26 AM, Michael Joyner <mi...@newsrx.com> wrote:
> Try escaping special chars with a "\"
>
>
> On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
>>
>> We are using a eDisMax parser in our configuration. When we search using
>> the query term that has a ‘-‘ we don’t get any results back.
>>
>> Search term: red - yellow
>> This doesn’t return any data back but
>>
>>
>
Re: eDisMax parser and special characters
Posted by Michael Joyner <mi...@newsrx.com>.
Try escaping special chars with a "\"
On 10/08/2014 01:39 AM, Lanke,Aniruddha wrote:
> We are using a eDisMax parser in our configuration. When we search using the query term that has a ‘-‘ we don’t get any results back.
>
> Search term: red - yellow
> This doesn’t return any data back but
>
>
Re: eDisMax parser and special characters
Posted by Aman Tandon <am...@gmail.com>.
Hi,
It seems me like there is difference in tokens generated during query and
indexing time, you can tell us the your field type and the analyzers you
are using to index that field.
With Regards
Aman Tandon
On Wed, Oct 8, 2014 at 11:09 AM, Lanke,Aniruddha <Aniruddha.Lanke@cerner.com
> wrote:
> We are using a eDisMax parser in our configuration. When we search using
> the query term that has a ‘-‘ we don’t get any results back.
>
> Search term: red - yellow
> This doesn’t return any data back but
>
> Search term: red yellow
> Will give back result ‘red - yellow’
>
> How does eDisMax treat special characters?
> What tweaks do we need to do, so when a user enters a ‘-‘ in the query
> e.g. red - yellow, we
> get the appropriate result back?
>
> Thanks,
>
> CONFIDENTIALITY NOTICE This message and any included attachments are from
> Cerner Corporation and are intended only for the addressee. The information
> contained in this message is confidential and may constitute inside or
> non-public information under international, federal, or state securities
> laws. Unauthorized forwarding, printing, copying, distribution, or use of
> such information is strictly prohibited and may be unlawful. If you are not
> the addressee, please promptly delete this message and notify the sender of
> the delivery error by e-mail or you may call Cerner's corporate offices in
> Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
>