openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2017) Improve batch insertion performance
Date Mon, 20 Jun 2011 14:57:47 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051998#comment-13051998
] 

Michael Dick commented on OPENJPA-2017:
---------------------------------------

I've reverted these changes - since I was unable to build trunk (tests failed in openjpa-lib).
I'm not opposed to the changes, but I don't have the leisure to resolve the testcase problem
right now, please re-commit when the test problem is resolved. 

> 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
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message