Immutable solution version
Pattern field types for E-Commerce
Complete solution
Shows how to fix pattern field types for E-Commerce. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
[bratseth (member)]: To deploy schemas incrementally without redeploying the whole application, create a new deploy session from the currently active application using the from query parameter, then PUT the new schema and updated services.xml into that session.
Steps
- [bratseth (member)]: To deploy schemas incrementally without redeploying the whole application, create a new deploy session from the currently active application using the from query parameter, then PUT the new schema and updated services.xml into that session. The reporter confirmed it worked.
- Source: https://github.com/vespa-engine/vespa/issues/26104 (Vespa)
When to use
You are seeing this: The reporter confirmed it worked. Source: https://github.com/vespa-engine/vespa/issues/26104 (Vespa) Use this skill when you run into "Pattern field types for E-Commerce".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/vespa-engine/vespa/issues/26104
Evidence
In gh:vespa-engine/vespa#26104, the issue was: Is your feature request related to a problem? Please describe. I considered integrating Vespa to my WooCommerce plugin. But for this use case the schema is not fixed, as the site owner may add fields, change field types, and re-index on-the-fly. By settings or code. For instance, WooCommerce provides several pricing fields, that a WooCommerce site can choose to use as a numerical facet or not. A manual update of the schema file with the use of a CLI command to apply is not a realistic option here.
Describe the solution you'd like A solution would be defining dynamic types.... The verified answer: [bratseth (member)]: To deploy schemas incrementally without redeploying the whole application, create a new deploy session from the currently active application using the from query parameter, then PUT the new schema and updated services.xml into that session. The reporter confirmed it worked.. Issue URL: https://github.com/vespa-engine/vespa/issues/26104
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_nvwmjzdRFLw1TPmRo86sNA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pattern field types for E-Commerce <span>— Vectle</span></a>