Cparle added a comment.
... and searching now works on testcommons! So - are we good to go?TASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: CparleCc: Ramsey-WMF, EBjune, Smalyshev, Cparle, Jdforrester-WMF,
Jdforrester-WMF added a comment.
Yeah, the cirrusDumpQuery is now the same. Sorry for the confusion!TASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Jdforrester-WMFCc: Ramsey-WMF, EBjune, Smalyshev, Cparle,
Jdforrester-WMF added a comment.
OK, I think I've found the cause of this, which is a config mistake which should be now fixed in production. Will confirm.TASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
Smalyshev added a comment.
Presumably this means that it will occur on real Commons as soon as we switch SDC on, which is a really big problem (as I suspect a manual rebuild there takes a bit longer than a few seconds).
Remembering the Wikidata rollout, here's how we did it:
Make an option to
Smalyshev added a comment.
What's the likelihood of us getting T194968 (or something similar to the solution for T204813) ready by end of January? :)
With the resources and plans we have now - quite unlikely. We could talk about reprioritizing, but even if we'd drop everything (which we can't)
Smalyshev added a comment.
If you enable Wikibase searching (no matter federated or not, I'm not familiar with test-commons setup so tell me if I'm talking nonsense here) then it should have the fields in the index, otherwise you'd get errors.
I have no idea why it considers namespace 0 to be
Cparle added a comment.
These 2 queries are rather different on commons and testcommons. I wonder why?
https://test-commons.wikimedia.org/w/index.php?search==salmonid=Special%3ASearch=Go
https://commons.wikimedia.org/w/index.php?search=salmonid=Special%3ASearch=Go
The testcommons one includes
Jdforrester-WMF added a comment.
In T212138#4861204, @Smalyshev wrote:
I did a reindex and the error is gone. Please see if any other help is needed.
Hmm. This error now occurs on TestCommons, which is configured with captions-only (no Wikibase federation):
Cparle added a comment.
@Jdforrester-WMF afaics that error is something screwy with namespaces on beta
Searching for 'cat' on beta gives me this url https://commons.wikimedia.beta.wmflabs.org/w/index.php?search=cat=Special%3ASearch="">
If you remove ns0=1 then it works without the warning, which
Ramsey-WMF added a comment.
All right. Thanks everyone for the input so far.
So, I have two questions.
a.) I want to confirm that if federation isn't enabled, this isn't a problem. Search worked as expected back when we were only testing captions; are we sure that's still the case so we can
Smalyshev added a comment.
I did a reindex and the error is gone. Please see if any other help is needed.TASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Ramsey-WMF, EBjune, Smalyshev, Cparle,
Smalyshev added a comment.
This is what I am getting in the log:
2019-01-07 23:47:53 [XDPlKawQBHcAAEAR02gAAABS] deployment-mediawiki-07 commonswiki 1.33.0-alpha CirrusSearch WARNING: Search backend error during full_text search for 'duck' after 12: parse_exception: parse_exception: Field
Jdforrester-WMF added a comment.
In T212138#4860903, @Smalyshev wrote:
If you give me access to the instance, I could take a quick look.
This is on Beta Cluster (deployment-prep), so it should show up in the logstash system somewhere (but I can't see it), though you appear to be a project owner
Smalyshev added a comment.
If you give me access to the instance, I could take a quick look.TASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Ramsey-WMF, EBjune, Smalyshev, Cparle,
Smalyshev added a comment.
"An error has occurred while searching" usually means not missing data in index (in that case search would just return nothing, usually) but some kind of error returned by Elastic. I'd check the debug logs - they usually have more information about what exactly Elastic
Cparle added a comment.
Correction - never mind the comment above, eventually the content showed up in the index, so that's not the problemTASK DETAILhttps://phabricator.wikimedia.org/T212138EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: CparleCc: Cparle,
Cparle added a comment.
FYI it looks like data isn't being written to the search index
Captions should be getting written to opening_text. See below - the cirrus data is old
https://commons.wikimedia.beta.wmflabs.org/wiki/File:Photo_on_06-12-2018_at_10.20.jpg
17 matches
Mail list logo
