#[non_exhaustive]pub struct QueryInput {Show 15 fields
pub index_id: Option<String>,
pub query_text: Option<String>,
pub attribute_filter: Option<AttributeFilter>,
pub facets: Option<Vec<Facet>>,
pub requested_document_attributes: Option<Vec<String>>,
pub query_result_type_filter: Option<QueryResultType>,
pub document_relevance_override_configurations: Option<Vec<DocumentRelevanceConfiguration>>,
pub page_number: Option<i32>,
pub page_size: Option<i32>,
pub sorting_configuration: Option<SortingConfiguration>,
pub sorting_configurations: Option<Vec<SortingConfiguration>>,
pub user_context: Option<UserContext>,
pub visitor_id: Option<String>,
pub spell_correction_configuration: Option<SpellCorrectionConfiguration>,
pub collapse_configuration: Option<CollapseConfiguration>,
}
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.index_id: Option<String>
The identifier of the index for the search.
query_text: Option<String>
The input query text for the search. Amazon Kendra truncates queries at 30 token words, which excludes punctuation and stop words. Truncation still applies if you use Boolean or more advanced, complex queries. For example, Timeoff AND October AND Category:HR
is counted as 3 tokens: timeoff
, october
, hr
. For more information, see Searching with advanced query syntax in the Amazon Kendra Developer Guide.
attribute_filter: Option<AttributeFilter>
Filters search results by document fields/attributes. You can only provide one attribute filter; however, the AndAllFilters
, NotFilter
, and OrAllFilters
parameters contain a list of other filters.
The AttributeFilter
parameter means you can create a set of filtering rules that a document must satisfy to be included in the query results.
For Amazon Kendra Gen AI Enterprise Edition indices use AttributeFilter
to enable document filtering for end users using _email_id
or include public documents (_email_id=null
).
facets: Option<Vec<Facet>>
An array of documents fields/attributes for faceted search. Amazon Kendra returns a count for each field key specified. This helps your users narrow their search.
requested_document_attributes: Option<Vec<String>>
An array of document fields/attributes to include in the response. You can limit the response to include certain document fields. By default, all document attributes are included in the response.
query_result_type_filter: Option<QueryResultType>
Sets the type of query result or response. Only results for the specified type are returned.
document_relevance_override_configurations: Option<Vec<DocumentRelevanceConfiguration>>
Overrides relevance tuning configurations of fields/attributes set at the index level.
If you use this API to override the relevance tuning configured at the index level, but there is no relevance tuning configured at the index level, then Amazon Kendra does not apply any relevance tuning.
If there is relevance tuning configured for fields at the index level, and you use this API to override only some of these fields, then for the fields you did not override, the importance is set to 1.
page_number: Option<i32>
Query results are returned in pages the size of the PageSize
parameter. By default, Amazon Kendra returns the first page of results. Use this parameter to get result pages after the first one.
page_size: Option<i32>
Sets the number of results that are returned in each page of results. The default page size is 10. The maximum number of results returned is 100. If you ask for more than 100 results, only 100 are returned.
sorting_configuration: Option<SortingConfiguration>
Provides information that determines how the results of the query are sorted. You can set the field that Amazon Kendra should sort the results on, and specify whether the results should be sorted in ascending or descending order. In the case of ties in sorting the results, the results are sorted by relevance.
If you don't provide sorting configuration, the results are sorted by the relevance that Amazon Kendra determines for the result.
sorting_configurations: Option<Vec<SortingConfiguration>>
Provides configuration information to determine how the results of a query are sorted.
You can set upto 3 fields that Amazon Kendra should sort the results on, and specify whether the results should be sorted in ascending or descending order. The sort field quota can be increased.
If you don't provide a sorting configuration, the results are sorted by the relevance that Amazon Kendra determines for the result. In the case of ties in sorting the results, the results are sorted by relevance.
user_context: Option<UserContext>
The user context token or user and group information.
visitor_id: Option<String>
Provides an identifier for a specific user. The VisitorId
should be a unique identifier, such as a GUID. Don't use personally identifiable information, such as the user's email address, as the VisitorId
.
spell_correction_configuration: Option<SpellCorrectionConfiguration>
Enables suggested spell corrections for queries.
collapse_configuration: Option<CollapseConfiguration>
Provides configuration to determine how to group results by document attribute value, and how to display them (collapsed or expanded) under a designated primary document for each group.
Implementations§
Source§impl QueryInput
impl QueryInput
Sourcepub fn query_text(&self) -> Option<&str>
pub fn query_text(&self) -> Option<&str>
The input query text for the search. Amazon Kendra truncates queries at 30 token words, which excludes punctuation and stop words. Truncation still applies if you use Boolean or more advanced, complex queries. For example, Timeoff AND October AND Category:HR
is counted as 3 tokens: timeoff
, october
, hr
. For more information, see Searching with advanced query syntax in the Amazon Kendra Developer Guide.
Sourcepub fn attribute_filter(&self) -> Option<&AttributeFilter>
pub fn attribute_filter(&self) -> Option<&AttributeFilter>
Filters search results by document fields/attributes. You can only provide one attribute filter; however, the AndAllFilters
, NotFilter
, and OrAllFilters
parameters contain a list of other filters.
The AttributeFilter
parameter means you can create a set of filtering rules that a document must satisfy to be included in the query results.
For Amazon Kendra Gen AI Enterprise Edition indices use AttributeFilter
to enable document filtering for end users using _email_id
or include public documents (_email_id=null
).
Sourcepub fn facets(&self) -> &[Facet]
pub fn facets(&self) -> &[Facet]
An array of documents fields/attributes for faceted search. Amazon Kendra returns a count for each field key specified. This helps your users narrow their search.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .facets.is_none()
.
Sourcepub fn requested_document_attributes(&self) -> &[String]
pub fn requested_document_attributes(&self) -> &[String]
An array of document fields/attributes to include in the response. You can limit the response to include certain document fields. By default, all document attributes are included in the response.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .requested_document_attributes.is_none()
.
Sourcepub fn query_result_type_filter(&self) -> Option<&QueryResultType>
pub fn query_result_type_filter(&self) -> Option<&QueryResultType>
Sets the type of query result or response. Only results for the specified type are returned.
Sourcepub fn document_relevance_override_configurations(
&self,
) -> &[DocumentRelevanceConfiguration]
pub fn document_relevance_override_configurations( &self, ) -> &[DocumentRelevanceConfiguration]
Overrides relevance tuning configurations of fields/attributes set at the index level.
If you use this API to override the relevance tuning configured at the index level, but there is no relevance tuning configured at the index level, then Amazon Kendra does not apply any relevance tuning.
If there is relevance tuning configured for fields at the index level, and you use this API to override only some of these fields, then for the fields you did not override, the importance is set to 1.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .document_relevance_override_configurations.is_none()
.
Sourcepub fn page_number(&self) -> Option<i32>
pub fn page_number(&self) -> Option<i32>
Query results are returned in pages the size of the PageSize
parameter. By default, Amazon Kendra returns the first page of results. Use this parameter to get result pages after the first one.
Sourcepub fn page_size(&self) -> Option<i32>
pub fn page_size(&self) -> Option<i32>
Sets the number of results that are returned in each page of results. The default page size is 10. The maximum number of results returned is 100. If you ask for more than 100 results, only 100 are returned.
Sourcepub fn sorting_configuration(&self) -> Option<&SortingConfiguration>
pub fn sorting_configuration(&self) -> Option<&SortingConfiguration>
Provides information that determines how the results of the query are sorted. You can set the field that Amazon Kendra should sort the results on, and specify whether the results should be sorted in ascending or descending order. In the case of ties in sorting the results, the results are sorted by relevance.
If you don't provide sorting configuration, the results are sorted by the relevance that Amazon Kendra determines for the result.
Sourcepub fn sorting_configurations(&self) -> &[SortingConfiguration]
pub fn sorting_configurations(&self) -> &[SortingConfiguration]
Provides configuration information to determine how the results of a query are sorted.
You can set upto 3 fields that Amazon Kendra should sort the results on, and specify whether the results should be sorted in ascending or descending order. The sort field quota can be increased.
If you don't provide a sorting configuration, the results are sorted by the relevance that Amazon Kendra determines for the result. In the case of ties in sorting the results, the results are sorted by relevance.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .sorting_configurations.is_none()
.
Sourcepub fn user_context(&self) -> Option<&UserContext>
pub fn user_context(&self) -> Option<&UserContext>
The user context token or user and group information.
Sourcepub fn visitor_id(&self) -> Option<&str>
pub fn visitor_id(&self) -> Option<&str>
Provides an identifier for a specific user. The VisitorId
should be a unique identifier, such as a GUID. Don't use personally identifiable information, such as the user's email address, as the VisitorId
.
Sourcepub fn spell_correction_configuration(
&self,
) -> Option<&SpellCorrectionConfiguration>
pub fn spell_correction_configuration( &self, ) -> Option<&SpellCorrectionConfiguration>
Enables suggested spell corrections for queries.
Sourcepub fn collapse_configuration(&self) -> Option<&CollapseConfiguration>
pub fn collapse_configuration(&self) -> Option<&CollapseConfiguration>
Provides configuration to determine how to group results by document attribute value, and how to display them (collapsed or expanded) under a designated primary document for each group.
Source§impl QueryInput
impl QueryInput
Sourcepub fn builder() -> QueryInputBuilder
pub fn builder() -> QueryInputBuilder
Creates a new builder-style object to manufacture QueryInput
.
Trait Implementations§
Source§impl Clone for QueryInput
impl Clone for QueryInput
Source§fn clone(&self) -> QueryInput
fn clone(&self) -> QueryInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for QueryInput
impl Debug for QueryInput
Source§impl PartialEq for QueryInput
impl PartialEq for QueryInput
impl StructuralPartialEq for QueryInput
Auto Trait Implementations§
impl Freeze for QueryInput
impl RefUnwindSafe for QueryInput
impl Send for QueryInput
impl Sync for QueryInput
impl Unpin for QueryInput
impl UnwindSafe for QueryInput
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);