Details
-
Bug
-
Resolution: Unresolved
-
High
-
None
-
1.13.0
-
None
-
ezp with DFS cluster in dedicated table
Description
It is recommended that you store DFS table in a dedicated database.
However, if you do that, the dfs migration script won't run:
$ php app/console ezplatform:io:migrate-files --from=default,default --to=dfs,nfs --env=prod The command ezplatform:io:migrate-files migrates files from one IO repository to another. It can for example be used to migrate local files from the default IO configuration to a new IO configuration, like a clustered setup. NB: This command is experimental. Use with caution! The --from and --to values must be specified as <metadata_handler>,<binarydata_handler>. If --from is omitted, the default IO configuration will be used. If --to is omitted, the first non-default IO configuration will be used. During the script execution the files should not be modified. To avoid surprises you are advised to create a backup and/or execute a dry run before proceeding with actual update. Since this script can potentially run for a very long time, to avoid memory exhaustion run it in production environment using --env=prod switch. Migrating from 'default,default' to 'dfs,nfs' [Doctrine\DBAL\Exception\TableNotFoundException] An exception occurred while executing 'SELECT filename, mime_type FROM `ezbinaryfile`': SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ezp.ezbinaryfile' doesn't exist [Doctrine\DBAL\Driver\PDOException] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ezp.ezbinaryfile' doesn't exist [PDOException] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'ezp.ezbinaryfile' doesn't exist
So, it seems like it is looking for the ezbinaryfile table in the DFS database, not in the normal ezp database
Attachments
Issue Links
- relates to
-
EZEE-1756 Automatic deployment on TastefulPlanet.com
- Closed