Create fields in index required for storing image metadata and code that indexes relevant data.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Create fields & data for image/file data indexing | mediawiki/core | master | +138 -32 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Invalid | None | T101089 [GTWL] Epic: Search for images by colour, size and format | |||
Open | None | T114798 Use TitleInputWidget in the Score inspector for choosing overriding files | |||
Resolved | Smalyshev | T144447 [Story] Expose image meta-data to the SearchEngine | |||
Resolved | Smalyshev | T145561 Reindex all image files to include metadata index fields | |||
Resolved | Smalyshev | T145558 Create search engine mappings and indexing data for images | |||
Resolved | Smalyshev | T145555 Determine which fields will be indexed for image files | |||
Resolved | CKoerner_WMF | T146907 Adding ability to search by metadata: document and announce |
Event Timeline
Change 310472 had a related patch set uploaded (by Smalyshev):
[WIP] Create fields & data for image data
@dcausse I wonder whether we should put limit on file text. Or at least some special options on file text field? It can be huge, e.g. for large PDFs. Is it OK to keep it all and do we need any special options?
I think we already index PDF no?
Basically the only limit we have is the request body size sent to elastic which is limited to 100mb by default, the http request will fail if we try to send 100mb json to elastic.
I don't know if we need to worry here, I've seen lucene able to index pdf with more than 700pages of text...
Maybe we already have a limit on the mysql blob?
Change 310472 merged by jenkins-bot:
Create fields & data for image/file data indexing