Support for document-summaries and struct datatypes about pyvespa

[bratseth]

Struct/array/importing

Are you asking about struct, array, or importing either from parents?

• Structs: https://docs.vespa.ai/en/reference/schema-reference.html#struct
• Arrays: Under https://docs.vespa.ai/en/reference/schema-reference.html#field-types

You can import arrays from parent documents just like other field types.
(You cannot refer to an array of parents, but I don't think you are asking about that.)

Document summaries

I assume you mean dynamic summary fields? Yes there is built-in support for that: https://docs.vespa.ai/en/reference/schema-reference.html#summary (see "dynamic").

You might also mean: Is it possible to select the fields to include in a summary, and have multiple such selections you can choose by query. For that, see https://docs.vespa.ai/en/reference/schema-reference.html#document-summary

[danclark382]

For both the struct and the summary, is there a way to implement these in Pyvespa? The links you sent are the correct items I'm mentioning.

I'm trying to use Pyvespa to automate the configuration build of the Vespa application. If there isn't a way to create a struct in Pyvespa (like there is a Field within a schema), is there another automated process for building the configuration besides editing the files within the application directory?

Hope that clarifies the question a bit.

[bratseth]

Yes, that makes it clear. @thigm85 can answer best about Pyvespa, but it is not a design goal of it to be functionally complete for defining production applications, it only provides what's necessary for data science.

You need to have a source of truth which specifies what the schema and application package should contain. I don't see why that should be in some other format than the native one provided by Vespa.

[danclark382]

That makes sense…thanks for the clarification!

…

On Tue, Jul 12, 2022 at 12:38 AM Jon Bratseth ***@***.***> wrote: Yes, that makes it clear. @thigm85 <https://github.com/thigm85> can answer best about Pyvespa, but it is *not* a design goal of it to be functionally complete for defining production applications, it only provides what's necessary for data science. You need to have a source of truth which specifies what the schema and application package should contain. I don't see why that should be in some other format than the native one provided by Vespa. — Reply to this email directly, view it on GitHub <#362 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJDCOAORUE3VZM7ACAUTAPDVTUOGTANCNFSM527BXLEQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>