So, I'll answer your question with some questions: - No matter the data store we use upgrading will take some care, right? - Do we currently depend on a RDBMS anywhere? I want to say that we do in the REST layer already, right? - If we don't use a RDBMs, what's the other option? What are the pros and cons? - Have we considered non-server offline persistent solutions (e.g. https://www.html5rocks.com/en/features/storage)?
On Thu, Feb 1, 2018 at 9:11 AM, Ryan Merriman <merrim...@gmail.com> wrote: > There is currently a PR up for review that allows a user to configure and > save the list of facet fields that appear in the left column of the Alerts > UI: https://github.com/apache/metron/pull/853. The REST layer has ORM > support which means we can store those in a relational database. > > However I'm not 100% sure this is the best place to keep this. As we add > more use cases like this the backing tables in the RDBMS will need to be > managed. This could make upgrading more tedious and error-prone. Is there > are a better way to store this, assuming we can leverage a component that's > already included in our stack? > > Ryan >
