[
https://issues.apache.org/jira/browse/USERGRID-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046415#comment-14046415
]
George Reyes commented on USERGRID-182:
---------------------------------------
While both configurations were combined into the existing
usergrid-default.properties I was not able to get rid of seemingly duplicate
information. In this case it was cassandra.url, which is used directly by the
hector client. Now we have the additional cassandra.hosts and cassandra.port
that represents the same information , but cannot be removed as that is how the
corepersistence stuff is being used. This can be addressed later by either
creating an interface bean which would force us to write a new calss. Or to
change CorePersistance to use cassandra:url.
> Reconcile 2 config systems (UG and new CP) - go back to just one
> ----------------------------------------------------------------
>
> Key: USERGRID-182
> URL: https://issues.apache.org/jira/browse/USERGRID-182
> Project: Usergrid
> Issue Type: Improvement
> Components: Stack
> Reporter: George Reyes
> Assignee: George Reyes
>
> Currently, Usergrid w/Core Persistence has three configuration files:
> 1) usergrid.properties (also known as usergrid-deployment.properties) - which
> is loaded and "auto wired" big Spring into various classes in Usergrid.
> 2) corepersistence.properties (known as corepersistence-UNIT.properties and
> corepersistence-deploy.properties) - which is loaded by the GuiceyFig system.
> To resolve this issue, we need to have ONE configuration file. This file
> should contain all of the properties that are in the existing usergrid AND
> corepersistence properties files. Where there are new
> corepersistence*.properties properties that replace existing
> usergrid*.properties, we should change the Usergrid code to use the new core
> persistence properties.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
