[jira] [Updated] (RYA-138) Support the ability to fully re-hydrate AccumuloRdfConfiguration from Configuration

["Puja Valiyil (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RYA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Puja Valiyil  updated RYA-138:
------------------------------
    Priority: Critical  (was: Minor)

> Support the ability to fully re-hydrate AccumuloRdfConfiguration from Configuration
> -----------------------------------------------------------------------------------
>
>                 Key: RYA-138
>                 URL: https://issues.apache.org/jira/browse/RYA-138
>             Project: Rya
>          Issue Type: Bug
>          Components: dao
>    Affects Versions: 3.2.10, 3.2.9
>            Reporter: Jamie Johnson
>            Assignee: David W. Lotts
>            Priority: Critical
>
> Currently if the AccumuloRdfConfiguration is written to XML and passed into the constructor of AccumuloRdfConfiguration, the table prefix is carried through, but the table layout strategy defaults to the PrefixTableLayoutStrategy with the default prefix.  A simple example demonstrates the issue
> {code}
> AccumuloRdfConfiguration initial = new AccumuloRdfConfiguration();
> initial.setTablePrefix("rya2_");
> ByteArrayOutputStream stream = new ByteArrayOutputStream();
> initial.writeXml(stream);
> AccumuloRdfConfiguration second = new AccumuloRdfConfiguration();
> second.addResource(new ByteArrayInputStream(stream.toByteArray()));
> System.out.println(initial.getTablePrefix().equals(second.getTablePrefix()));
> System.out.println(initial.getTableLayoutStrategy().getSpo().equals(second.getTableLayoutStrategy().getSpo()));
> {code}
> This primarily seems to be related to the fact that TableLayoutStrategy isn't captured in the configuration.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)