Hi guys
Do you have an ETA on Hibernate Search 3.3.0, even early betas, etc? I'm
particularly keen on HSEARCH-397 (to be able to finalise ISPN-194).
Cheers
--
Manik Surtani
ma...@jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
__
Most people are on JPA 2 atm. so Hibernate Search 3.2 is not getting as much
attention as hoped.
We need to do 3.2 beta2 3.2 beta 3 3.2 final and then we can think about a 3.3
timeframe.
In particular the Query DSL has not moved (I think it's more important for
infinispan than HSEARCH-397).
On
On 7 Jan 2010, at 13:18, Emmanuel Bernard wrote:
> Most people are on JPA 2 atm. so Hibernate Search 3.2 is not getting as much
> attention as hoped.
> We need to do 3.2 beta2 3.2 beta 3 3.2 final and then we can think about a
> 3.3 timeframe.
>
> In particular the Query DSL has not moved (I t
I don't think you can realistically remove a tech preview flag from a query API
which does not have a decent query builder :)
On 7 janv. 2010, at 14:33, Manik Surtani wrote:
>
> On 7 Jan 2010, at 13:18, Emmanuel Bernard wrote:
>
>> Most people are on JPA 2 atm. so Hibernate Search 3.2 is not g
Sure, let's do one at the beginning of next week.
On Wed, 2010-01-06 at 18:11 +0100, Emmanuel Bernard wrote:
> Steve,
> Do you think there is enough material / bug fix to cut another beta
> for inclusion in AS 6 M2?
> Something like a 2 weeks target.
>
>
> On my side that would make sense to pu
My understanding is that the return types for aggregation function in
criteria queries should follow the same rules as defined for JPAQL. So
first, is that a correct understanding?
The confusion is the type signatures of the builder methods, espcially
the ones that "change" based on the argument
We fail because we return Long and not Integer, correct?
That's one of the latest changes we did in the spec (the addition of the
sumAsLong / sumAsDouble, especially for the case where you sum two integers.
"
>> We will add the following 2 methods to the QueryBuilder(now CriteriaBuilder)
>>i
I went ahead and set up this next release in JIRA (3.5.0-Beta-3) and
moved all unresolved issues to the 3.5 working release. If there is
anything you need in 3.5.0-Beta-3 that is not there speak up now (by
scheduling the corresponding JIRA issue) or forever hold your piece :)
On Thu, 2010-01-07
