[Hibernate-JIRA] Created: (HSEARCH-1027) Analyzer delegates fail to delegate all methods
by Sanne Grinovero (JIRA)
Analyzer delegates fail to delegate all methods
-----------------------------------------------
Key: HSEARCH-1027
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1027
Project: Hibernate Search
Issue Type: Bug
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 4.1.0.Alpha1
org.apache.lucene.analysis.Analyzer.getOffsetGap(Fieldable) was not being "routed" to the proper delegate, which introduces functional differences in text analysis.
org.apache.lucene.analysis.Analyzer.close() was not replicated either, which should not cause problems unless the delegated implementation required it.
org.hibernate.search.util.impl.ScopedAnalyzer.reusableTokenStream(String, Reader) was missing: this causes a HUGE performance drop since reusable analyzers are usually expensive to initialize, and they where not being reused.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[Hibernate-JIRA] Created: (HSEARCH-1020) Regression in 3.4: index not updated after updating a collection
by Guillaume Smet (JIRA)
Regression in 3.4: index not updated after updating a collection
----------------------------------------------------------------
Key: HSEARCH-1020
URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1020
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 4.0.0.Final, 3.4.1.Final
Reporter: Guillaume Smet
Hi,
I know it's not exactly documented but, before 3.4, it was possible to index a collection with the @Field annotation and a FieldBridge (in our case, a FieldBridge which indexes all the ids of the linked entities).
We use it a lot instead of @IndexedEmbedded because it allows us not to bloat our index when we want to index a collection containing indexed entities (@IndexedEmbedded integrates all the fields of the linked entities in the index of the main entity - which is often not needed in our case: we have autocomplete field for our search so we only need the id of the linked entities).
Starting with 3.4, it doesn't work anymore: the entity is correctly indexed when created but, if we update only the collection, the index is not updated.
The problem is in AbstractDocumentBuilder.isCollectionRoleExcluded(String collectionRole) which is called to check if the collection update should trigger a reindex. This method should also consider the collections having a @Field annotation, not just the collections with @IndexedEmbedded or @ContainedIn.
FWIW, if somebody else has this problem, as a workaround, I use a non default boost strategy to force the reindex but it would be nice to have it fixed because it's really a useful pattern.
If needed, we can provide a test case.
Thanks.
--
Guillaume
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[Hibernate-JIRA] Created: (HV-482) Weblogic ConstrantDeclationException HVbeta2
by Tim Canavan (JIRA)
Weblogic ConstrantDeclationException HVbeta2
--------------------------------------------
Key: HV-482
URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-482
Project: Hibernate Validator
Issue Type: Bug
Affects Versions: 4.2.0.Beta2
Environment: Weblogic 10.3
Reporter: Tim Canavan
After upgrading to HV beta2 and changing all our validations to be at the interface level
we get the constraint declaration exception
Caused by: javax.validation.ConstraintDeclarationException: Only the root method of an overridden method in an inheritance hierarchy may be annotated with parameter constraints. The following method itself has no parameter constraints but it is not defined on a sub-type of class
Under OpenEJB which our unit tests use everything works fine.
Is there any code that HV could use that would allow it to understand these proxies or would an option be available
to turn the check off.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months
[Hibernate-JIRA] Created: (BVAL-260) Implement boolean composition of composed constraints
by Hardy Ferentschik (JIRA)
Implement boolean composition of composed constraints
-----------------------------------------------------
Key: BVAL-260
URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-260
Project: Bean Validation
Issue Type: New Feature
Components: spec-general
Affects Versions: 1.0 final
Reporter: Hardy Ferentschik
Should we add boolean composition of constraints as provided by Hibernate Validator (HV-390).
Some examples:
{code}
@ConstraintComposition(OR)
@Pattern(regexp = "K")
@Size(min = 2, max = 10)
@ReportAsSingleViolation
@Target({ METHOD, FIELD })
@Retention(RUNTIME)
@Constraint(validatedBy = { })
public @interface PatternOrSize {
public abstract String message() default "OR";
public abstract Class<?>[] groups() default { };
public abstract Class<? extends Payload>[] payload() default { };
}
{code}
or
{code}
@ConstraintComposition(ALL_FALSE)
@Target({ METHOD, FIELD, ANNOTATION_TYPE })
@Retention(RUNTIME)
@Constraint(validatedBy = { })
@List({
@Pattern(regexp = "12345678901"),
@Pattern(regexp = "98765678765"),
@Pattern(regexp = "55555555555"),
@Pattern(regexp = "123456")
})
public @interface Blacklist {
public abstract String message() default "Blacklisted SSN";
public abstract Class<?>[] groups() default { };
public abstract Class<? extends Payload>[] payload() default { };
}
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 12 months