[hibernate-dev] [hibernate-hql-parser] 1.0.0.Alpha3 released

[Sanne Grinovero]

Hi Adrian,
we don't have an ETA for that specific issue as the user who
originally proposed the issue on the forum didn't provide a full test.
I think I have an idea of what could be happening, but it seems very
hard to forge a unit test which could really reproduce it, and I don't
think we'll want to fix that in Hibernate Search 4.x anyway as it
would break current mappings.

So I tried to upgrade the Hibernate Search code in Infinispan Query to
check what you're talking about, and indeed I get exceptions with a
similar message but I don't think HSEARCH-1318 is related, I'm not
sure yet what is exactly happening but it's definitely not a mapping
circularity problem. I'll let you know.

-- Sanne

On 14 August 2013 16:26, Gunnar Morling <gunnar at hibernate.org> wrote:
> Adrian,
>
> Do you happen to have an isolated test case which shows that issue? This
> would help me in analyzing the issue.
>
> Thanks,
>
> --Gunnar
>
>
>
> 2013/8/14 Adrian Nistor <anistor at redhat.com>
>>
>> Thanks a lot guys!
>>
>> So far everything works fine with your latest fixes in hql parser. There
>> is however that issue in hibernate-search 4.4.0.Alpha1 that prevents us to
>> integrate this in master right now because too many of infinispan-query
>> tests would fail (due to
>> https://hibernate.atlassian.net/browse/HSEARCH-1318). Do you have an ETA for
>> it?
>>
>> Adrian
>>
>>
>> On 08/13/2013 11:17 PM, Gunnar Morling wrote:
>>
>> 2013/8/13 Sanne Grinovero <sanne at hibernate.org>
>>>
>>> @Gunnar I've included your last pull, tagged it and uploaded it already.
>>
>>
>> Awesome Sanne, thanks.
>>
>>>
>>> I've sent a pull to OGM including your tests and more tests to verify
>>> the LIKE behavior; I think they are quite comprehensive and are
>>> passing, but if you are able to add more failing ones please send them
>>> to me :-)
>>
>>
>> Ok, will check it out tomorrow.
>>>
>>>
>>> No changes where needed, it just worked fine. I suspect you didn't
>>> take case sensitivity in consideration when trying? It is case
>>> sensitive, and should not be applied on analyzed fields.
>>
>>
>> I thought I used correct casing, but it might be I got it wrong. Either
>> way nice that it's working! Thanks for checking it out and adding more
>> tests.
>>>
>>>
>>> @Adrian, this should contain all the fixes you needed; if not we don't
>>> mind making more releases soon.
>>
>>
>> Right, just let us/me know in case you need anything more.
>>>
>>>
>>> Cheers,
>>> Sanne
>>
>>
>> --Gunnar
>>
>>
>>
>