On Mon, Jun 3, 2019 at 9:18 AM Ralph Goers <[email protected]>
wrote:

> I still don’t understand. According to
> https://www.mongodb.com/blog/post/mongodb-2-6-end-of-life <
> https://www.mongodb.com/blog/post/mongodb-2-6-end-of-life> MongoDB
> reached end-of-life in 2016 and I can’t find the download for it on their
> web site. Why should Log4j 2 3.0 support that?
>

It's not so much an issue of supporting which server but which client.

Gary


>
> Ralph
>
> > On Jun 3, 2019, at 4:03 AM, Gary Gregory <[email protected]> wrote:
> >
> > Indeed. I use Log4j with MongoDB at work. My goal in supporting MongoDB 2
> > and 3 drivers was to allow to match our customer's MongoDB environment,
> > which we are not able to control in all cases. Note that there is no
> Mongo
> > 4 driver to match the server so I can only assume that the version 3
> driver
> > works with server 4.
> >
> > Right, now I have no reason to take the version 2 plugin out in Log4j
> 3.0,
> > especially since it is in a separate plugin.
> >
> > Gary
> >
> > On Sun, Jun 2, 2019 at 6:30 PM Ralph Goers <[email protected]>
> > wrote:
> >
> >> I believe support for Mongo was added by Gary so I am expecting he might
> >> have more input into this.
> >>
> >> Ralph
> >>
> >>> On Jun 2, 2019, at 3:17 PM, Matt Sicker <[email protected]> wrote:
> >>>
> >>> I haven't kept up with MongoDB in quite some time (I'm more interested
> >>> in tech like Cassandra or Postgres), so I wouldn't be able to say
> >>> there. If it's anything like other databases, it might work to simply
> >>> use the oldest compatible driver that supports the necessary features.
> >>>
> >>> On Sun, 2 Jun 2019 at 17:03, Ralph Goers <[email protected]>
> >> wrote:
> >>>>
> >>>> Looking at the MongoDB web site I see release 4 and release 3. We have
> >> support for release 2 and 3. Do we really need support for version 2 in
> the
> >> 3.0 branch? Is anything special required to support MongoDB 4?
> >>>>
> >>>> Ralph
> >>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker <[email protected]>
> >>>
> >>
> >>
> >>
>
>

Reply via email to