Increase the wmbs_file_details/lfn column length to 1250

[amaltaro]

Fixes #9366

Status

ready

Description

Given that logArchive LFNs are prefixed by the task name (and its whole chain), we might have files with more than the current 700 chars. Given that the task path has been recently increased to 1250 chars, I'm setting the LFN column to the same length.

Is it backward compatible (if not, which system it affects?)

no (db schema changes)

Related PRs

Somehow related to: #9243

External dependencies / deployment changes

Yes, we need to update the database schema on the agents already deployed. Or deploy the agent from scratch (and using a new RPM).

[cmsdmwmbot]

Jenkins results:

• Unit tests: failed
  • 1 new failures
• Pylint check: succeeded
  • 3 comments to review
• Pycodestyle check: succeeded
  • 7 comments to review
• Python3 compatibility checks: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-WMCore-PR-test/9461/artifact/artifacts/PullRequestReport.html

[amaltaro]

Fix #9367 - Increase the wmbs_file_details/lfn column length to 1250

[amaltaro]

It has been pushed to all the current production agents via:

ALTER TABLE wmbs_file_details MODIFY lfn VARCHAR(1250);
commit;