Hi Balaji: I agree storing audit data in DB is not scalable for long term data.
What would be the path forward for users who are already using DB to store audit data and managing the DB themselves? Adding user@ranger list. Thank you, Vel On 3/8/16, 3:19 PM, "Balaji Ganesan" <bgane...@apache.org> wrote: >All, any concerns with the proposed approach? > >On Wed, Mar 2, 2016 at 12:25 PM, Balaji Ganesan <bgane...@apache.org> >wrote: > >> All, >> >> As I had spoken with some of you offline, I would want to propose >>phasing >> out support for storing audit in database as part of next major release. >> Currently Ranger supports the following methods for storing audit data >> >> 1. Database >> 2. HDFS >> 3. Solr >> 4. Log4j custom appender >> >> The Ranger UI can currently read from both the database and Solr. Moving >> forward, I would propose to remove database support for audit and keep >>only >> Solr as the source of audit for Ranger UI. Users can still send their >>audit >> to HDFS as well as Log4j >> >> The proposal would involve removing audit to DB related configuration as >> well removal of any code related to storing audit in the database. >> >> I wanted to start this thread to discuss this proposal and understand >> concerns/questions. >> >> -Balaji >>
