Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of simone.tripodi@gmail.com
 designates 74.125.82.49 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=RxCB+gSACwRxjZxxK+Jq0RWFwltAEIrmWC6tE3tOVPqyilhtDd5u0aQjp8v1FcTyqZ
         fMYTnnVpOK3UenXRMyIp+5dpU8b+523rHA4JKCayiaaOITABNmDJRwtDglOHeREmcM9D
         IrWZa4i+KXcWswH2ZKRrEhjX6ojKb8MmvsM+c=
MIME-Version: 1.0
Sender: simone.tripodi@gmail.com
In-Reply-To: <AANLkTinNVkYu9qBiE1EZnFT4h_VK8SUbyLhgj9ZHDnPD@mail.gmail.com>
References: <AANLkTi=uBJky1Gy6NWuGFQ_0TAKke3Up+RBwRgLJUVPZ@mail.gmail.com>
	<AANLkTi=CiGwhvgCgX1RjPS5L3BLsFc0uHsWmMYxwxNwH@mail.gmail.com>
	<AANLkTinNVkYu9qBiE1EZnFT4h_VK8SUbyLhgj9ZHDnPD@mail.gmail.com>
Date: Sun, 27 Feb 2011 10:53:18 +0100
Message-ID: <AANLkTi=C_TEJJcvLUURDRZHOJgFv1LjGBDMFQSNgZg4f@mail.gmail.com>
Subject: Re: [digester] How to deal with flexible XML ?
From: Simone Tripodi <simonetripodi@apache.org>
To: Commons Users List <user@commons.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Patrick,
I used Field.Index different values just to show that the Lucene rule
accepts parameters.
Unfortunately your question is more Lucene/domain related, I suggest
you asking on Lucene ML.
HTH, have a nice WE,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/


On Sun, Feb 27, 2011 at 10:39 AM, Patrick Diviacco
<patrick.diviacco@gmail.com> wrote:
> hi,
>
> thanks for the snipper. I see in your code you are
> using Field.Index.NOT_ANALYZED =C2=A0for the title.
>
> It is not clear to me what I should analyze and what not. I need to add
> tf-idf weights to all terms of all fields.
>
> Should I use Field.Index.ANALYZED for all of them ?
>
> thnks
>
>
>
> On 27 February 2011 09:55, Simone Tripodi <simonetripodi@apache.org> wrot=
e:
>
>> Hi Patrick,
>> I quickly had a look at your code and l didn't see anything wrong, the
>> Digester should work either the <geo> tag is empty or not.
>>
>> When you will have documents such
>>
>> <doc>
>> ..
>> <geo></geo>
>> </doc>
>>
>> the `collection/doc/geo/(latitude|longitude)` pattern will never
>> match, so set(Latitude|Longitude) methods won't be invoked.
>> I can suggest you 2 options:
>>
>> =C2=A0* quick solution: when building the Lucene document, check if the
>> latitude/longitude is not null before setting it
>>
>> =C2=A0 =C2=A0if (flickrDoc.getLatitude() !=3D null) {
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0document.add(new Field("latitude", flickrDoc.=
getLatitude(),
>> Field.Store.YES, Field.Index.ANALYZED));
>> =C2=A0 =C2=A0}
>>
>> =C2=A0* a little more complex - but more efficient - solution I wrote fo=
r
>> you and paste on[1], it parses & index the document into Lucene
>> Document in one shot; the LuceneFieldRule is parametrized just in case
>> you need to configure the Lucene Field depending on the matching
>> pattern.
>>
>> HTH,
>> Simo
>>
>> [1] http://pastie.org/1612471
>>
>> http://people.apache.org/~simonetripodi/
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Feb 25, 2011 at 9:21 PM, Patrick Diviacco
>> <patrick.diviacco@gmail.com> wrote:
>> > hi,
>> >
>> > I need to understand how to deal changing xml fields such as these one=
s:
>> >
>> > <doc>
>> > ..
>> > <geo></geo>
>> > </doc>
>> >
>> > <doc>
>> > ..
>> > <geo>
>> > =C2=A0<latitude>2432</latitude>
>> > =C2=A0<longitude>2342</longitude>
>> > </geo>
>> > </doc>
>> >
>> > As you can see geo element can be empty or parent element. I need to
>> > build an apposite parser to deal with it. THis is my current code, but
>> > I get error since latitude not always works...
>> > http://codepad.org/jpKXmGZq
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>> For additional commands, e-mail: user-help@commons.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org