Search broken?

[bdcheung]

When I click my username and select "Find more posts by bdcheung", none of my recent posts show up. Similarly, if I go to my profile and click "Find all posts by bdcheung" OR "Find all threads started by bdcheung", none of the recent posts/threads show up. In fact, nothing after 1/29/08 appears in the search results.

[bdcheung]

and newly created threads aren't showing up when you search for their titles. It seems like this thing only indexes once a week.

[KevinSours]

There was a problem with search indexing that was recently resolved. We should now be indexing posts every minute.
Kevin

[vrkelley]

Also when you search within a thread, it shows deleted posts.

When I click my username and select "Find more posts by bdcheung", none of my recent posts show up. Similarly, if I go to my profile and click "Find all posts by bdcheung" OR "Find all threads started by bdcheung", none of the recent posts/threads show up. In fact, nothing after 1/29/08 appears in the search results.

[KevinSours]

can you PM me with an example?
Thanks.
Kevin

[meeshu]

I'm trying to search "Cadence Cycles", with the search option set for showing results by post date.

I tried this search twice a few hours ago, and I received an error message each time (error message below).

Just tried this search again, and again I got the error message!

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.RuntimeException: field "posttime" does not appear to be indexed
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:488)
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:441)
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

root cause

java.lang.RuntimeException: field "posttime" does not appear to be indexed
org.apache.lucene.search.FieldCacheImpl$11.createValue(FieldCacheImpl.java:465)
org.apache.lucene.search.FieldCacheImpl.get(FieldCacheImpl.java:72)
org.apache.lucene.search.FieldCacheImpl.getAuto(FieldCacheImpl.java:424)
org.apache.lucene.search.FieldSortedHitQueue.comparatorAuto(FieldSortedHitQueue.java:338)
org.apache.lucene.search.FieldSortedHitQueue$1.createValue(FieldSortedHitQueue.java:172)
org.apache.lucene.search.FieldCacheImpl.get(FieldCacheImpl.java:72)
org.apache.lucene.search.FieldSortedHitQueue.getCachedComparator(FieldSortedHitQueue.java:155)
org.apache.lucene.search.FieldSortedHitQueue.<init>(FieldSortedHitQueue.java:56)
org.apache.lucene.search.TopFieldDocCollector.<init>(TopFieldDocCollector.java:41)
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:122)
org.apache.lucene.search.Hits.getMoreDocs(Hits.java:74)
org.apache.lucene.search.Hits.<init>(Hits.java:61)
org.apache.lucene.search.Searcher.search(Searcher.java:55)
com.internetbrands.ibsearch.service.LuceneIndexService.search(LuceneIndexService.java:662)
com.internetbrands.ibsearch.data.vBulletinSearch.search(vBulletinSearch.java:467)
com.internetbrands.ibsearch.web.EmbeddedSearchController.onSubmit(EmbeddedSearchController.java:59)
org.springframework.web.servlet.mvc.SimpleFormController.onSubmit(SimpleFormController.java:381)
org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController. java:267)
org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormControl ler.java:265)
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:48)
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:874)
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:808)
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:476)
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:441)
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

note The full stack trace of the root cause is available in the Apache Tomcat/6.0.14 logs.
Apache Tomcat/6.0.14

Note that I tried using the quote marks as well, as I wanted the exact phrase to be searched.

What's wrong with the search feature?

[KevinSours]

I don't know, but I'll forward this to our search developer. It looks like its working at the moment.
Kevin

[meeshu]

Thanks!

But, I got the same, or similar, error message again when I searched a minute ago for "Cadence Cycles" (qoute marks included)!?

[donnamb]

Kevin, I tried it and am receiving the same message.

[meeshu]

I believe the number of search results per page is up to 25(?)

A recent search returned 99 pages.

First page displayed 25 results. But second and subsequent pages only displayed 12 results per page, despite the top of the search frame indicating multiples of 25 results per page!?

So there appears to be a discrepancy on the number of results per page to be displayed.

What's wrong?

[East Hill]

What's wrong?

"Beta".

It's nowhere near being perfect :p .

East Hill

[BillK]

I reported the same issue last Sunday (see link below). According to Tom Stormcrowe, the problem is being worked.

Link Here (http://www.bikeforums.net/showthread.php?t=379127&page=2)

[Tom Stormcrowe]

Yeah, the search engine is still in a beta release, so it's a bit buggy. :(

[meeshu]

Thanks folks!

Sorry I missed the earlier post.

My understanding is that the "new" search engine is an upgrade over the old. The reason(s) for the upgrade is unknown. But I would have thought that any upgrade should have been tested first (off line) before being implemented? It appears that this search engine is being tested on line instead. Consequently, the new search engine 'bugs' are causing frustrations, with posts here reflecting those frustrations. :mad:

Another search last night resulted in 9 pages. And each page was displayed correctly at 25 results per page! :) So, we're making progess!?

[cuda2k]

Thanks folks!

Sorry I missed the earlier post.

My understanding is that the "new" search engine is an upgrade over the old. The reason(s) for the upgrade is unknown. But I would have thought that any upgrade should have been tested first (off line) before being implemented? It appears that this search engine is being tested on line instead. Consequently, the new search engine 'bugs' are causing frustrations, with posts here reflecting those frustrations. :mad:

Another search last night resulted in 9 pages. And each page was displayed correctly at 25 results per page! :) So, we're making progess!?

The old search had a lot of problems including:

1) Being very very slow
2) Was causing the website to crash completely!
3) The index table was being corrupted frequently causing the search to become useless for weeks at a time.

Basically the forum outgrew the design limitations of the old search engine. The decision was between trying to fix the old search (again) and see how long it took to break again. Or go with this new search that we knew wasn't perfect yet, but was still running much smoother than the current setup. There's been a few hicups along the way with the new one, but its still better than what we had before. Which fairly often was no search at all.

[bdcheung]

Hate to bring up the thread, but searching for posts by user is still buggy.

Parameters:
- "User Name:" = "bdcheung"
- "Find posts by user"
- "Sort results by post date"
- "Show results as: Posts"
- "Search in all open forums"

Results in showing all threads started by bdcheung, sorted by post date.

But when I click on a username (while browsing a thread) and select "Find more posts by XXXXX", then the results show all posts by the user. Weiirrrddd.

[donrhummy]

There no longer seems to be a way to find all posts by a user, say "donrhummy" for example, and sort them by which have most recently been responded to.