On 10 August 2015 at 21:32, Gunnar Morling wrote:
> Deal: https://hibernate.atlassian.net/browse/HSEARCH-1959
>
> Feel free to merge the PR yourself ;)
Thanks, done! Had to add a test to figure out some corner cases...
will be useful when we'll move away from class type based
polymorphispm (free-
On 7 August 2015 at 13:31, Gustavo Fernandes wrote:
> On Fri, Aug 7, 2015 at 1:14 PM, Sanne Grinovero wrote:
>>
>> A quick update on some more exploration on this:
>> it turns out sorting on a NumericField when this field is also using
>> an "indexNullAs" token gets the UninvertingReader approach
Deal: https://hibernate.atlassian.net/browse/HSEARCH-1959
Feel free to merge the PR yourself ;)
Thanks!
2015-08-10 18:30 GMT+02:00 Sanne Grinovero :
> open a JIRA, assign it to me and I'll send a pull request ;)
>
> On 10 August 2015 at 17:10, Gunnar Morling wrote:
>> Hi,
>>
>> Could someone gi
open a JIRA, assign it to me and I'll send a pull request ;)
On 10 August 2015 at 17:10, Gunnar Morling wrote:
> Hi,
>
> Could someone give me a one-sentence definition of what's the method
> named above is supposed to do? Its name gives me some ideas, but I'd
> love to see a proper documentation
Hi,
Could someone give me a one-sentence definition of what's the method
named above is supposed to do? Its name gives me some ideas, but I'd
love to see a proper documentation of the intended behaviour there.
Thanks,
--Gunnar
___
hibernate-dev mailing
On 08/07/2015 02:41 PM, Steve Ebersole wrote:
> Yeah, which is great when you can rely on impl-specific apis.
Agreed. I'm not sure of what we should do when ORM is running in
environments that cannot rely on a NarayanaJtaPltaform. Especially,
when every call into Hibernate ORM is from a diff
On Mon, Aug 10, 2015 at 12:34:33PM +0100, Davide D'Alto wrote:
> I'm not sure there is an easy way to convert Instant and DateTime to a
> numeric value.
> The problem is that the resolution for temporal types is nanoseconds, the
> following datetime is valid:
>
> year: -999.999.999
> month: 12
> d
On 10 August 2015 at 12:16, Gunnar Morling wrote:
>> With these new types,backwards compatibility is a non-issue. So unless
>> someone makes a strong case for needing these as String in the index,
>> what about we drop some complexity?
>
> ElasticSearch uses Strings for transferring dates in JSON
I'm not sure there is an easy way to convert Instant and DateTime to a
numeric value.
The problem is that the resolution for temporal types is nanoseconds, the
following datetime is valid:
year: -999.999.999
month: 12
day: 31
hour: 23
minute: 59
second: 59
nanos: 999.999.999
It gets more complica
> With these new types,backwards compatibility is a non-issue. So unless
> someone makes a strong case for needing these as String in the index,
> what about we drop some complexity?
ElasticSearch uses Strings for transferring dates in JSON structures
(see
https://www.elastic.co/guide/en/elastics
On 10 August 2015 at 11:04, Hardy Ferentschik wrote:
> Hi,
>
> sorry, I am late to the game, but I here are some more thoughts on this.
>
> I think the consensus so far is that
>
> # Date/time types which represent an instant in time are treated as usual.
> They can be string encoded (per defau
Hi,
sorry, I am late to the game, but I here are some more thoughts on this.
I think the consensus so far is that
# Date/time types which represent an instant in time are treated as usual.
They can be string encoded (per default MMddHHmmssSSS) or numerically
in which case the numeric l
12 matches
Mail list logo
