Apache OpenOffice (AOO) Bugzilla – Issue 32135
users@de.openoffice.org not searchable at all
Last modified: 2006-12-13 12:53:12 UTC
This is not about search not bringing *all* expected results! This is about search being disabled for the list. Goto http://de.openoffice.org/servlets/SearchList?listName=users The text below the search-box reads "No search specified" Now enter some search-term and run the search. Now the text reads: "Text search not available for this list" (and it doesn't get any results) However, all ather lists are searchable (including the cvs@de.openoffice.org and issues@de.openoffice.org mailing lists).
I confirmed this. routing to support. thanks louis
Filed an internal issue PCN 30446 for the engineers to look at. -Priya
PB-DEF: The problem is looked into by engineering currently. Updating the whiteboard with the current PCN.
Do we have an update on this? A few days ago, a user gave the "hint" to browse *all* the mails via web interface and the search per browsers text-search. I'd expect, this would cause real heavy load to retrieve 25k mailheaders via web. I explained, how to search the mails via advanced search, but this is not so obvious to ne users.
This is in the engineering queue. There were some activities regarding this issue internally. I will update the ticket as soon as I get some feedback.
Closing this one as duplicate of Issue 28708. *** This issue has been marked as a duplicate of 28708 ***
This is not a duplicate of issue 32135. issue 32135 is about search not returning all results. This issue is about no search possible *at all* (it is disabled) ->reopen issue.
(s/32135/28708/g - it is not a duplicate of 28708 of course)
Objection noted. Checked internally for updates. Should have something by early next week. Updating keywords accordingly.
The internal issue has been reviewed by engineering to scope out an estimate. It is in the queue along with other SUN issues.
again a month passed without an update. :-( When can we expect a fix?
Further research indicate that this might not be a duplicate of Issue 32135, but the root cause for both these issues are the same. Engineering is right now working on this with the Openoffice data set.
Some typos from cloph and myself here. What I meant was that this issue is closely related with Issue 28708. In that issue I mentioned that the indexer is looked into engineering currently and they are working on it right now.
So it was not a duplicate. The index-run had completed but still the text-search is disabled. I still think that it is only a wrongly set configuration bit like "enable_search=1" instead of "enable_search=true" or something.
Yes. I could replicate it now. Discussing about this to the engineers internally will update as and when we get the update from them. Priya
Adding the PCN number 30446 which is tracking this issue.
Same like issue 28708 we need to schedule another task to fix the indexer issue as the indexer on production box will be down. Please let us know a suitable time.
German lang doesn't care when it will be. We want this fixed even if this means that the site would be unavailable for three days. (You get the idea...) And I still think that issue 28708 and this one are not the same cause. This one: * No search possible at all, the site still tells you that the search is "not available" The other issue: * Search only gives some results and misses some messages. Running the indexer probably won't help if this is the only action taken. We get: "Text search not available for this list" whereas one would get "No matches found" when there are no messages indexed. But anyway: Stefan, Louis, please choose any time that fits for the whole site. The sooner the better.
Could you please let us know whether the indexer has impact on mail delivery? If not feel free to go ahead at weekends. Please inform us about the end of the indexer downtime and the expected timeframe the indexer will need to catch up.
hello support, would you be able to get back to us on this issue this week? thanks Louis
Again a whole month passed without *any* response. The issue has been filed almost a year ago. It is high-priority for us. If you don't want to fix it, then mark as wontfix.
hi support... could you take a peek at this? thanks louis
As per PCN 6156, this will be fixed once we upgrade the customer to Danube-S as we no longer use native indexes for search starting Mississippi. So this can be verified the upgrade Danube.
@sripriya: It is not clear to me how native indexing is relevant to this issue. This issue is not about display problems with special characaters or a couple of messages missing from the index. It is about the whole search being disabled. Other lists of german-lang project are indexed successfully and can be searched without problems. On these lists the same people write with the same clients and with the same set of characters. Please state clearly that [ ] The message "Text search not available for this list" is *NOT* a sign of a configuration problem [ ] The cause of this problem is ....
Hello Support, please have devel answer this: Please state clearly that [ ] The message "Text search not available for this list" is *NOT* a sign of a configuration problem [ ] The cause of this problem is .... What have native-Indexes to do with this issue?
Again a month without response: Here again the question: Hello Support, please have devel answer this: Please state clearly that [ ] The message "Text search not available for this list" is *NOT* a sign of a configuration problem [ ] The cause of this problem is .... What have native-Indexes to do with this issue?
Hi I'm raising the priority on this to p2 and requesting that support provide periodic feedback on the resolution of this issue. thanks louis
The cause of this problem is due to incostenices/corruption of the native indexes for this mailing list used on CEE for this version. This can be manually fixed by engineering but the effort is quite substantial. (For clarification, native indexes are indexes specific to mailing list search). When Openoffice upgrades to Danube-S (the next version to which Openoffice is scheduled to be upgraded) this will no longer be an issue, since from 3.x onwards, domain wide indexes are used (no longer local mailing list indexes are used). We did verify that that The message "Text search not available for this list" is *NOT* a sign of a configuration problem. Normally, (as you correctly pointed out)if the indexing for that list has been turned off then this would appear. However we checked with the database and noticed that the 'indexed' has been column set to 1 and so its enabled. The error will also disappear when upgraded to Danube-S.
there are two options, then, support. Resolve with "wontfix" "wontfix" means that for one reason or another the problem won't be fixed. or Resolve with "later." "later" means that a subsequent release fixes the problem. Both alert us to the fact that the problem for now will not be fixed. Thanks Louis
Basically any of the following would be OK for us: * delete the old, corrupted index and regenerate it. Move any messages that cause trouble when indexing out of the way (e.g. to a seperate list "broken-messages") * create a new mailing-list, transfer (bounce) the messages to the new list, delete the old one, create it again, transfer the messages back and index the restored list. * provide the messages & search on a different machine, on a different host,.. * dump the old, corrupted index and start indexing the messages from now on * give access to the mbox-files (or whatever is used) so we can set-up our own archive (giving us access probably is not possible at all - but anyway...) If any action requires to take the list off-list, don't hesitate to do so. Any time between 22:00 and 04:00 UTC should not be a problem at all. (but please send a short announce message). Waiting until the next update of SourceCast/CEE is not an option (as nobody knows when this will happen).
I forgot: Thank you for the answer (esp. for explaining what "native indexes" are in this context)
Guess what? Another month without *any* response. What is so hard about writing an answer? louis, st, mh - can you try to push this one please?
Engineering resource was busy with the Danube-S release. Checking to see if resources are available to start this task now.
hi I'll see about raising awareness of this. Again. thanks louis
*Again* a whole month without any response or action. Is it really *that* hard to get one of the dev-people to have a look at this issue for 5 or 10 minutes to evaluate? If it is, then just write: "Yes, our mail-system & webfrontend just sucks and will keep sucking" and close this issue as wontfix. It is pointless in delaying this issues every month and waiting until the monthly request for response arrives and then delay the issue again, and so on. If search results in the new release are presented in the same as in the current release & when the mailing-list-browsing will work the same as in the current release, then the webarchive is not really usable anyway.
Marking this as RESOLVED->LATER. The indexer issue will be fixed in Danube. Openoffice is due for upgrade in the next few months.
there's hope, finally ... works in OOo staging site, see http://de.stage.openoffice.org/servlets/SearchList?list=users&searchText=hilfe&defaultField=subject&Search=Search
Did a small test of searching for a very common word called "test" in the list and found that i did receive about 45 search results . Please verify and close this issue .
the list is searchable, but the presentation of the results still is just as useless as with the old site. But anyway → closing.