[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-08-05 Thread gerritbot
gerritbot added a comment. Change 294403 merged by jenkins-bot: Cleanup code that has been moved. https://gerrit.wikimedia.org/r/294403TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev, gerritbotCc:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-08-05 Thread gerritbot
gerritbot added a comment. Change 289115 merged by jenkins-bot: Make content handler produce field data https://gerrit.wikimedia.org/r/289115TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev,

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-08-04 Thread gerritbot
gerritbot added a comment. Change 289021 merged by jenkins-bot: Make content handlers assemble content for search https://gerrit.wikimedia.org/r/289021TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-07-27 Thread gerritbot
gerritbot added a comment. Change 288567 merged by jenkins-bot: Use structured fields API to build mapping https://gerrit.wikimedia.org/r/288567TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev,

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-07-08 Thread gerritbot
gerritbot added a comment. Change 294411 abandoned by Smalyshev: Add nested field support https://gerrit.wikimedia.org/r/294411TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev, gerritbotCc:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-07-07 Thread gerritbot
gerritbot added a comment. Change 288559 merged by jenkins-bot: Create API to allow content handlers to handle structured data definitions https://gerrit.wikimedia.org/r/288559TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-06-14 Thread gerritbot
gerritbot added a comment.Change 292490 abandoned by Smalyshev: Add nested field support Reason: oops, somehow duplicated. The right one now is I82a82526e2e254edc1fa7d861d7ac23d9cf07d1c https://gerrit.wikimedia.org/r/292490TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-06-14 Thread gerritbot
gerritbot added a comment.Change 294411 had a related patch set uploaded (by Smalyshev): Add nested field support https://gerrit.wikimedia.org/r/294411TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-06-14 Thread gerritbot
gerritbot added a comment.Change 292490 had a related patch set uploaded (by Smalyshev): Add nested field support https://gerrit.wikimedia.org/r/292490TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-06-14 Thread gerritbot
gerritbot added a comment.Change 294381 had a related patch set uploaded (by Smalyshev): Add search-ignored-headings string, copied from cirrus-search-ignored-headings. https://gerrit.wikimedia.org/r/294381TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-06-14 Thread gerritbot
gerritbot added a comment.Change 294403 had a related patch set uploaded (by Smalyshev): Cleanup code that has been moved. https://gerrit.wikimedia.org/r/294403TASK DETAILhttps://phabricator.wikimedia.org/T89733EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-25 Thread Smalyshev
Smalyshev added a comment. Current implementation slightly modifies the model above, namely: - There is an interface `SearchIndexField` which has `public function getMapping( SearchEngine $engine )`. This is the main way how the search engine mapper gets the concrete mapping. - The

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-16 Thread gerritbot
gerritbot added a comment. Change 288559 had a related patch set uploaded (by Smalyshev): [WIP] [DNM] Create API to allow content handlers to handle structured data definitions https://gerrit.wikimedia.org/r/288559 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-16 Thread gerritbot
gerritbot added a comment. Change 289115 had a related patch set uploaded (by Smalyshev): [WIP] Make content handler produce field data https://gerrit.wikimedia.org/r/289115 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-16 Thread gerritbot
gerritbot added a comment. Change 289021 had a related patch set uploaded (by Smalyshev): [WIP] Make content handlers assemble content for search https://gerrit.wikimedia.org/r/289021 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-12 Thread gerritbot
gerritbot added a comment. Change 288567 had a related patch set uploaded (by Smalyshev): [WIP] Use structured fields API to build mapping https://gerrit.wikimedia.org/r/288567 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-10 Thread dcausse
dcausse added a comment. >> For Wikibase, I am experimenting with unnested fields for multilingual content, though then we have hundreds of unnested fields and not sure there is some point where it's too many? > > Since Elastic says nested field is separate document anyway

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-09 Thread Smalyshev
Smalyshev added a comment. > for multilingual, ElasticSearch supports nested fields (as done with coordinates) but those can be problematic, especially with large nestings. Exactly. I'm not sure hundred-item nested field would do well. What is the use case for multilingual fields? Maybe

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-09 Thread aude
aude added a comment. I think we need generic interfaces, such as FieldDefinitions and Field, and then maybe it's okay to have more specific implementations for specific search engines (e.g. ElasticSearch) for multilingual, ElasticSearch supports nested fields (as done with

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-05-09 Thread Smalyshev
Smalyshev added a comment. I've looked into how we map now in CirrusSearch and we have these broad types: - Date - a match for INDEX_TYPE_DATETIME - Integer - may be a match for INDEX_TYPE_QUANTITY, but I think we need separate types for floats and integers. ElasticSearch has support

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-01-20 Thread Aklapper
Aklapper added a comment. Wikimedia Developer Summit 2016 ended two weeks ago. This task is still open. **If the session in this task took place**, please make sure 1) that the session Etherpad notes are linked from this task, 2) that followup tasks for any actions identified have been created

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-01-05 Thread Deskana
Deskana added a subscriber: Deskana. Deskana added a comment. Etherpad for the session at the Developer Summit: https://etherpad.wikimedia.org/p/WikiDev16-T89733 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T89733: Allow ContentHandler to expose structured data to the search engine.

2016-01-05 Thread Deskana
Deskana added a comment. Paste of my somewhat limited notes: https://etherpad.wikimedia.org/p/WikiDev16-T89733 TASK DETAIL https://phabricator.wikimedia.org/T89733 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel, Deskana Cc: Deskana,