[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-964) Create Transforming CacheLoaders that transform 1.x formatted data into 2.x format

[Galder Zamarreno (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-964?page=comments#action_12355390 ] 
            
Galder Zamarreno commented on JBCACHE-964:
------------------------------------------

I'm gonna commit the first part of the work:

- Transforming Cache Loaders implemented and unit tests provided
- Structure created:
[JBC-SOURCE-ROOT]
  + migration
    + src
      + o.j.c.migration.TransformingJDBCCacheLoader
      + o.j.c.migration.TransformingFileCacheLoader
      + o.j.c.migration.LegacyJDBCCacheLoader (JDBCCacheLoaderOld)
    + lib
      + jboss-minimal.jar (from 1.4.x)
    + tests (UT)
      + o.j.c.migration.TransformingCacheLoaderTestBase
      + o.j.c.migration.TransformingFileCacheLoaderTest
      + o.j.c.migration.TransformingJDBCCacheLoaderTest
    + examples
      + cacheloader-migration
        // includes files to run the examples and readme.txt with
        // explanation
        + data
          + filecacheloader-1x.zip
          + jbossdb-1x.zip
        + resources
          + original-fcl-service.xml (sample original FCL XML)
          + original-jdbccl-service.xml (sample original JDBCCL XML)
          + transform-fcl-service.xml (mod of original to transform)
          + transform-jdbccl-service.xml (mod of original to transform)
        + src
          + examples.TransformStore
- build.xml modified to compile, jar, create manifest for migration jar
and also added examples and migration jar to distros.
- example created and tested; it includes readme.txt with details of the 
example and how to run it.

TODO:

- Unit tests for transforming cache loaders need to run from build.xml
- Documentation for transforming cache loaders in users guide, what are 
they, when to use them,...etc.
- Fix http://jira.jboss.com/jira/browse/JBCACHE-877 that occurrs when unzipping
JBossCache-core-2.0.0.BETA2.zip and running the examples. Workaround is to bring trove.jar into its lib.
- Get examples/cacheloader-migration/build.sh working
- Move JDBCCacheLoaderOld to the migration side. It's not that straightforward due to classes in
/src having dependencies on it. Needs further study.

> Create Transforming CacheLoaders that transform 1.x formatted data into 2.x format
> ----------------------------------------------------------------------------------
>
>                 Key: JBCACHE-964
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-964
>             Project: JBoss Cache
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Cache loaders
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>             Fix For: 2.0.0.GA, 2.0.0.BETA2
>
>
> Customers that want to use JBossCache 2.x might be reluctant to 
> migrate their data from one format to the other. I can see how an 
> existing customer might think this is a proper pain in the ass, 
> independent of the benefits, and might reduce adoption among them.
> We want to remove barriers upgrading, but at the same time, we want 
> new customer to use new marshalling, so I'd actually implement the 
> possibility to use 1.x marshalling which is plan java serialization at 
> the CacheLoader level. This could easily achieved adding a property to 
> the <properties> section.
> The default in 2.x should be to use VAM and only people who are 
> resilient to change their existing stores to VAM should use the 1.x 
> option, which would need explicitly definition.
> This option also makes it easier for migration purpouses as customers 
> should be able to start two cache instances with different cache loader 
> marshalling method set. They could then loop through the first one using 
> get operations and call put in the second instance.
> Just note that this does not apply to the marshalling done at 
> replication level as there's no hard data that needs migrating.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira