October 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-70) Add @Equals(property="name")

by Juergen Zimmermann (JIRA)

Add @Equals(property="name") ---------------------------- Key: HV-70 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-70 Project: Hibernate Validator Issue Type: New Feature Affects Versions: 3.1.0.CR2 Reporter: Juergen Zimmermann It would be nice to have something like: public class Customer implements Serializable { private String password; @Equals(property="password") // the name of the property above private String password2; ... } Such entity classes would be helpful for user interfaces e.g. inside registration pages where you want to avoid typos or ensure that a human being is registering. -- 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

13 years, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-115) Add a default value for indexing null value

by Julien Brulin (JIRA)

Add a default value for indexing null value ------------------------------------------- Key: HSEARCH-115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-115 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Julien Brulin Hi, Null elements are not indexed by lucene then it's not easy to use a nullable property in lucene query. I have a TagTranslation entity in my model with a nullable property language. In this case null is used as default language for tag translation. Each translation may have many variations like synonyms. Because I can specified a default value for null value in the @Field annotation like this @Field(index=Index.UN_TOKENIZED, store=Store.NO, default='null'), i can't search a cat tag with a default translation like this : +value:cat* +lang:null <pre></code> @Entity() @Table(name="indexing_tag_trans") @org.hibernate.annotations.Cache(usage=org.hibernate.annotations.CacheConcurrencyStrategy.READ_WRITE) @Indexed public class TagTranslation implements java.io.Serializable { private static final long serialVersionUID = -1065316566731456110L; @Id @GeneratedValue(strategy=GenerationType.IDENTITY) @DocumentId private Integer id; @Field(index=Index.UN_TOKENIZED, store=Store.NO) private String language; @Field(index=Index.TOKENIZED, store=Store.YES) private String value; @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.LAZY) @org.hibernate.annotations.Fetch(org.hibernate.annotations.FetchMode.SUBSELECT) @JoinColumn(name="translation_id") @IndexedEmbedded private List<TagVariation> variations = new LinkedList<TagVariation>(); public TagTranslation() { } ... </code> </pre> What do you think about that ? Ps: sorry for english write, i am a french guy. -- 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

13 years, 8 months

4
28
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-618) BridgeFactory should pass along the field type to the field bridge constructor (if an appropriate constructor exists)

by I D (JIRA)

BridgeFactory should pass along the field type to the field bridge constructor (if an appropriate constructor exists) --------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-618 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-618 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.3.0.Beta2 Environment: Hibernate Core 3.6.0 Reporter: I D Priority: Minor Currently, only the built in EnumBridge is getting access to the field type via its constructor. That's a shame, since the field type is very useful information, and may be necessary for certainy types of bridges, plus it's readily available to the BridgeFactory. Here's one use case: Suppose I want to create a bridge named EnumOrdinalBridge, similar to EnumBridge but saving the constants' ordinals to the index (instead of their names/values). This bridge would need to know the Enum type, so the only way this could be done presently is to make it a ParameterizedBridge and then to pass the enum's class name via the "params" param of the @FieldBridge annotation. Here is how an invokation of such a bridge would look: {code} public enum Gender {MALE,FEMALE} {code} {code} @Field(index = Index.UN_TOKENIZED) @FieldBridge(impl = EnumOrdinalBridge.class, params = {@Parameter(name="class", value="package.name.Gender")}) public Gender getGender() { return gender; } {code} Note the problematic use of qualified class name as a string literal - this is neither portable nor refactoring-proof. What if I wanted to change the name of the enum or move it to another package (or what if I simply misspell the qualified class name)? These will all lead to runtime (rather than compile-time) errors. Also, repetition's bad (m'kay?), so there's no reason to have to explicitly pass along information to the bridge when that information is already implicitly available to the BridgeFactory. I suggest you use reflection in BridgeFactory to detect whether the constructed FieldBridge has a constructor with one argument of type Class. If so - that constructor will be used (instead of the no-args constructor, currently used for all non-built-in field bridges), and the type of the field will be passed as its argument. With this behavior implemented, the above example can be nicely reduced to the following, and we'll have achieved code portability and enhanced compile-time safety: {code} public enum Gender {MALE,FEMALE} {code} {code} @Field(index = Index.UN_TOKENIZED) @FieldBridge(impl = EnumOrdinalBridge.class) public Gender getGender() { return gender; } {code} -- 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

13 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-573) PerDPQueueProcessor forces release of lock even if not held - causes corrupt index

by Christian Köberl (JIRA)

PerDPQueueProcessor forces release of lock even if not held - causes corrupt index ---------------------------------------------------------------------------------- Key: HSEARCH-573 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-573 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.1, 3.2.0.Final, 3.2.0.CR1 Environment: Hibernate 3.5.0-Final, Oracle 10g Reporter: Christian Köberl Occurs: when an indexed entity is modified while another thread is re-indexing the index for that entity Consequences: Hibernate Search calls "workspace.forceLockRelease();" in the catch-block of PerDPQueueProcessor#run - so the lock held by the batch indexer is forcefully released. That means the next entity index operation will write to the index causing the index to be corrupt. h2. First Exception - triggers forceLockRelease {noformat} ERROR| Unexpected error in Lucene Backend: | at org.hibernate.search.backend.impl.lucene.PerDPQueueProcessor.run(PerDPQueueProcessor.java:118) org.hibernate.search.SearchException: Unable to open IndexWriter at org.hibernate.search.backend.Workspace.getIndexWriter(Workspace.java:159) at org.hibernate.search.backend.impl.lucene.PerDPQueueProcessor.run(PerDPQueueProcessor.java:103) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:432) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) at java.lang.Thread.run(Thread.java:811) Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@C:\Temp\turntableLuceneIndex\LogEntry\lucene-74da319434c1dd9f133d63245791e1b4-write.lock at org.apache.lucene.store.Lock.obtain(Lock.java:85) at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:1538) at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1067) at org.hibernate.search.backend.Workspace.getIndexWriter(Workspace.java:152) ... 7 more WARN | going to force release of the IndexWriter lock | at org.hibernate.search.backend.Workspace.forceLockRelease(Workspace.java:221) {noformat} h2. second Exception - index is destroyed {noformat} ERROR| Exception occurred org.hibernate.search.SearchException: Unable to add to Lucene index: class com.poi.egh.turntable.vehicle.domain.vehicle.Vehicle#200 Primary Failure: Entity com.poi.egh.turntable.vehicle.domain.vehicle.Vehicle Id 200 Work Type org.hibernate.search.backend.AddLuceneWork | at org.hibernate.search.exception.impl.LogErrorHandler.logError(LogErrorHandler.java:83) org.hibernate.search.SearchException: Unable to add to Lucene index: class com.poi.egh.turntable.vehicle.domain.vehicle.Vehicle#200 at org.hibernate.search.backend.impl.lucene.works.AddWorkDelegate.performWork(AddWorkDelegate.java:81) at org.hibernate.search.backend.impl.lucene.PerDPQueueProcessor.run(PerDPQueueProcessor.java:106) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:432) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) at java.lang.Thread.run(Thread.java:811) Caused by: java.io.IOException: Cannot overwrite: C:\temp\turntableLuceneIndex\vehicle\_5.fdt at org.apache.lucene.store.FSDirectory.initOutput(FSDirectory.java:362) at org.apache.lucene.store.SimpleFSDirectory.createOutput(SimpleFSDirectory.java:58) at org.apache.lucene.index.FieldsWriter.<init>(FieldsWriter.java:61) at org.apache.lucene.index.StoredFieldsWriter.initFieldsWriter(StoredFieldsWriter.java:66) at org.apache.lucene.index.StoredFieldsWriter.finishDocument(StoredFieldsWriter.java:144) at org.apache.lucene.index.StoredFieldsWriter$PerDoc.finish(StoredFieldsWriter.java:190) at org.apache.lucene.index.DocumentsWriter$WaitQueue.writeDocument(DocumentsWriter.java:1466) at org.apache.lucene.index.DocumentsWriter$WaitQueue.add(DocumentsWriter.java:1485) at org.apache.lucene.index.DocumentsWriter.finishDocument(DocumentsWriter.java:1089) at org.apache.lucene.index.DocumentsWriter.updateDocument(DocumentsWriter.java:775) at org.apache.lucene.index.DocumentsWriter.addDocument(DocumentsWriter.java:750) at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java:2454) at org.hibernate.search.backend.impl.lucene.works.AddWorkDelegate.performWork(AddWorkDelegate.java:77) ... 7 more {noformat} -- 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

