#778: Ticket cannot be found if reporter is not an active user
----------------------+--------------------
  Reporter:  hb       |      Owner:
      Type:  defect   |     Status:  closed
  Priority:  major    |  Milestone:
 Component:  search   |    Version:  0.7.0
Resolution:  wontfix  |   Keywords:
----------------------+--------------------

Comment (by hb):

 Explanation of the situation:
 BH 0.7, from an import from Trac
 Trac used to be based on local authentication
 I switched BH to LDAP, where 1 user name got changed

 After some time I detected that the tickets for the user that got renamed
 could not be found via search on their content. Only the tickets of that
 user that were updated since the import could be found. I may have
 incorrectly concluded that this was related to the name change, it may
 also have been just the fact that the ticket was not updated since the
 import, although I did not get alerted on that issue for other users.
 I changed the 'reporter' and 'owner' columns in the ticket table to
 reflect the new user name. (this is what I called 'offending data') (and
 restarted)
 No change.
 I then ran bhsearch rebuild (after some problems, but that is part of a
 known issue)
 I then found that the search from the 'root' ('above' the products) could
 no longer find any wiki article nor ticket, except those articles that got
 updated since the rebuild.
 I also found that when executing the search from the (default, %40)
 product, it did find the wiki pages and tickets.

 As a result, we changed some settings in base.ini: is_default = False and
 enable_redirect = False. (no idea what they are for, just guessing, I am
 unable to find even the slightest useful documentation, I did find loads
 of source code and dead links, but nothing relevant)

 Now BH behaves relatively correctly, as the search from the 'root'
 dashboard now automatically goes to the 'default product' search, I'm
 leaving it like this.

 It is clear to me that there are some bugs around the product handling and
 whoosh, but I'm lacking the time to dive in this more thoroughly. If
 someone investigates this situation, the search environments ('root' or
 'default product') must also be taken into account.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/778#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

Reply via email to