[
http://issues.ops4j.org/browse/QI-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11709#action_11709
]
Niclas Hedhman commented on QI-127:
-----------------------------------
I have now added the "nice to have", of checking the result type and properties
for Queryable.
> Make possible to mark an Entity as not indexable
> ------------------------------------------------
>
> Key: QI-127
> URL: http://issues.ops4j.org/browse/QI-127
> Project: Qi4j
> Issue Type: New Feature
> Components: API, Core Runtime, Indexing, Query
> Affects Versions: 0.1, 0.2, 0.3
> Reporter: Alin Dreghiciu
> Assignee: Niclas Hedhman
> Priority: Minor
> Fix For: 0.5
>
>
> The current situation is that entities are always indexed by default. But
> there are use cases when an entity should not be indexed. One such a case are
> configuration entities which by indexing will trigger a recursive process as
> described in:
> " Basically, a change will trigger the indexing, which will attempt to
> load/create the config for the indexing, which will use the EntityStore,
> which will trigger the indexing, and then this loops until OutOfMemory."
> Solution is to make possible to mark entities as not indexable via
> annotations e.g. @Queryable(false).
> Further on this annotation could be applied to the type meaning that the
> entities of this type are not indexable or on a member property/assoc meaning
> that only that specific prop/annotation is not indexed.
> By default (@Queryable or annotation not present) the entities will be
> indexed.
> A nice to have is that query api should not allow filtering of entities
> marked as not indexable (runtime exception while building the where clause)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
