Ticket #1089 (closed clarification: wontfix)

Opened 3 years ago

Last modified 3 years ago

search migration results in many WARNs in mulgara log about insert failures

Reported by: russ Assigned to: ronald
Priority: low Milestone: 0.9.2
Component: ambra Version: 0.9.1_rc1
Keywords: migration Cc:
Blocking: Blocked By:

Description

on our migration of the plos staging server the following select inserts were run: 

2009-01-29 19:27:17,777 INFO  SearchMigrator()> Performing insert select of 
ClassMetadata[name=Category, type=[]]

2009-01-30 05:41:40,130 INFO  SearchMigrator()> Performing insert select of 
ClassMetadata[name=ObjectInfo, type=[http://rdf.topazproject.org/RDF/ObjectInfo]]

2009-01-30 05:43:36,150 INFO  SearchMigrator()> Performing insert select of 
ClassMetadata[name=UserProfile, type=[http://xmlns.com/foaf/0.1/Person]]

2009-01-30 05:52:06,620 INFO  SearchMigrator()> Performing insert select of 
ClassMetadata[name=Aggregation, type=[http://purl.org/dc/dcmitype/Collection]

2009-01-30 05:52:07,352 INFO  SearchMigrator()> Performing insert select of 
ClassMetadata[name=Citation, type=[http://purl.org/net/nknouf/ns/bibtex#Entry]]

we started getting warnings in mulgara.log after the second: 

2009-01-30 05:44:33,676 WARN  LuceneResolver> Unable to add 
{info:doi/10.1371/profile/0747c169-78d6-4369-9114-cfe5ffc0aad3, 
http://rdf.topazproject.org/RDF/bio, } to full text string index [RMI TCP 
Connection(1635)-192.168.66.15 org.mulgara.resolver.lucene.LuceneResolver]

all in all, we got 3,201 such warnings, and they continued until after the last select-insert was run. so i think that most of the select inserts are failing

Dependency Graph

Change History

(follow-up: ↓ 3 ) 02/12/09 16:32:14 changed by rich

  • owner changed from rich to ronald.
  • type changed from defect to clarification.

Are these warnings something to worry about?

02/12/09 16:32:20 changed by rich

  • priority changed from unassigned to low.

(in reply to: ↑ 1 ; follow-up: ↓ 4 ) 02/12/09 16:57:40 changed by ronald

Replying to rich:

Are these warnings something to worry about?

No, they can be safely ignored. If you look closely at what it's failing to add, you'll notice that the third element of the triple is empty, i.e. an empty string is being inserted into the search graph and because it is pointless to attempt to index an empty string the insert is skipped and a warning is logged.

We could possibly add a check for this in OTM.

(in reply to: ↑ 3 ) 02/12/09 17:01:28 changed by ronald

  • status changed from new to closed.
  • resolution set to wontfix.

Replying to ronald:

We could possibly add a check for this in OTM.

Oh, sorry, this is the migrator: in that case forget it (it would be way too expensive to add this check, and the migrator is single-use code, i.e. will probably be removed in the next version anyway).