Is it really that useful to have "NoSQL" as an abstraction in the first
place? Is there that much code to share?
On 2018-01-22 21:43, Gary Gregory wrote:
On Mon, Jan 22, 2018 at 12:30 PM, Matt Sicker wrote:
Back when I wrote the initial CassandraAppender implementation, I found the
existing
On Mon, Jan 22, 2018 at 12:30 PM, Matt Sicker wrote:
> Back when I wrote the initial CassandraAppender implementation, I found the
> existing NoSQL interfaces to be too restrictive. I found a similar problem
> long ago when I was experimenting with a DynamoDB appender. Most NoSQL APIs
> I've used
Back when I wrote the initial CassandraAppender implementation, I found the
existing NoSQL interfaces to be too restrictive. I found a similar problem
long ago when I was experimenting with a DynamoDB appender. Most NoSQL APIs
I've used tend to accept a generic Map for documents/records, and it was
Hi All,
The interface org.apache.logging.log4j.core.appender.nosql.NoSqlObject
requires arrays in two methods:
set(String, NoSqlObject[])
set(String, Object[])
For some providers like the new MongoDB driver 3.x provider I am working on
this causes double work. First the log4j NoSQL guts converts
