[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-867) input stream support
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-867?pag...
]
Sanne Grinovero commented on HSEARCH-867:
-----------------------------------------
Hi Adam,
I agree on opening this issue, no doubt better support for this should be explicit. I only
linked to the original blogpost in case you where looking for something to have it working
with a current release.
Yes stringValue() is invoked at some point, but the trick in that case is that it's
invoked by another thread, as the backend is configured async so there is no performance
hit on the main application thread. Or do you need it to never invoke the stringValue ?
input stream support
--------------------
Key: HSEARCH-867
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-867
Project: Hibernate Search
Issue Type: Improvement
Components: analyzer, integration
Affects Versions: 3.4.0.Final
Reporter: adam
Priority: Minor
The current hibernate search functionality is not optimized for dealing with large text
contents. Two use cases:
1. indexing an external PDF that's 100MB where an @Field is set on a getter
2. indexing a @Lob field
in both cases, the method must return a string, or a base class, which might mean that
you have an InputStream that's 50MB, which gets concatenated into a string, and then
passed to an analyzer bundled into a Reader object. I'm unclear what HibernateSearch
is doing when the getter for the @Field annotation is called, but it would be ideal if it
could use a reader instead of a string
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira