November 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-810) @NumericFields with NumericField forName require @Field to use name=

by Izaak Alpert (JIRA)

@NumericFields with NumericField forName require @Field to use name= -------------------------------------------------------------------- Key: HSEARCH-810 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-810 Project: Hibernate Search Issue Type: Bug Reporter: Izaak Alpert Priority: Minor It seems that unless name for the first @Field is specified range searches on that field will not be numeric Doesn't work: public class TestExampleClass { @Fields({ @Field( index = Index.UN_TOKENIZED), @Field(name = "quantityFitted_forSort", index = Index.UN_TOKENIZED, store = Store.YES) }) @NumericFields({ @NumericField(forField = "quantityFitted") }) private Integer quantityFitted; } public class TestExampleClass { @Fields({ @Field(name = "quantityFitted", index = Index.UN_TOKENIZED), @Field(name = "quantityFitted_forSort", index = Index.UN_TOKENIZED, store = Store.YES) }) @NumericFields({ @NumericField(forField = "quantityFitted") }) private Integer quantityFitted; } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-918) Refactor AbstractDocumentBuilder.PropertiesMetadata

by Hardy Ferentschik (JIRA)

Refactor AbstractDocumentBuilder.PropertiesMetadata --------------------------------------------------- Key: HSEARCH-918 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-918 Project: Hibernate Search Issue Type: Improvement Affects Versions: 4.0.0.Beta1 Reporter: Hardy Ferentschik Fix For: 4.1 This metadata structure uses parallel arrays to collect metadata. This data structure is hard to maintain. It would be better to have a meta data instance while keeps all information for a single property. Also PropertiesMetadata should become a standalone class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-904) Have TwoWayFieldBridge report which fields should be loaded from a Document

by Sanne Grinovero (JIRA)

Have TwoWayFieldBridge report which fields should be loaded from a Document --------------------------------------------------------------------------- Key: HSEARCH-904 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-904 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Fix For: 4.0.0.Beta1 This is needed to use a FieldSelector in more cases. See also HSEARCH-213. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-697) Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery

by Sanne Grinovero (JIRA)

Think about improving type mismatch detection between QueryBuilder output and targeted FullTextQuery ---------------------------------------------------------------------------------------------------- Key: HSEARCH-697 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-697 Project: Hibernate Search Issue Type: Bug Components: query Reporter: Sanne Grinovero Fix For: 3.4.0.Beta1 Use cases: 1)we ask for the target type when creating a QueryBuilder, then we ask again for the same information again at FullTextQuery creation - they must match. 2)it seems that when people get the match wrong, they receive cryptic error messages (see https://forum.hibernate.org/viewtopic.php?f=9&t=1009700 ) It would be nice if we could infer the target type from the builder, we'd likely have to introduce a new class hiding away org.apache.search.Query in something which knows a bit more about types. Or maybe introduce a new method in FullTextSession to create a Hibernate.Query directly from the builder, projecting on the known types. train of thoughts.. maybe this could lead to a typesafe API to define fulltext projections reusing JPA2 metamodel in case it's available. -- 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

14 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-431) More details in documentation about MassIndexer

by Sanne Grinovero (JIRA)

More details in documentation about MassIndexer ----------------------------------------------- Key: HSEARCH-431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-431 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta3 Add the new diagram Emmanuel has drawn with explanations about the different stages and pipelines of MassIndexer. -- 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

14 years, 3 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-818) Cacheable instance filters are created multiple times before being cached

by Sanne Grinovero (JIRA)

Cacheable instance filters are created multiple times before being cached ------------------------------------------------------------------------- Key: HSEARCH-818 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-818 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.4.0.Final Reporter: Sanne Grinovero Fix For: 4.0 Filters are being built during SessionFactory creation a first time, only to test creation capabilities, and then again in org.hibernate.search.query.engine.impl.HSQueryImpl.buildLuceneFilter(FullTextFilterImpl) The filter instance is created first with createFilterInstance, and only *after* being created we look it up in the cache. Same issue with Filter Factories, the factories are not cached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-896) Master nodes should flush IndexWriter only before an index copy

by Sanne Grinovero (JIRA)

Master nodes should flush IndexWriter only before an index copy --------------------------------------------------------------- Key: HSEARCH-896 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-896 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 4.1 When in a JMS/JGroups master/slave design the IndexWriter on the master doesn't need to commit all the time, it could receive a forced commit from the same timer initiating the index copy. (when Infinispan is not used, as it replicates changes in real time) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-868) Support DISTINCT select on single field projection

by Sanne Grinovero (JIRA)

Support DISTINCT select on single field projection -------------------------------------------------- Key: HSEARCH-868 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-868 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Sanne Grinovero Fix For: 4.0 This is an often requested feature, the information is in the index so we could expose it. I guess the hardest part of solving this issue is to propose a nice and simple API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-152) Consider using SnapshotDeletionPolicy for hot backup instead of the old locking scheme

by Emmanuel Bernard (JIRA)

Consider using SnapshotDeletionPolicy for hot backup instead of the old locking scheme -------------------------------------------------------------------------------------- Key: HSEARCH-152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-152 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Emmanuel Bernard Not sure it's really interesting in our environment though -- 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

14 years, 3 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-826) Optionally allow WorkQueuePerIndexSplitter to apply changes to indexes in parallel

by Sanne Grinovero (JIRA)

Optionally allow WorkQueuePerIndexSplitter to apply changes to indexes in parallel ---------------------------------------------------------------------------------- Key: HSEARCH-826 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-826 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Sanne Grinovero Fix For: 4.0 I think there should be two different implementations of this, a simple one like the current implementation and an alternative strategy using an Executor and waiting for each operation to complete. Async indexes could be dealt with to optimize the no-wait, but the IndexManager would return immediately anyway. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2011