You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Andrew Smith (JIRA)" <ji...@apache.org> on 2018/11/07 22:41:00 UTC
[jira] [Updated] (RYA-512) MongoDBRdfConfigurationBuilder creates
new properties keys
[ https://issues.apache.org/jira/browse/RYA-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Smith updated RYA-512:
-----------------------------
Description:
The AbstractMongoDBRdfConfigurationBuilder uses new fields instead of the MongoDBRdfConfiguration fields as property keys.
This creates confusion between fields when switching between Configurations and Properties. There is no reason to have 2 different sets of keys. Refactor the configuration builder to use the configuration key values.
A stop gap solution can be found: *https://github.com/isper3at/incubator-rya/tree/RYA-512_dupFields*
was:
The AbstractMongoDBRdfConfigurationBuilder uses new fields instead of the MongoDBRdfConfiguration fields as property keys.
This creates confusion between fields when switching between Configurations and Properties. There is no reason to have 2 different sets of keys. Refactor the configuration builder to use the configuration key values.
> MongoDBRdfConfigurationBuilder creates new properties keys
> ----------------------------------------------------------
>
> Key: RYA-512
> URL: https://issues.apache.org/jira/browse/RYA-512
> Project: Rya
> Issue Type: Improvement
> Reporter: Andrew Smith
> Priority: Trivial
>
> The AbstractMongoDBRdfConfigurationBuilder uses new fields instead of the MongoDBRdfConfiguration fields as property keys.
> This creates confusion between fields when switching between Configurations and Properties. There is no reason to have 2 different sets of keys. Refactor the configuration builder to use the configuration key values.
> A stop gap solution can be found: *https://github.com/isper3at/incubator-rya/tree/RYA-512_dupFields*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)