Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D1B4AFB1E for ; Fri, 3 May 2013 12:06:06 +0000 (UTC) Received: (qmail 36012 invoked by uid 500); 3 May 2013 11:50:43 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 35592 invoked by uid 500); 3 May 2013 11:50:24 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 35476 invoked by uid 99); 3 May 2013 11:50:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 11:50:18 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nachum234@gmail.com designates 209.85.215.46 as permitted sender) Received: from [209.85.215.46] (HELO mail-la0-f46.google.com) (209.85.215.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 11:50:10 +0000 Received: by mail-la0-f46.google.com with SMTP id fk20so1439560lab.19 for ; Fri, 03 May 2013 04:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=8/QbqqCxH+l0ffdaHzfqwoiglvvFoEG2kYAXl406Lc0=; b=O1nMtVsxwqX6HClFbFMKxYdizt5QCHKQ+10/tFL4hxDw81meBsANtqlTenb2i6owCl 8MFXIqfDF/7z4wT1N+a9VpBgQqWljs9AmRvqFqa1U8Z1AhOsVjVHhGd28EQsxeHKy8eI DCUjGGCWc1Dfqwfb719oRu2NoBhFsQpd1WN9uYEqhlGJR3YvpgRy/SuoYDxWxo97LWVZ QF39ndeQ8kcjC3Smvp7zR5HAq4Px8YFTN8fUMXdS321IKNsg+0mH30wKM4nJqL1HNc0O 21/0VwiEGxlewbNZzgQfCHrBAVLvsrLyB9ll3v/3vtjapBsK/m1slMyIE8oq9OWHHErg YU2w== MIME-Version: 1.0 X-Received: by 10.112.128.135 with SMTP id no7mr4187035lbb.79.1367581790187; Fri, 03 May 2013 04:49:50 -0700 (PDT) Received: by 10.112.34.69 with HTTP; Fri, 3 May 2013 04:49:50 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 May 2013 14:49:50 +0300 Message-ID: Subject: Re: Problem with directories in hebrew and jcifs From: Yossi Nachum To: user@manifoldcf.apache.org Content-Type: multipart/alternative; boundary=047d7b3441fece386904dbcef28d X-Virus-Checked: Checked by ClamAV on apache.org --047d7b3441fece386904dbcef28d Content-Type: text/plain; charset=ISO-8859-1 That is working. I created a path field in my schema and use the "path attribute". I have one problem, I don't see the name of the cifs server, just the path inside it. I try to use "Match Regexp" in the metadata tab with the following values: Match regexp: "(.*)" Replace string: "file:////server_name/$(1)" but it did not work. Still seeing the path only. What am I doing wrong? How can I add my server name to the path? Thanks Yossi On Wed, May 1, 2013 at 4:10 PM, Yossi Nachum wrote: > Thanks I will try that > On May 1, 2013 3:54 PM, "Karl Wright" wrote: > >> There is also a different way to do this entirely - there is a path >> attribute you can send as metadata to Solr. Just include the entire path, >> and put it into a different field that you declare in your schema. See >> "path attribute" in the end-user documentation for the JCIFS connector. >> >> >> >> On Wed, May 1, 2013 at 8:52 AM, Karl Wright wrote: >> >>> IE 6 is extremely old and I believe we developed for IE 7 at a minimum >>> (there were two different versions with different functionality we had to >>> support there), and made further changes for IE 8 when it came out. I have >>> no idea what IE 9 or IE 10 do. >>> >>> The only way to change the encoding of the IRI is to modify the JCIFS >>> connector code. But please bear in mind that unless you can show your >>> modifications will work across a wide variety of browsers, we are unlikely >>> to accept these changes back into the code base. >>> >>> The alternative is, since the encoding IS deterministic and reversible, >>> you could readily write a Tika plugin that would modify at least the URL >>> field in the manner you desire. But you could not modify the ID field >>> since ManifoldCF uses this to delete documents that have disappeared. >>> >>> Karl >>> >>> >>> >>> On Wed, May 1, 2013 at 8:45 AM, Yossi Nachum wrote: >>> >>>> The IRI is not working in my IE. I am using old version of IE V6 SP3. >>>> But what I realy want is to display the correct name of the path with >>>> hebrew characters. >>>> If I understand you right, then I need to change the representation of >>>> the IRI. How can I do that? >>>> On May 1, 2013 3:14 PM, "Karl Wright" wrote: >>>> >>>>> Right, that is exactly what I would expect. >>>>> >>>>> ManifoldCF uses a URL (which is constructed by the connector) as the >>>>> primary key for every document as indexed in the search engine. The URL >>>>> has two purposes: first, it is supposed to be unique, and second, it is >>>>> supposed to allow someone who browses to that result to locate the >>>>> document. In the case of JCIFS, the environment is presumed to be the >>>>> local active directory domain(s), and the "URL" generated is really a file >>>>> IRI, usually of the form "file://///server.domain/path/filename". You thus >>>>> should be able to paste the "URL" of the document from Solr into a browser >>>>> on a machine in the domain, and see the document load. >>>>> >>>>> As I said before, however, there are already certain problems with >>>>> this because each version of IE differs somewhat in how it deals with >>>>> non-ASCII characters. IRI legal character rules are somewhat different >>>>> than URL rules, but IRI's are still nevertheless escaped in various ways. >>>>> There are also multiple equivalent ways of representing the same file path >>>>> with different IRI's. >>>>> >>>>> It is not typical that the ID and URL fields of a document are >>>>> presented to the user in any meaningful way, so your question is usually >>>>> academic in most settings. If you have a problem with the IRI's not >>>>> actually working in a browser, that's of more immediate interest. Please >>>>> let us know if that's the case. >>>>> >>>>> Thanks, >>>>> Karl >>>>> >>>>> >>>>> On Wed, May 1, 2013 at 8:04 AM, Yossi Nachum wrote: >>>>> >>>>>> Thanks for your response >>>>>> I am seeing these characters in solr when I search these files. >>>>>> I am using the solr example site and these characters show up in the >>>>>> ID field and URL field. >>>>>> BTW I am running solr and mcf on a linux server >>>>>> On May 1, 2013 1:11 PM, "Karl Wright" wrote: >>>>>> >>>>>>> Where are you seeing these characters? Are you talking about the >>>>>>> file IRI's that the JCIFS connector generates? Those IRI's are supposed to >>>>>>> be constructed so that your browser would find them if you paste them into >>>>>>> the browser URL window. Unfortunately, there is no good standard, and >>>>>>> people follow IE's behavior, and IE has changed multiple times in how it >>>>>>> deals with non-latin-1 characters. >>>>>>> >>>>>>> Please provide a bit more information so that we can provide a >>>>>>> better answer. >>>>>>> >>>>>>> Karl >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, May 1, 2013 at 3:11 AM, Yossi Nachum wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>> I install search server with solr and manifoldcf. >>>>>>>> I want to index my netapp files over cifs and I have a problem with >>>>>>>> hebrew files and directories. >>>>>>>> When I search for these files in solr I see "%D7%91%D7%..." instead >>>>>>>> of the directory path that contain hebrew characters . >>>>>>>> I try to run the java process with "-Djcifs.encoding=cp1255" but it >>>>>>>> didn't help. >>>>>>>> Can anyone help and tell me how can I index directories/files in >>>>>>>> hebrew? >>>>>>>> >>>>>>>> Thanks >>>>>>>> Yossi >>>>>>>> >>>>>>> >>>>>>> >>>>> >>> >> --047d7b3441fece386904dbcef28d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
That is working. I= created a path field in my schema and use the "path attribute".<= br>
I have one problem, I don't see the name of the cifs server, j= ust the path inside it.
I try to use "Match Regexp" in the metadata tab with the fo= llowing values:
Match regexp: "(.*)"
Replace st= ring: "file:////server_name/$(1)"

but it did not wor= k. Still seeing the path only.

What am I doing wrong? How can I add my server name to the path?<= br>
Thanks
Yossi



On Wed, May 1, 2013 at 4:10 PM, Yossi Na= chum <nachum234@gmail.com> wrote:

Thanks I will try that

On May 1, 2013 3:54 PM, "Karl Wright" = <daddywri@gmail.= com> wrote:
There is also a different way to do this entirely - there = is a path attribute you can send as metadata to Solr.=A0 Just include the e= ntire path, and put it into a different field that you declare in your sche= ma.=A0 See "path attribute" in the end-user documentation for the= JCIFS connector.



On = Wed, May 1, 2013 at 8:52 AM, Karl Wright <daddywri@gmail.com> wrote:
IE 6 is extr= emely old and I believe we developed for IE 7 at a minimum (there were two = different versions with different functionality we had to support there), a= nd made further changes for IE 8 when it came out.=A0 I have no idea what I= E 9 or IE 10 do.

The only way to change the encoding of the IRI is to modify the J= CIFS connector code.=A0 But please bear in mind that unless you can show yo= ur modifications will work across a wide variety of browsers, we are unlike= ly to accept these changes back into the code base.

The alternative is, since the encoding IS deterministic and rever= sible, you could readily write a Tika plugin that would modify at least the= URL field in the manner you desire.=A0 But you could not modify the ID fie= ld since ManifoldCF uses this to delete documents that have disappeared.

Karl

<= br>
On Wed, May 1, 2013 at 8:45 AM, Yossi Nachum = <nachum234@gmail.com> wrote:

The IRI is not working in my IE. I am usi= ng old version of IE V6 SP3.
But what I realy want is to display the correct name of the path with hebre= w characters.
If I understand you right, then I need to change the representation of the = IRI. How can I do that?

On May 1, 2013 3:14 PM, "Karl Wright" = <daddywri@gmail.= com> wrote:
Right, that is exactly what I would expect.
<= br>
ManifoldCF uses a URL (which is constructed by the connector) as t= he primary key for every document as indexed in the search engine.=A0 The U= RL has two purposes: first, it is supposed to be unique, and second, it is = supposed to allow someone who browses to that result to locate the document= .=A0 In the case of JCIFS, the environment is presumed to be the local acti= ve directory domain(s), and the "URL" generated is really a file = IRI, usually of the form "file://///server.domain/path/filename".= =A0 You thus should be able to paste the "URL" of the document fr= om Solr into a browser on a machine in the domain, and see the document loa= d.

As I said before, however, there are already certain problems with this= because each version of IE differs somewhat in how it deals with non-ASCII= characters.=A0 IRI legal character rules are somewhat different than URL r= ules, but IRI's are still nevertheless escaped in various ways.=A0 Ther= e are also multiple equivalent ways of representing the same file path with= different IRI's.

It is not typical that the ID and URL fields of a document are presente= d to the user in any meaningful way, so your question is usually academic i= n most settings.=A0 If you have a problem with the IRI's not actually w= orking in a browser, that's of more immediate interest.=A0 Please let u= s know if that's the case.

Thanks,
Karl

On Wed, May 1, 2013 at 8:04 AM, Yossi Nachum <= span dir=3D"ltr"><nachum234@gmail.com> wrote:

Thanks for your response
I am seeing these characters in solr when I search these files.
I am using the solr example site and these characters show up in the ID fie= ld and URL field.
BTW I am running solr and mcf on a linux server

On May 1, 2013 1:11 PM, "Karl Wright" = <daddywri@gmail.= com> wrote:
Where are you seeing these characters?=A0 Are you tal= king about the file IRI's that the JCIFS connector generates?=A0 Those = IRI's are supposed to be constructed so that your browser would find th= em if you paste them into the browser URL window.=A0 Unfortunately, there i= s no good standard, and people follow IE's behavior, and IE has changed= multiple times in how it deals with non-latin-1 characters.

Please provide a bit more information so that we can provide a be= tter answer.

Karl



On Wed, May 1, 2013 at 3:11 AM, Yossi Nachum <n= achum234@gmail.com> wrote:

Hello,
I install search server with solr and manifoldcf.
I want to index my netapp files over cifs and I have a problem with hebrew = files and directories.
When I search for these files in solr I see "%D7%91%D7%..." inste= ad of the directory path that contain hebrew characters .
I try to run the java process with "-Djcifs.encoding=3Dcp1255" bu= t it didn't help.
Can anyone help and tell me how can I index directories/files in hebrew?

Thanks
Yossi






--047d7b3441fece386904dbcef28d--