2016-01-28 20:17 GMT+01:00 Guillaume Smet :
> Hey Gunnar,
>
> On Thu, Jan 28, 2016 at 6:52 PM, Gunnar Morling
> wrote:
>>
>> They in turn pull in Lucene in a version which potentially differs
>> from the Lucene version used by Hibernate Search itself. Also I wanted
>> to leave the door open for su
Hey Gunnar,
On Thu, Jan 28, 2016 at 6:52 PM, Gunnar Morling
wrote:
>
> They in turn pull in Lucene in a version which potentially differs
> from the Lucene version used by Hibernate Search itself. Also I wanted
> to leave the door open for supporting multiple (potentially
> incompatibly altered)
For this to work will require some significant changes. The main one being
to combine JPA's support for schema generation along
with SchemaManagementTool. The reason being simply that I will need to
encapsulate the interpretation of all these settings behind
the SchemaManagementTool facade in ord
Hi Guillaume,
Indeed there is a reason for not using the DSL: I wanted to avoid the
dependency to the ES libraries.
They in turn pull in Lucene in a version which potentially differs
from the Lucene version used by Hibernate Search itself. Also I wanted
to leave the door open for supporting multi
Hi Sanne,
On Thu, Jan 28, 2016 at 3:23 PM, Sanne Grinovero
wrote:
> I am a bit skeptical as we have CI working already on ci.hibernate.org
> and having limited people we can't really afford to fix things which
> already work.
>
I perfectly understand that. I wanted to experiment it without both
Hi all (and especially Gunnar),
I dug a bit in your ElasticSearch work today as I wanted to give a try to
the facet implementation and I was wondering if maybe we should use the
ElasticSearch DSL to build the queries instead of building raw JSON strings.
I experimented here:
https://github.com/gs
Yep: https://travis-ci.org/gsmet/hibernate-search
As already mentioned, if you want to get the results of the test, you can
push them to an AWS S3 bucket.
--
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org
I do not know how to quantify "popularity", but I do know I have seen lots
of projects using travis for commit validation.
TBH my only concern would be access to the results. And that is more an
unknown. As I have never used Travis CI I do not know how its UI works.
Guillaume do you have project
Hi Guillaume,
I am a bit skeptical as we have CI working already on ci.hibernate.org
and having limited people we can't really afford to fix things which
already work.
That said, this does look good, and it's certainly positive that we
can get some free computation resources from travis.org as our
-1 for me.
--
View this message in context:
http://hibernate-development.74578.x6.nabble.com/Re-hibernate-dev-HHH-6726-LONG-and-LONG-RAW-column-types-in-Oracle-tp1224p1243.html
Sent from the Hibernate Development mailing list archive at Nabble.com.
_
+1 to allow a setting to control *logging* of SQLWarnings. I find it silly
that MySQL handle it this way (I can only find reference to MySQL when I
google search for `JDBC getSQLWarnings performance`) in terms of it being
such a performance hit.
However I really do not like the idea of fencing th
I agree with providing a specific property to enable this behaviour.
I noticed also that handleAndClearWarnings(Connection
connection,WarningHandler handler) does the walking without checking for
the log level.
On 28 January 2016 at 07:59, Gunnar Morling wrote:
> Is the call also expensive i
Thanks! that looks like a very good idea.
On 28 January 2016 at 05:48, Vlad Mihalcea wrote:
> I created this JIRA issue for this:
>
> https://hibernate.atlassian.net/browse/HHH-10483
>
> Vlad
>
> On Wed, Jan 27, 2016 at 7:02 PM, Vlad Mihalcea
> wrote:
>
>> Then we can add this task as a featur
13 matches
Mail list logo
