[
https://issues.apache.org/jira/browse/OPENJPA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Lee updated OPENJPA-2017:
--------------------------------
Affects Version/s: 2.2.0
Fix Version/s: (was: 2.2.0)
2.3.0
Pinaki confirmed the committed content was rolled back. Deferred issue to 2.3.0
in preparation for 2.2.0 release.
> Improve batch insertion performance
> -----------------------------------
>
> Key: OPENJPA-2017
> URL: https://issues.apache.org/jira/browse/OPENJPA-2017
> Project: OpenJPA
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 2.1.1, 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.3.0
>
>
> Batch loading data is a common use case. Often, the user would not refer to
> the managed instances after the loading session. However, the runtime, by
> default, spends time in detaching the managed instances by creating/removing
> proxy or retaining state as per the configured options.
> An option should be provided to bypass these operations per persistence
> context basis.
> AutoDetach.NONE could be a possibility. This option will be exclusive i.e. it
> can not be specified with any other AutoDetach options. The NONE option will
> bypass proxying the fields at the transaction boundary or close.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
