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]<mailto:[email protected]>>
Reply-To: "Support and info exchange list for Fedora users."
<[email protected]<mailto:[email protected]>>
Date: Tuesday, 13 August 2013 16:10
To: "Support and info exchange list for Fedora users."
<[email protected]<mailto:[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
