indexer DB should not use bytea for mimetype and encoding columns
Closed, MigratedEdits Locked
Actions

Assigned To

Authored By

	ardumont
	Oct 26 2017, 12:37 PM

Description

The content_mimetype table uses bytea for both column encoding and mimetype.
Those should be fairly ascii compatible.

Related Objects
Search...

Status	Assigned	Task
Migrated	gitlab-migration	T439 Indexers: compute (and maintain up-to-date) the filetype of all blobs
Migrated	gitlab-migration	T1385 Monitor output of metadata indexers
Migrated	gitlab-migration	T359 Indexers: batch content analyzer infrastructure
Migrated	gitlab-migration	T1227 General improvments of the indexer: Schedule indexer tasks
Migrated	gitlab-migration	T1374 content indexer: Determine the identifier ranges to use to schedule those
Migrated	gitlab-migration	T818 indexer DB should not use bytea for mimetype and encoding columns

Event Timeline

ardumont created this task.Oct 26 2017, 12:37 PM

zack mentioned this in T817: analyze bogus mimetype values in content_mimetype table.Oct 26 2017, 1:11 PM

zack renamed this task from Indexer mimetype: Use text instead of bytea for mimetype and encoding columns? to indexer DB should not use bytea for mimetype and encoding columns.Sep 28 2018, 10:34 AM

zack updated the task description. (Show Details)

ardumont added a parent task: T1374: content indexer: Determine the identifier ranges to use to schedule those.Nov 27 2018, 11:53 AM

ardumont mentioned this in D714: mimetype: Migrate to indexed data as text.Nov 27 2018, 1:23 PM

ardumont mentioned this in rDCIDX6cbee6588b87: mimetype: Migrate to indexed data as text.Nov 27 2018, 5:49 PM

ardumont closed this task as Resolved.Nov 28 2018, 12:26 PM

ardumont claimed this task.

anlambert mentioned this in rDWAPPS20f880d4097f: common.converters.from_filetype: Reflect type migration in indexer db.Nov 28 2018, 4:27 PM

anlambert mentioned this in R65:20f880d4097f: common.converters.from_filetype: Reflect type migration in indexer db.Feb 23 2019, 1:57 AM