Undefined array key "type" Db/SchemaBuilder.php on line 93

[fokkejan-made-by-mouses]

Preconditions and environment

• Magento version: 2.4.7-p5
• ElasticSuite version: 2.11.10

Steps to reproduce

1. Install patch 2.4.7-p5 on an instance with ElasticSuite v2.11.10
2. Run bin/magento setup:upgrade

Expected result

The upgrade command can be fully executed.

Actual result

We get this error: Warning: Undefined array key "type" in /var/www/html/vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 93

Additional information

Line 93 in vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php assumes that type exists for a column.
When a column is set to disabled, this is not the case.

ElasticSuite has this line in db_schema.xml:
<column name="is_used_in_autocomplete" disabled="true"/>

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @fokkejan-made-by-mouses. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[hostep]

#39799 was send in earlier today which should give you some more details about the problem.
But that's not a fix for this problem.

[ilnytskyi]

same problem, cannot upgrade to 2.4.7-p5
I'd suggest assigning Severity: S0
@engcom-Bravo

[fokkejan-made-by-mouses]

I also have an error when a table becomes disable via db_scheme.xml.
For example: <table name="akeneo_connector_product_model" disabled="true"/>

Warning: Undefined array key "column" in /var/www/html/vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 89

The workaround at this moment is to create a patch and ignore this array keys.

[NikitaNoaks]

Same issue as well on our project.

vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 89

As a workaround, a patch was implemented to check for the existence of the column key before accessing it, in order to avoid warnings when the key is missing from the table definition.

Replaced:

            foreach ($data['table'] as $keyTable => $tableColumns) {
                foreach ($tableColumns['column'] as $keyColumn => $columnData) {
                    if ($columnData['type'] == 'json') {
                        $tablesWithJsonTypeField[$keyTable] = $keyColumn;
                    }
                }
            }

With:

foreach ($data['table'] as $keyTable => $tableColumns) {
    if (!isset($tableColumns['column']) || !is_array($tableColumns['column'])) {
        continue; // skip tables without columns
    }

    foreach ($tableColumns['column'] as $keyColumn => $columnData) {
        if (isset($columnData['type']) && $columnData['type'] === 'json') {
            $tablesWithJsonTypeField[$keyTable] = $keyColumn;
        }
    }
}

[hostep]

I believe that the second error @fokkejan-made-by-mouses mentioned here will be fixed by this change: 84e57ee

Not sure about the initially reported error. I also think that the line reported of the error happening is wrong and it's happening on line 90 and not 93, right?

[galanis-a]

I had the same issue today with Magento 2.4.7-p5 and ElasticSuite 2.11.10.

I managed to overcome this by upgrading to php 8.3, which upgraded ElasticSuite to 2.11.13, which fixed the issue.

[engcom-Bravo]

Hi @fokkejan-made-by-mouses,

Thanks for your reporting and collaboration.

As I can see this issue got fixed in the scope of the internal Jira ticket ACP2E-3871 by the internal team
Related commits:https://github.com/search?q=repo%3Amagento%2Fmagento2+ACP2E-3871&type=commits

Based on the Jira ticket, the target version is 2.4.9-alpha2.

Thanks