Let me see the log lines.
Gert
On 14/08/2013, at 17.04, Alistair Young wrote:
> Having said that, I have to force index via pid to get it to index the
> updated resources.
>
> Renamed all dcterms datastreams namespaces to be same as xslt in the
> objectStore. Rebuilt the resourceIndex and database. Blew away the solr
> index. Index from scratch and it won't index dcterms on the resources that
> had their dcterms renamed. Have to force update on them by pid and then it
> indexes their dcterms.
>
> Any idea why an initial index would fail while an individual index via pid
> would work?
>
> Alistair
>
> -----------------
> mov eax,1
> mov ebx,0
> int 80
>
> From: Alistair Young <[email protected]>
> Reply-To: "Support and info exchange list for Fedora users."
> <[email protected]>
> Date: Wednesday, 14 August 2013 09:53
> To: "Support and info exchange list for Fedora users."
> <[email protected]>
> Subject: Re: [fcrepo-user] gsearch not indexing dcterms on upload
>
> Thanks for that Gert. Finally tracked it down to different representations of
> the same namespace in the repo. Some objects have their dcterms namespace
> declared as per the xslt, others don't. I feel some metadata munging coming
> on. Thanks for confirming the single xslt though. At the end of this hoping
> to produce a tutorial on fedora/gsearch/solr. This seems to be the last thorn
> in the bush.
>
> Cheers,
>
> Alistair
>
>
> From: Gert Schmeltz Pedersen <[email protected]>
> Reply-To: "Support and info exchange list for Fedora users."
> <[email protected]>
> Date: Tuesday, 13 August 2013 20:51
> To: "Support and info exchange list for Fedora users."
> <[email protected]>
> Subject: Re: [fcrepo-user] gsearch not indexing dcterms on upload
>
> No separate xslt, gsearch uses the same indexing xslt, whether triggered by
> an ingest/update of the Fedora object, or by an updateIndex fromPid
> operation, or by an updateIndex fromFoxmlFiles operation. If you get
> different indexing documents in these three cases, then the way to find out
> why, is to compare the log lines in debug mode. I may help, if you send me
> those log lines.
>
> Gert
>
>
> On 13/08/2013, at 18.47, Alistair Young wrote:
>
>> Nup , not that. Even uploading the DCTERMS first it doesn't index them. Is
>> there a separate xslt it uses for updating a resource? The symptoms are
>> identical to when the main xslt was lacking the dcterms namespace.
>>
>> Alistair
>>
>> -------------------
>> Alistair Young
>> Àrd Innleadair air Bathair-bog
>> UHI@Sabhal Mòr Ostaig
>>
>> From: Alistair Young <[email protected]>
>> Reply-To: "Support and info exchange list for Fedora users."
>> <[email protected]>
>> Date: Tuesday, 13 August 2013 16:44
>> To: "Support and info exchange list for Fedora users."
>> <[email protected]>
>> Subject: Re: [fcrepo-user] gsearch not indexing dcterms on upload
>>
>> I think the problem is down to the multi part commit technique being used
>> when uploading to Fedora:
>>
>> 1 – new object pid is generated by a POST
>> 2 – the DC datastream is then PUT
>> 3 - the DCTERMS datastream is then PUT
>> 4 - the content datastream is then POST
>>
>> so I suspect 3 (or 4) is not getting to solr. gsearch indexes on 2 but not
>> on 3 I'm assuming. All the datastreams are present in the foxml files when
>> doing a new index from scratch so they work.
>>
>> Is it possible to turn off auto indexing on upload and instead force it via
>> a REST call to gsearch once the complete resource is uploaded?
>>
>> Alistair
>>
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>>
>> From: Alistair Young <[email protected]>
>> Reply-To: "Support and info exchange list for Fedora users."
>> <[email protected]>
>> Date: Tuesday, 13 August 2013 16:10
>> To: "Support and info exchange list for Fedora users."
>> <[email protected]>
>> Subject: [fcrepo-user] gsearch not indexing dcterms on upload
>>
>> I think I must be missing a file mod or something. Indexing from scratch,
>> using from foxml files works fine and dcterms in all resources are indexed
>> as the namespaces are in the xslt. When uploading a new resource to fedora
>> it gets indexed but only on dc, not dcterms. Does gsearch use a different
>> xslt when indexing from an upload rather than a clean start?
>>
>> Alistair
>>
>> --
>> mov eax,1
>> mov ebx,0
>> int 80h
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
>> Fedora-commons-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk_______________________________________________
> Fedora-commons-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
