Alright, interesting. Maybe you can share your experience later and propose
something that can be integrated in sculptor. If you need we can probably
assist you with customization of generation.
/Patrik
Wojtek Wasik wrote:
>
> @Patrik
> Compass has a problem with locking/unlocking index files w
@Patrik
Compass has a problem with locking/unlocking index files when you heavily
upading indexes in short period of time (like importing ~8000 products,
almost every time it ends with this problem)
In current project i think i will use Hibernaate Search, but so far i'm not
able to say anythnig
I like the idea, as a complement to structural finders (which always requires
predefined indexes for decent performance on large data volumes).
Do you think http://www.hibernate.org/subprojects/search.html Hibernate
Search is the right way to go, or is it better to use Lucene api ourselves.
May
We are now using findByCondition which is easy and very
straightforward to use. If you have good model (and sculptor is very
powerful tool for making good models) you can use fulltext search for
notes or something similar but don't see reason why to use full text
for normal fields. For example 'lik
Have you ever considered support for Apache Lucene? From my experience(not a
great experience but still;)) almost evry single application have a search
functionality for selected entities. It would be great if developer could
mark entity in dsl to be indexed by lucene. Giving user the opportunity
