Interface FieldIndexer
- All Known Subinterfaces:
CustomFieldIndexer
- All Known Implementing Classes:
AffectedVersionsIndexer,AssigneeIndexer,AttachmentIndexer,BaseCustomFieldIndexer,BaseLabelsIndexer,CascadingSelectCustomFieldIndexer,CascadingSelectCustomFieldIndexer.CascadingSelectChildCustomFieldIndexer,ComponentsIndexer,CreatedDateIndexer,CreatorIndexer,CurrentEstimateIndexer,CustomFieldIndexerWithStats,CustomFieldLabelsIndexer,DateCustomFieldIndexer,DescriptionIndexer,DueDateIndexer,EnvironmentIndexer,ExactTextCustomFieldIndexer,FeatureFlagGuardedCustomFieldIndexer,FeatureFlagGuardedFieldIndexer,FieldIndexerWithStats,FixForVersionsIndexer,GroupCustomFieldIndexer,IssueIdIndexer,IssueKeyIndexer,IssueLinkIndexer,IssueTypeIndexer,LabelsCustomFieldIndexer,LabelsIndexer,LocalDateIndexer,MultiGroupCustomFieldIndexer,MultiUserCustomFieldIndexer,NumberCustomFieldIndexer,OriginalEstimateIndexer,ParentIssueIndexer,PriorityIndexer,ProgressIndexer,ProjectCustomFieldIndexer,ProjectIdIndexer,ReporterIndexer,ResolutionDateIndexer,ResolutionIndexer,SecurityIndexer,SelectCustomFieldIndexer,SlowFieldIndexer,SortableTextCustomFieldIndexer,StatusIndexer,SubTaskIndexer,SummaryIndexer,TimeSpentIndexer,UpdatedDateIndexer,UserCustomFieldIndexer,VersionCustomFieldIndexer,VisibilityBaseFieldIndexer,VoterIndexer,VotesIndexer,WatcherIndexer,WatchesIndexer,WorkRatioIndexer
FieldValue that is relevant for a Jira
field.
The portion that is added to the collector will be the indexed value that is represented by the value contained
in the Issue object when the indexFields(FieldValueCollector, Issue, CustomFieldPrefetchedData)
method is called.
There is a strong relationship between a FieldIndexer and a ClauseQueryMapper
as the indexer declares index fields and the query factory assumes it knows
how to generate a query that will find relevant issues based on the values that were indexed.
If you are writing a CustomFieldSearcher then the glue that binds the FieldIndexer and the ClauseQueryFactory
together is the CustomFieldSearcher since it provides both
the ClauseHandler and the FieldIndexer. Keep in mind that if you are creating one of these that the Indexer
must declare fields that the ClauseQueryFactory knows how to search.
This replaces the deprecated FieldIndexer, which is Lucene specific.
- Since:
- 10.4
-
Field Summary
Fields -
Method Summary
Modifier and TypeMethodDescriptionDeclares the fields to be added to the index schemagetId()voidindexFields(FieldValueCollector collector, Issue issue, CustomFieldPrefetchedData prefetchedData) This method allows an indexer the opportunity to add values to the provided collector that are relevant for searching and storage of the portion of the issue that the FieldIndexer handles.booleanisFieldVisibleAndInScope(Issue issue) This method is used to determine if the indexer is relevant for the provided issue.default booleanUsed to declare how the indexer handles nulls.
-
Field Details
-
NO_VALUE_INDEX_VALUE
General empty token- See Also:
-
-
Method Details
-
getId
String getId()- Returns:
- the String representation of the field id that this indexer is indexing, this must be unique for each independent FieldIndexer. If the Indexer does not represent a System or Custom field in Jira this should still return a unique string that describes the indexer.
-
getFields
Collection<Field> getFields()Declares the fields to be added to the index schema -
indexFields
void indexFields(FieldValueCollector collector, Issue issue, CustomFieldPrefetchedData prefetchedData) This method allows an indexer the opportunity to add values to the provided collector that are relevant for searching and storage of the portion of the issue that the FieldIndexer handles.If, for example, the indexer handles indexing an issues summary then this indexer will add a field value to the collector that represents the stored and searchable summary of the issue.
Note that trying to index very large (i.e. larger than ~32 kB) fields as
KeywordFieldwill result in them being removed to prevent the indexing operation from crashing. This is a limitation of how OpenSearch and Lucene store terms.- Parameters:
collector- the collector for collecting indexed valuesissue- the issue that contains the data that will be indexed and which can be used to determine the project/issue type context that will allow you to determine if we should add the value as searchable or unsearchable.prefetchedData- if the custom field type implementedCustomFieldType.getNonNullCustomFieldProvider()this reference will hold the matching value returned fromNonNullCustomFieldProvider.getCustomFieldInfo(List <Issue>)
-
isFieldVisibleAndInScope
This method is used to determine if the indexer is relevant for the provided issue. This method must check the fields visibility, in relation to the field configuration scheme, must check any global flags that would enable or disable a field (such as enable votes flag), and must check, if the field is a custom field, if the custom field is relevant for this issue.All these checks should take into account the
IssueContextas defined by the passed in issue.The result of this method is used to determine the correct values that should be returned when performing an empty search.
- Parameters:
issue- that is having a document created from.- Returns:
- if true then this field is relevant for the issue, otherwise it is not.
-
skipsIndexingNull
@ExperimentalApi default boolean skipsIndexingNull()Used to declare how the indexer handles nulls.- Returns:
- true if the indexer doesn't do anything when the field value is null
-