Last modified: 2012-12-24 19:57:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44416, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42416 - incategory:"xyz" search method for category intersections not unicode compatible
incategory:"xyz" search method for category intersections not unicode compatible
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Categories (Other open bugs)
1.21.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
aklapper-moreinfo
:
Depends on:
Blocks: 41348
  Show dependency treegraph
 
Reported: 2012-11-24 19:27 UTC by Siddhartha Ghai
Modified: 2012-12-24 19:57 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Comment 1 Bawolff (Brian Wolff) 2012-11-24 19:37:39 UTC
I originally assumed this was due to using the translation of the category namespace (under the assumption that lucene has "category" hard coded) but this doesn't seem to work even for categories that use "category" as the namespace name in the link.
Comment 3 MZMcBride 2012-11-25 04:51:51 UTC
(In reply to comment #0)
> The incategory:"xyz" method of finding category intersections doesn't seem to
> work with unicode.
> 
> I tried using the method with one category [1] and two categories [2] on hi-wp,
> but it didn't work. [1] did show three results (but at the time of search the
> category contains 1700+ articles).
> 
> It seems to work at en-wp with both one [3] and multiple categories [4].

I think your test cases are flawed. You seem to have run a bot ("Siddhartha Ghai bot"; cf. <https://hi.wikipedia.org/wiki/%E0%A4%B5%E0%A4%BF%E0%A4%B6%E0%A5%87%E0%A4%B7:%E0%A4%AF%E0%A5%8B%E0%A4%97%E0%A4%A6%E0%A4%BE%E0%A4%A8/Siddhartha_Ghai_bot>) on November 24, 2012 updating a particular category name. On November 24, 2012, you also filed this bug.

The "incategory" feature relies on Lucene search's index of the wikitext of each individual page. This index is updated approximately every 24 hours. You should wait a day or two to see if the problem still persists. My suspicion is that the index simply hasn't updated yet. I'd be surprised if Lucene didn't support Unicode categories (cf. comment 2).

https://hi.wikipedia.org/w/index.php?title=विशेष%3Aखोज&profile=default&search=incategory%3A%22आन्ध्र+प्रदेश%22 seems to work as expected, showing 4,668 results for Category:आन्ध्र प्रदेश.

https://hi.wikipedia.org/w/index.php?search=incategory%3A%22कृष्णा+जिला%22&title=विशेष%3Aखोज similarly correctly shows 955 results for Category:कृष्णा जिला.

The intersection of these categories shows 955 results: <https://hi.wikipedia.org/w/index.php?title=विशेष%3Aखोज&profile=default&search=incategory%3A%22कृष्णा+जिला%22+incategory%3A%22आन्ध्र+प्रदेश%22&fulltext=Search&searchengineselect=mediawiki>.

There seems to be a separate issue where the incategory feature is not always returning results properly. This seems like mis-synchronized search indices. I'll file a separate bug about this.

As far as I can see, this bug is invalid.
Comment 4 MZMcBride 2012-11-25 04:59:09 UTC
(In reply to comment #3)
> There seems to be a separate issue where the incategory feature is not always
> returning results properly. This seems like mis-synchronized search indices.
> I'll file a separate bug about this.

Filed as bug 42423.
Comment 5 Andre Klapper 2012-12-19 16:54:31 UTC
> You should wait a day or two to see if the problem still persists.

Siddhartha: Is this still a problem?
Comment 6 Siddhartha Ghai 2012-12-24 19:57:28 UTC
(In reply to comment #5)
> > You should wait a day or two to see if the problem still persists.
> 
> Siddhartha: Is this still a problem?

Uh, no. Seems like it was my mistake in the first place. Thanks to MZMcBride for pointing it out in Comment 3.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links