Main Overview Wiki Issues Forum Build Fisheye
Issue Details (XML | Word | Printable)

Key: CMP-577
Type: New Feature New Feature
Status: Open Open
Priority: Minor Minor
Assignee: Shay Banon
Reporter: Ismael Juma
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

Annotations by exception mode

Created: 09/Mar/08 07:54 AM   Updated: 09/Mar/08 10:54 AM
Component/s: Compass::Core
Affects Version/s: 2.0.0 M2
Fix Version/s: None

 Description  « Hide

Until now I have only used Compass to provide search functionality over a model persisted with an ORM in enterprise applications. The current annotations model works very well for that scenario.

A different scenario is a desktop application that would rather use a single store for search and storage where disks are slower and the memory available is more limited. RSSOwl is an example of such scenario, so I was considering replacing db4o and Direct Lucene with Compass.

In this scenario, I would prefer an annotations model that works similarly to the JPA one where simple elements that are not annotated are persisted automatically with decent defaults. This would be an additional mode that would have to be requested by the user, so it would not affect the more common use-case where Compass is used with an ORM.

Does this make sense or are there technical reasons for not doing it?

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Shay Banon added a comment - 09/Mar/08 10:22 AM
Make perfect sense what is suggested here. Something like @Searchble(includeAllByDefault = true")

This complicates the mappings a bit (need to add @SearchableExclude) but a valid request. I will try to get it into 2.0, but not sure... . What do you think?

Ismael Juma added a comment - 09/Mar/08 10:54 AM
Sounds perfect to me.