Hi,
After our upgrade to 4.0 (from 3.4.1), we've started to have a lot of
lock errors on our development boxes. I thought it was due to brutal
kills of the JVM (typically Terminate in Eclipse) but we also have
them in our CI environment on a project where every test is OK.
The stracktraces look
Hi,
I opened https://hibernate.onjira.com/browse/HSEARCH-917 a few months
ago about something that really prevents us from using the DSL API in
a lot of cases.
I explained why in the JIRA issue. While I'm OK to do the ground work
of coding something and adding tests for it, I think it might be a
On Wed, Dec 28, 2011 at 2:21 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
After our upgrade to 4.0 (from 3.4.1), we've started to have a lot of
lock errors on our development boxes. I thought it was due to brutal
kills of the JVM (typically Terminate in Eclipse) but we also have
them
Hi Sanne,
On Fri, Dec 30, 2011 at 2:12 AM, Sanne Grinovero sa...@hibernate.org wrote:
[very detailed explanation]
Thanks for taking the time to answer.
While I agree with you on most of what you explained, I think the
point is: is it a good default value?.
The typical development workflow of
On Fri, Dec 30, 2011 at 5:55 PM, Sanne Grinovero sa...@hibernate.org wrote:
Proposal: https://github.com/hibernate/hibernate-search/pull/221
could you see if it improves your experience with locks? I'm deploying
a 4.1.0-SNAPSHOT as well.
Let me setup our config to exclusive + native for the
Hi Sanne and happy new year,
On Fri, Dec 30, 2011 at 6:23 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
Let me setup our config to exclusive + native for the next few days.
I can confirm you that using exclusive + native is OK for us and that
we don't have remaining locks anymore.
I
Hi Sanne,
On Sat, Jan 7, 2012 at 11:03 AM, Sanne Grinovero sa...@hibernate.org wrote:
I've written some ideas for MassIndexer improvements in the forum, to
allow it to work in background using updates instead of wiping out the
index, so that it doesn't prevent running applications to find
Hi,
In our test cases, we have a test which checks a lot of cascade
configuration (it's more to document all the cascade behaviors than to
really test an application).
After the upgrade from Hibernate 4.0 to Hibernate 4.0.1, we have a test failing:
- a person is linked to a company
- if we
Hi Steve,
On Wed, Jan 18, 2012 at 5:42 PM, Steve Ebersole st...@hibernate.org wrote:
This is unexpected and obviously unintended, but it is also clearly what the
spec says should happen. I have asked the spec lead about some possible
options that would probably still meet the intent of the
On Wed, Jan 18, 2012 at 6:31 PM, Steve Ebersole st...@hibernate.org wrote:
Well really the trouble is that you are not managing the associations in
memory. I understand the behavior is surprising, but had you simply cleaned
up the Person reference from all its associations (as the JPA spec
Hi,
On Mon, Feb 13, 2012 at 4:38 PM, Hardy Ferentschik ha...@hibernate.org wrote:
I am fine with a 3.4.2. I don't think we should put too much effort into it
ourself, but rely on the
community if they want more features back ported.
+1 for upgrading to Lucene 3.4.0
I don't think you can
Hi,
It's not something new as we checked that it was already the case with
Hibernate 3.6 but we just hit an annoying problem with @OneToOne
annotation if the relation is bidirectional.
Simplified example:
class A {
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true)
Hi,
On Mon, Feb 27, 2012 at 1:35 PM, Sanne Grinovero sa...@hibernate.org wrote:
And sent a last pull request for 3.4
https://github.com/hibernate/hibernate-search/pull/240
Thanks a lot for publishing 3.4.2. Greatly appreciated.
--
Guillaume
___
On Wed, Feb 29, 2012 at 7:50 PM, Steve Ebersole st...@hibernate.org wrote:
How are you loading these? Using Query#iterate I assume?
We are using:
entityManager().createQuery(query).getResultList(); and AFAICS in the
stacktrace Query#list.
___
Hi Emmanuel,
Here is what I have in mind:
- Providing a nice API to get the indexed classes. Currently I use
something extracted from MassIndexerImpl#toRootEntities. We use it
currently for our reindexAll implementation. As the MassIndexer uses
too much threads and connections when you have a lot
One more idea: we would like to have an API to disable Hibernate
Search temporarily.
Currently we have to start the application with a specific Spring
context configuration to do so. We would like to:
- disable Hibernate Search
- do bulk loading
- enable Hibernate Search again
- use the Mass
Hi Sanne,
On Thu, Mar 1, 2012 at 1:09 PM, Sanne Grinovero sa...@hibernate.org wrote:
I'm aware of the issue, and I wouldn't mind some help on it: it would
be better to fix the MassIndexer design to use a limited set of
threads than to expose more metadata information, don't you agree?
The
On Thu, Mar 1, 2012 at 2:55 PM, Sanne Grinovero sa...@hibernate.org wrote:
I don't dislike the concept, but are you sure that is actually going
to be faster?
If you have the bulk loading trigger async indexing events, it won't
be much different than what the MassIndexer would do, with the
On Thu, Mar 1, 2012 at 2:59 PM, Sanne Grinovero sa...@hibernate.org wrote:
I understood you where doing something crazy like that :D
My question is, this additional API would be pointless assuming we fix
HSEARCH-598?
Or we add an option like:
Hi,
Yesterday, we tried the following mapping:
EntityA {
@Embedded
private EntityB entityB;
}
EntityB {
@OneToOne
private EntityC entityC;
}
In this configuration, and only with a @OneToOne, Hibernate JPA
Modelgen doesn't generate the attribute for entityC in EntityB_
Hi,
There are a few copy/paste errors in the Hibernate Metamodel Generator
download page: http://www.hibernate.org/subprojects/jpamodelgen/download
.
This page would benefit from a s/Search/Metamodel Generator/g .
Have a nice day.
--
Guillaume
___
Hi Steve,
On Tue, Mar 13, 2012 at 10:39 PM, Steve Ebersole st...@hibernate.org wrote:
As I understood it, when accessed through the Session interface what
return type is defined by SessionImpl is irrelevant. And indeed I am
not able to reproduce this when access those methods via Session. My
Hi Hardy,
On Wed, Mar 14, 2012 at 9:35 AM, Hardy Ferentschik ha...@hibernate.org wrote:
first off, thanks for your pull requests for Modelgen. I applied both :-)
Thanks.
I did not realize that the issue you are describing here is still in issue.
Are you reproduce
this problem with the
On Wed, Mar 14, 2012 at 11:22 AM, Hardy Ferentschik ha...@hibernate.org wrote:
Thanks. I got the patch now. I have indeed not seen it before.
I need to have a closer look though, because as I said, I don't see
this test failure. As you suspect, I would not intentionally keep a failing
test
BTW, tests also fails here with Maven 3.0.4.
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On Wed, Mar 14, 2012 at 12:53 PM, Hardy Ferentschik ha...@hibernate.org wrote:
@Generated(value = org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor)
@StaticMetamodel(ZeroCoordinates.class)
public abstract class ZeroCoordinates_ {
}
Nope. I have attributes in it (and SingularAttribute
On Wed, Mar 14, 2012 at 1:20 PM, Hardy Ferentschik ha...@hibernate.org wrote:
I think it would be time to track this via a proper Jira issue. Do you mind
creating one? You can also attach the patch
you've sent me.
OK, I'll do it later today.
--
Guillaume
Hi Steve,
On Wed, Mar 14, 2012 at 4:46 PM, Steve Ebersole st...@hibernate.org wrote:
Was the initial problem you just using SessionImpl directly? Or is it a
problem of particular JDK handling the covariant return differently? In the
latter case we'd need to change the code. In the former,
Hi Hardy,
On Wed, Mar 14, 2012 at 1:36 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
On Wed, Mar 14, 2012 at 1:20 PM, Hardy Ferentschik ha...@hibernate.org
wrote:
I think it would be time to track this via a proper Jira issue. Do you mind
creating one? You can also attach the patch
Hi,
On Tue, May 8, 2012 at 10:20 AM, Hardy Ferentschik ha...@hibernate.org wrote:
Sanne also suggested an alternative solution. We may introduce a new global
option which would define the default value for Field#norms(). The default
value of this option would be obviously YES. Users like me
On Tue, May 8, 2012 at 12:27 PM, Sanne Grinovero sa...@hibernate.org wrote:
Proposal for next versions: allow @Stereotype - like user annotations?
We would let the user define custom annotations to stack/combine
multiple framework annotations, possibly centralizing what the
default is for your
On Sat, May 12, 2012 at 10:51 AM, Emmanuel Bernard
emman...@hibernate.org wrote:
That would go counter to the JPA design I think and to be honest, I like the
idea of being able to not index a given branch of a class hierarchy.
But more importantly, you would require Hibernate Search to scan
Hi Steve,
On the list again, my bad...
On Thu, May 17, 2012 at 1:07 PM, Steve Ebersole st...@hibernate.org wrote:
I am not following what you are saying about reusing keys and optimizers.
Nor how it might lead to bad execution plans. Can you elaborate on your
thoughts here?
If you have a
On Thu, May 17, 2012 at 3:02 PM, Steve Ebersole st...@hibernate.org wrote:
But just because you have 100 values in no way indicates how many rows will
be returned. And I personally know of no optimizers that make such an
assumption; its a totally worthless assumption.
That's why I put
On Thu, May 17, 2012 at 5:40 PM, Steve Ebersole st...@hibernate.org wrote:
Its an index scan, totally trivial (unless their index hashing algos are
awful as well).
It is.
Unless you have a lot of LEFT JOINs in the query due to your class
hierarchy (that's our case and the resulting queries
On Thu, May 17, 2012 at 6:53 PM, Andrej Golovnin golov...@gmx.net wrote:
Query: SELECT * FROM test WHERE oid IN (100, 101, 102, 100, 100, 100);
Index Scan using test_pkey on public.test (cost=0.00..29.72 rows=*6*
width=9) (actual time=0.024..0.034 rows=3 loops=1)
Query: SELECT * FROM test
Hi,
We just upgraded to Hibernate 4.1.7.Final (from 4.1.6.Final) and we
have a pretty bad regression with 4.1.7 and Hibernate Search 4.1.1.
We have the following stack trace when saving an object:
Caused by: org.hibernate.HibernateException: Error while indexing in
Hibernate Search (before
Hi,
On Mon, Sep 10, 2012 at 4:53 PM, Steve Ebersole st...@hibernate.org wrote:
We are going to need a test (ideally without Search) reproducing this.
OK, I'll work on providing a quick start to reproduce the problem.
Not sure I'll be able to provide a test without Search though: our
On Fri, Sep 14, 2012 at 5:55 PM, Sanne Grinovero sa...@hibernate.org wrote:
I could reproduce the same problem by just running the Hibernate
Search testsuite, from master just changing the hibernate-core
dependency from 4.1.6 to 4.1.7
Thanks Sanne.
Sorry for not providing the test case to you
Hi,
I don't know what is your policy about the dependency management but,
currently, when you include hibernate-entity-manager in the pom of an
application, it comes with dependencies to 3.1.0.Final and 3.1.0.CR2.
The problem is that hibernate-commons-annotations-4.0.1.Final requires
3.1.0.CR2
Hi Sanne,
On Mon, Oct 8, 2012 at 3:34 PM, Sanne Grinovero sa...@hibernate.org wrote:
I'll leave it to the gradle gurus on the team to say how to fix that,
but I'm surprised that Maven suggests both dependencies, that should
never be the case.
It doesn't include both, of course. But both
On Mon, Oct 8, 2012 at 7:05 PM, Steve Ebersole st...@hibernate.org wrote:
That's not exactly how the deps work here. It is in fact hibernate-core
that introduces the dep on hibernate-commons-annotations, not
hibernate-entitymanager.
AFAICS, nope.
The dependency for
On Mon, Oct 8, 2012 at 7:43 PM, Steve Ebersole st...@hibernate.org wrote:
http://search.maven.org/remotecontent?filepath=org/hibernate/hibernate-core/4.1.7.Final/hibernate-core-4.1.7.Final.pom
Argh, stupid Firefox search.
So the hibernate-commons-annotations dependency is in
On Mon, Oct 8, 2012 at 7:03 PM, Steve Ebersole
steven.ebers...@gmail.com wrote:
We are not going to get into the business of releasing projects just for new
releases of dependencies. Thats not manageable.
Totally agree on this point. That's why I suggested to add an exclusion.
That said, I'm
Hi,
Any hints or advices on how we can make progress on the regressions below?
Any further information needed, pointers on where to look at to obtain
a self contained test case?
Thanks for your feedback.
On Sat, Nov 17, 2012 at 12:34 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
Hi
On Thu, Nov 22, 2012 at 4:37 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
I'm opening a JIRA issue.
https://hibernate.onjira.com/browse/HHH-7821
--
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org
Hi Brett,
On Thu, Dec 6, 2012 at 9:44 PM, Brett Meyer brme...@redhat.com wrote:
We're still aiming to have the 4.1.9.Final release next Wed. (12/12/12).
Please let us know if there are any objections or reasons to hold off.
Any chance we could make progress on
Hi Sanne,
On Mon, Dec 10, 2012 at 7:49 PM, Sanne Grinovero sa...@hibernate.org wrote:
did you try to flush indexes before clearing the session?
fullTextSession.flushToIndexes();
fullTextSession.clear();
Hmmm, no, we didn't. That's probably what we missed...
Is it transactionally
On Mon, Dec 10, 2012 at 8:27 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
Is it transactionally safe?
From what I read, it's not.
Do you see any way to get this type of pattern working in a
transactionally safe way?
--
Guillaume
___
hibernate
On Mon, Dec 10, 2012 at 9:07 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
On Mon, Dec 10, 2012 at 8:27 PM, Guillaume Smet
guillaume.s...@gmail.com wrote:
Is it transactionally safe?
From what I read, it's not.
Do you see any way to get this type of pattern working
Hi,
solr-analysis-extras is a big package as it comes with the following
dependencies:
3594568 2012-10-06 18:46 WEB-INF/lib/lucene-smartcn-3.6.1.jar
511956 2012-10-06 18:46 WEB-INF/lib/lucene-stempel-3.6.1.jar
which is 4 MB of dependencies which are usually not that useful
(stempel is
Hi Hardy,
On Thu, Dec 13, 2012 at 10:49 AM, Hardy Ferentschik ha...@hibernate.org wrote:
I am fine with removing it, but maybe we need to sync the docs in this case
as well. It says now:
all required Solr dependencies are now defined as dependencies of the
artifact
Hi Emmanuel, Sanne,
On Mon, Dec 17, 2012 at 12:25 PM, Sanne Grinovero sa...@hibernate.org wrote:
2#
I didn't see Guillaume asking about queries, so assuming he would just
need a large write buffer where to keep the current Documents; this is
a simpler patch as we already do build such a plan
Hi,
You're probably already aware of it but just in case...
I can't login to Hibernate JIRA. It looks like the server is out of disk space:
com.atlassian.crowd.embedded.ofbiz.db.DataAccessException:
org.ofbiz.core.entity.GenericEntityException: while inserting:
Hi,
While working on HHH-7821, I wanted to use the latest 4.1.x snapshot.
However, it seems that the snapshots published aren't correct: they
don't contain the latest fixes:
See
built by the official build
chain.
Thanks for your help.
On Mon, Feb 4, 2013 at 3:48 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi,
While working on HHH-7821, I wanted to use the latest 4.1.x snapshot.
However, it seems that the snapshots published aren't correct: they
don't contain
deployment problem in JBoss repository?
do we have a CI job that run on 4.2 branch and deploy snapshot?
On Feb 16, 2013, at 7:25 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi,
Could someone take a look at this, please?
The current 4.1.10-SNAPSHOT published on the snapshots repository
Hi Marc,
On Mon, Mar 4, 2013 at 8:41 PM, Marc Schipperheyn
m.schipperh...@gmail.com wrote:
Looks like Hibernate-core 4.1.10.Final is missing from some repositories
and Hibernate-ehcache.4.1.0.Final from *all* repositories. Same goes for
hibernate-entitymanager. Shouldn't these versions be in
Hi,
Sorry for bothering you with this, but we just got hit by
https://hibernate.atlassian.net/browse/HHH-8092 in our applications
after an upgrade to 4.1.11 (we worked on fixes included in 4.1.10 and
needed the upgrade to get our bugs fixed).
Due to HHH-8092, with 4.1.10 and 4.1.11, our unique
Hi Brett,
On Thu, Apr 4, 2013 at 5:48 PM, Brett Meyer brme...@redhat.com wrote:
Guillaume, here's what I'd propose. I'll cherry-pick the fix into the 4.1
branch. Can you grab that from git (or I'll re-enable the 4.1 builds
temporary and push out a new SNAPSHOT) and re-test? Before I
On Thu, Apr 4, 2013 at 8:50 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
If the patch for HHH-8092 is easy to backport, I can do it locally if
you prefer? If it's not, it might effectively be a better idea to
cherrypick it yourself and post a snapshot.
Did it.
Looks far better
Hi Brett,
On Fri, Apr 5, 2013 at 2:38 AM, Brett Meyer brme...@redhat.com wrote:
One other issue was pointed out:
https://hibernate.atlassian.net/browse/HHH-8092?focusedCommentId=50658page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-50658
Oh, yeah. I started the
Hi Brett,
Thanks for following up on this. My comments below.
On Fri, Apr 5, 2013 at 6:44 PM, Brett Meyer brme...@redhat.com wrote:
Here's what I'd like to do. In 4.1.x, all of the unique
constraint/index/column changes from HHH-7797 [1] and the random constraint
names in HHH-1904 [2] will
Hi,
We would like to declare our global @AnalyzerDefs on a class which
isn't a specific entity.
For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
a class annotated with @MappedSuperClass but with @AnalyzerDefs, we
are forced to declare them on a concrete @Entity.
Is this an
Hi Sanne,
On Thu, Jun 20, 2013 at 6:45 PM, Sanne Grinovero sa...@hibernate.org wrote:
Great, so maybe we should just do that.
Yep, looks like a good idea and would be far cleaner.
--
Guillaume
___
hibernate-dev mailing list
On Fri, Jun 21, 2013 at 2:35 PM, Hardy Ferentschik ha...@hibernate.org wrote:
Again, I still don't see the connection between @Entity and @AnalyzerDefs.
How does you library look like and what do you want to provide. Can you
provide
an example. Does your library contain an indexed type? Are
Hi all,
On Thu, Jul 4, 2013 at 11:19 AM, Hardy Ferentschik ha...@hibernate.org wrote:
Right, the artefacts are not on Nexus and I don't seem to see them in the
staging repo either.
Any news about this?
Thanks.
--
Guillaume
___
hibernate-dev
Hi Hardy,
The SearchFactory.getIndexedTypes API looks nice.
Would it be possible to also expose something like getRootIndexedTypes
based on the magic done in MassIndexerImpl.toRootEntities?
We have copied the code of MassIndexerImpl.toRootEntities in our
framework to do so but it would be nice
(Hardy, sorry for the double post, forgot the list)
On Mon, Aug 5, 2013 at 3:20 PM, Hardy Ferentschik ha...@hibernate.org wrote:
TBH i am not completely sure I understand what the method does. The docs says:
From the set of classes a new set is built containing all indexed
subclasses, but
Hi all,
It's been a long time since the last release of JPA modelgen and we
fixed a couple of annoying bugs, namely:
https://hibernate.atlassian.net/browse/METAGEN-81
https://hibernate.atlassian.net/browse/METAGEN-82
And this one was a work in progress a long time ago and I should
probably go
On Mon, Aug 5, 2013 at 5:10 PM, Hardy Ferentschik ha...@hibernate.org wrote:
And this one was a work in progress a long time ago and I should
probably go back to work on it to provide some feedback to Hardy:
https://hibernate.atlassian.net/browse/METAGEN-85
Right, I still have not been able
On Mon, Aug 5, 2013 at 5:37 PM, Sanne Grinovero sa...@hibernate.org wrote:
I understand my code, but I'm not sure I understood why you would need this?
Instead of calling the mass indexer directly for all our classes, we
get the root indexed types and we index them one by one using the mass
On Mon, Aug 5, 2013 at 6:07 PM, Sanne Grinovero sa...@hibernate.org wrote:
So we actually would be better off fixing that issue, rather than
polluting the metadata API with hard to explain methods.
Fixing the issue in its entirety is very complex, but what would you
think of having an option
On Mon, Aug 5, 2013 at 6:45 PM, Sanne Grinovero sa...@hibernate.org wrote:
Great, that's https://hibernate.atlassian.net/browse/HSEARCH-1384
then. Guillaume, is that something you would consider giving a try
yourself?
Yep. I'll have a look and see if I can come up with something.
I assigned
Hi,
Looks like there is a problem with the code templates file here:
https://community.jboss.org/wiki/ContributingToHibernateUsingEclipse
It looks empty and it sure wasn't before (there was at least the
copyright notice in it).
I needed it to set up my new Kepler environment for HSEARCH and I
Hi,
On Mon, Aug 5, 2013 at 5:10 PM, Hardy Ferentschik ha...@hibernate.org wrote:
+1 We really need to get a release out. As you say we have a couple of things
which are actually resolved
and just need a release, but I also think at the very least we need to look
at METAGEN-92.
Basically we
On Tue, Aug 6, 2013 at 6:38 PM, Hardy Ferentschik ha...@hibernate.org wrote:
I think we should move to .Next:
- METAGEN-72 - Generate attributes for @Transient columns : it might
be nice to have but it's definitely not something required (there are
a lot of other binding generators out there
Hi,
AFAICS in the pom.xml, Search is now compiled for Java 6.
I think It would be a good idea to add the @Override annotation to the
methods implemented from an interface, considering it's supported in
Java 6.
I'm willing to do the grunt work and prepare a pull request in the
next few days if
Hi Gunnar,
On Fri, Aug 9, 2013 at 6:19 PM, Gunnar Morling gun...@hibernate.org wrote:
Not sure though whether an ad-hoc action is required to add it everywhere.
In Eclipse I'm having a save action which adds it to every file I'm
touching in the course of other work I'm doing.
I don't like
Hi,
On Fri, Aug 9, 2013 at 6:41 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
I'll see what I can do about it as everyone seems to agree with it.
Done thanks to Eclipse quick fix:
https://hibernate.atlassian.net/browse/HSEARCH-1387
https://github.com/hibernate/hibernate-search/pull/467
Hi,
I'm planning to work on the pom files in the next few days.
Here is more or less the plan I have in mind:
- centralize all dependencies versions in the properties of the parent
pom file. A couple of them are directly in the dependencyManagement
block. It's easier to update them this way.
-
Hi,
Note: this is just a prospective idea I'd like to discuss. Even if
it's a good idea, it's definitely 5.0 material.
Those who have used Solr and are familiar with the Solr schema have
already seen the ability to use different analyzer for indexing and
querying.
It's usually useful when you
On Tue, Aug 13, 2013 at 10:58 AM, Sanne Grinovero sa...@hibernate.org wrote:
On 13 August 2013 09:12, Guillaume Smet guillaume.s...@gmail.com wrote:
Hi,
I'm planning to work on the pom files in the next few days.
Here is more or less the plan I have in mind:
- centralize all dependencies
Hi,
Here we go for the current state of my work and what I would like to do:
https://hibernate.atlassian.net/browse/HSEARCH-1392
I created a PR so that we can discuss the changes already made:
https://github.com/hibernate/hibernate-search/pull/472
Thanks for your feedback.
--
Guillaume
Hi Emmanuel,
On Wed, Aug 21, 2013 at 4:52 PM, Emmanuel Bernard
emman...@hibernate.org wrote:
To me the real answer is to the programmatic API and add a
programmatic mapping factory to your configuration.
See Example 4.28. Use a mapping factory in
Hi Emmanuel,
On Wed, Aug 21, 2013 at 5:20 PM, Emmanuel Bernard
emman...@hibernate.org wrote:
Can you explain to me why you would need a different analyzer for a
wildcard query? My brain is still tanning on the beach.
Well, it's the Lucene way. Wildcard queries are usually not analyzed
(see
Hi,
We have a weird problem here with Search 4.3 and ORM 4.2.7.SP1. I
wonder if it rings a bell for anyone?
In yet to determined circumstances, an object is missing from the
search results.
This object is returned by the Lucene search but is not added in the
results because it isn't
Hi Sanne,
On Mon, Nov 4, 2013 at 11:21 PM, Sanne Grinovero sa...@hibernate.org wrote:
Definitely needs further inspection, could you please open a JIRA?
Done:
https://hibernate.atlassian.net/browse/HSEARCH-1448
Would you be able to verify the same problem with the simple HashMap
second level
Hi all,
ORM 4.2.8.Final breaks the API of EntityKey as it removes tenantId
from the constructor.
Typically, in HSearch, we have the following call:
/commit/bf26311474257c2f0118615e003553095c2d87b0
On 12/05/2013 10:51 AM, Guillaume Smet wrote:
Hi all,
ORM 4.2.8.Final breaks the API of EntityKey as it removes tenantId
from the constructor.
Typically, in HSearch, we have the following call:
https://github.com/hibernate/hibernate-search
SP release. I'd fix it for 4.2.9, before compatibility in other
products became an actual issue. Any strong arguments against that?
Brett Meyer
Software Engineer
Red Hat, Hibernate ORM
- Original Message -
From: Guillaume Smet guillaume.s...@gmail.com
To: Scott Marlow smar
On Thu, Dec 5, 2013 at 5:31 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
I'm working on a pull request to fix the problem in search as
requested by Steve.
Done: https://github.com/hibernate/hibernate-search/pull/521
--
Guillaume
___
hibernate
communicate
about it?
Thanks for your feedback.
On Thu, Dec 5, 2013 at 5:46 PM, Guillaume Smet guillaume.s...@gmail.com wrote:
On Thu, Dec 5, 2013 at 5:31 PM, Guillaume Smet guillaume.s...@gmail.com
wrote:
I'm working on a pull request to fix the problem in search as
requested by Steve.
Done
?
The release blog would then also be an appropriate medium to warn
about the incompatibility.
Sanne
On 6 December 2013 10:30, Guillaume Smet guillaume.s...@gmail.com wrote:
Is there any decision taken about this?
I find the situation to have 2 major Hibernate components incompatible
after an upgrade
Hi all,
It's been quite a long time since I came up with lazy initialization
problems in the mass indexer for the last time.
Unfortunately, this time, I don't see exactly how to fix this one and
I would like to ask for your advice about it.
The problem is quite simple:
I want to index the
Hi Sanne,
On Wed, Jan 8, 2014 at 1:43 PM, Sanne Grinovero sa...@hibernate.org wrote:
As far as I remember, you and your team reported (and helped fixing!)
a depressingly long list of issues since approximately the migration
to Hibernate ORM 4 of your applications (adopting AFAIR early betas of
Hi Sanne,
On Mon, Jan 13, 2014 at 1:06 AM, Sanne Grinovero sa...@hibernate.org wrote:
Then, you can remove all the previous workarounds too: given we'd be
removing the re-attach processing and all the proxy re-attaching code,
it might even win you something in performance.. I don't know that
On Tue, Jan 14, 2014 at 12:11 AM, Sanne Grinovero sa...@hibernate.org wrote:
Of course I'm ok with that. If any I was under the impression you
needed a solution urgently; if that's the case, be aware I suspect
this could be a trivial change.
It's for a sort on a table (but an important one) so
Hi,
I'm starting our migration to ORM 4.3 to be able to provide some
(hopefully useful) feedback on ORM 4.3 and Search 4.5.
One thing we did in most of our apps was injecting Spring managed
interceptor into the session factory using a trick very similar to
what is explained there:
Hi Emmanuel,
On Thu, Feb 20, 2014 at 10:19 AM, Emmanuel Bernard
emman...@hibernate.org wrote:
## DisMax as top level DSL feature
Should we add .dismax() like we did bool()?
I am hard pressed to find a use case.
It's a project I have for a long time. I wanted to have an intern this
year to
1 - 100 of 609 matches
Mail list logo
