On 2 July 2015 at 12:50, Hardy Ferentschik wrote:
> Hi,
>
> On Thu, Jul 02, 2015 at 12:20:46PM +0100, Sanne Grinovero wrote:
>> Ideally we should provide something similar to the Dynamic Analyzer
>> feature but which also multiplexes an entity property into multiple
>> fieldnames;
>> for example
>
I’m torn.
I anticipate that the option programmatic API will be very commonly used,
especially when we start bringing new things like custom denormalisation.
It looks quite verbose for a single setting change :/ Is that how all property
changes will have to be done in native Hibernate ORM bootstr
Hi Emmanuel, all,
Prior to ORM 5, we used to have OgmConfiguration (sub-class of the dreaded
Configuration), which provided an entry point into our custom option API:
OgmConfiguration config = ...
config.configureOptionsFor( MongoDB.class )
.associationStorage(IN_ENTITY)
.
Hi,
On Thu, Jul 02, 2015 at 12:20:46PM +0100, Sanne Grinovero wrote:
> Ideally we should provide something similar to the Dynamic Analyzer
> feature but which also multiplexes an entity property into multiple
> fieldnames;
> for example
> property "title"
> -> title_en & analyzer en
> ->
On 2 July 2015 at 11:25, Hardy Ferentschik wrote:
> Hi,
>
>> This means we might need to drop our "Dynamic Analyzer" feature:
>>
>> http://docs.jboss.org/hibernate/search/5.4/reference/en-US/html_single/#_dynamic_analyzer_selection
>
> I think that seems rather harsh.
I agree, I'd be quite unha
Hi,
> This means we might need to drop our "Dynamic Analyzer" feature:
>
> http://docs.jboss.org/hibernate/search/5.4/reference/en-US/html_single/#_dynamic_analyzer_selection
I think that seems rather harsh.
> So, the alternatives I'm seeing:
> # Dropping the Dynamic Analyzer feature
> # Ch