13 years, 8 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-5705) Docs typos - EM 3.6

by Ondra Žižka (JIRA)

Docs typos - EM 3.6 ------------------- Key: HHH-5705 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5705 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.6.0 Environment: select from, param from Formula as form, Parameter as param Reporter: Ondra Žižka 1) "select from, param from Formula as form, Parameter as param" should be "select form ..." I suggest rather "f" for the alias for formula. BTW, using uppercase for keywords would help prevent such typos. 2) http://docs.jboss.org/hibernate/entitymanager/3.6/reference/en/html/confi... - "you can provides" -- 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

13 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-532) FSSlaveDirectoryProvider could retry several times when the current marker file is not found

by Hardy Ferentschik (JIRA)

FSSlaveDirectoryProvider could retry several times when the current marker file is not found -------------------------------------------------------------------------------------------- Key: HSEARCH-532 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-532 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.2.0.Final Reporter: Hardy Ferentschik Fix For: 3.3.0 The {{FSMasterDirectoryProvider}} has a hole in the startup procedure where it is possible for the {{FSSlaveDirectoryProvider}} to not being able to find the current marker file. At the moment the startup for the slave will fail in this case. We could let the {{FSSlaveDirectoryProvider}} retry for a couple of times to allow the master to create the marker file. This problem can also occur during runtime, but there the {{FSSlaveDirectoryProvider}} just skips a sync. However, we log this as error. Probably should just be a warning. -- 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

13 years, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5701) Add .metadata/* to .gitignore

by Yoryos Valotassios (JIRA)

Add .metadata/* to .gitignore ----------------------------- Key: HHH-5701 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5701 Project: Hibernate Core Issue Type: Improvement Reporter: Yoryos Valotassios Eclipse adds the directory with the name .metadata if someone uses the project root directory as a workspace location and git tracks it! -- 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

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-390) HibernateSearchResourceLoader uses default charset for reading resources

by Ivan Holub (JIRA)

HibernateSearchResourceLoader uses default charset for reading resources ------------------------------------------------------------------------ Key: HSEARCH-390 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-390 Project: Hibernate Search Issue Type: Bug Components: analyzer Affects Versions: 3.1.1.GA Reporter: Ivan Holub HibernateSearchResourceLoader uses default charset for reading resources. So stop words are not working for other languages. @AnalyzerDef(name="ru", tokenizer=(a)TokenizerDef(factory=StandardTokenizerFactory.class), filters={ @TokenFilterDef(factory=StandardFilterFactory.class), @TokenFilterDef(factory=LowerCaseFilterFactory.class), @TokenFilterDef(factory=StopFilterFactory.class, params=@Parameter(name="words", value="stopwords/stopwords_ru.txt")), @TokenFilterDef(factory=SnowballPorterFilterFactory.class, params=@Parameter(name="language", value="Russian")) stopwords/stopwords_ru.txt is UTF-8 file To fix the problem I constructed Analyzer in separate class and without using AnalyzerDef. -- 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

13 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-416) Analyze Payload and how this could be used to store id and class in the index and not the document

by Emmanuel Bernard (JIRA)

Analyze Payload and how this could be used to store id and class in the index and not the document -------------------------------------------------------------------------------------------------- Key: HSEARCH-416 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-416 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

13 years, 8 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-228) Write a reliability test under stress

by Emmanuel Bernard (JIRA)

Write a reliability test under stress ------------------------------------- Key: HSEARCH-228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-228 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard Fix For: 3.1.0 Write an app inserting, updating deleting concurrently Also searching concurrently and make sure data is reliable during search all that during stress conditions. -- 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

13 years, 8 months

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2010