You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Maxime Chassagneux <mc...@apache.org> on 2017/07/19 09:55:12 UTC
MongoDB driver
Hi,
The JMeter bundle still include a mongoDB java driver ( version 2.11.3 )
which is really old and doesn't work with all authentication
By example :
javax.script.ScriptException: java.lang.IllegalArgumentException:
Unsupported authMechanism: SCRAM-SHA-1
As mongoDB is deprecated in JMeter, my question is : Should we keep this
librairie or update it to the lastest version ?
Thanks for ur feedback.
Re: MongoDB driver
Posted by Emilian Bold <em...@gmail.com>.
I would vote to remove it entirely then from the codebase. A 3rd party
plugin could be created if people need it.
Do you want me to submit a patch?
--emi
On Thu, Jul 20, 2017 at 10:15 PM, Philippe Mouawad
<ph...@gmail.com> wrote:
> Hello,
> The decision to deprecate was motivated by many reasons:
>
> - Very low feedback both on SO, bugzilla and user mailing list
> - No mention at all from MongoDB which seems to have its own tool
> - The effort to upgrade (lot of deprecations) + the fact that an async
> driver was released and that might be a better choice
> - The fact that we need to make choices based on priorities :-) JDBC
> sampler addresses many DB, MongoDB addresses 1 Product. I think it was a
> mistake to add it (my mistake :-) )
>
> Regards
>
> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com> wrote:
>
>> When the decision was made to deprecate no one was volunteering to update
>> it. If we have volunteers then the volunteer(s) can update the driver.
>> Mongo becomes undeprecated.
>>
>> Sent from my iPhone
>>
>> > On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <ra...@gmail.com>
>> wrote:
>> >
>> > Issues, question in stackoverflow...
>> >
>> > 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
>> >
>> >> Out of curiosity, how do you measure usage? Based on issues opened?
>> >>
>> >> --emi
>> >>
>> >>
>> >> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
>> >> <ra...@gmail.com> wrote:
>> >>> Hi,
>> >>>
>> >>> If I remember it's because we have few time to update it and because
>> it's
>> >>> not very used
>> >>>
>> >>> Antonio
>> >>>
>> >>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>> >>>
>> >>>> I don't know why the MongoDB protocol got deprecated, but the next
>> >>>> step would be removal of the classes not updating libraries.
>> >>>>
>> >>>> --emi
>> >>>>
>> >>>>
>> >>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>> >>>> <mc...@apache.org> wrote:
>> >>>>> Hi,
>> >>>>>
>> >>>>> The JMeter bundle still include a mongoDB java driver ( version
>> >> 2.11.3 )
>> >>>>> which is really old and doesn't work with all authentication
>> >>>>>
>> >>>>> By example :
>> >>>>>
>> >>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
>> >>>>> Unsupported authMechanism: SCRAM-SHA-1
>> >>>>>
>> >>>>>
>> >>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
>> >> this
>> >>>>> librairie or update it to the lastest version ?
>> >>>>>
>> >>>>> Thanks for ur feedback.
>> >>>>
>> >>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: MongoDB driver
Posted by Vladimir Sitnikov <si...@gmail.com>.
>The driver has broken source compatibility.
ok. Then we drop it.
Vladimir
Re: MongoDB driver
Posted by UBIK LOAD PACK Support <su...@ubikloadpack.com>.
Hello,
I created a branch to remove mongodb.
It still has issues related to loading old plans having it.
I'll stop work on it for now, in case somebody wants to fix it, it's ok by
me.
Regards
On Sun, Oct 6, 2019 at 12:48 PM Felix Schumacher <
felix.schumacher@internetallee.de> wrote:
>
> Am 04.10.19 um 21:27 schrieb Philippe Mouawad:
> > Hello Vladimir,
> > No the gradle plugin won't solve this.
> > The driver has broken source compatibility.
> >
> > Also we exposed DB object and now it has been replaced by MongoDatabase.
> > The authentication is also different which means we need to rewrite
> nearly
> > everything.
> > And finally, the Mongo elements are not even visible today, so removing
> > them has no impact for me.
> >
> > So let's just remove the code no ?
>
> The driver has been marked deprecated for at least one version of JMeter
> (marked on Dec 27 2015).
>
> It will not work on newer MongoDB versions (at least that is what I
> heard, haven't tried it).
>
> So it is probably time to remove it.
>
> On the other hand, the versioning scheme would require a new major
> version for breaking changes such as dropping a sampler, would not it?
>
> Felix
>
> > Regards
> >
> > On Fri, Oct 4, 2019 at 7:30 PM Vladimir Sitnikov <
> > sitnikov.vladimir@gmail.com> wrote:
> >
> >>> It’s not about size, it’s about quality and « «uptodateness »
> >> This would partially be solved with
> >> https://github.com/ben-manes/gradle-versions-plugin
> >> That is a Gradle plugin that discovers available updates on demand.
> >> What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0?
> >>
> >>> But even with it, we should drop MongoDB
> >> Does it really hurt?
> >> The jar is small. The UI is small. It never fails CI.
> >>
> >> It is not like I use Mongo every day.
> >> I just mean that there might be chicken-and-egg problem: no Mongo
> sampler
> >> -> JMeter users don't even try testing MongoDB (or storing temporary
> data
> >> in MongoDB instead of files).
> >>
> >>> let’s make a POC of it.
> >> After 5.2?
> >>
> >> Vladimir
> >>
> >
>
--
Regards
Ubik Load Pack <http://ubikloadpack.com> Team
Follow us on Twitter <http://twitter.com/ubikloadpack>
Cordialement
L'équipe Ubik Load Pack <http://ubikloadpack.com>
Suivez-nous sur Twitter <http://twitter.com/ubikloadpack>
Re: MongoDB driver
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 04.10.19 um 21:27 schrieb Philippe Mouawad:
> Hello Vladimir,
> No the gradle plugin won't solve this.
> The driver has broken source compatibility.
>
> Also we exposed DB object and now it has been replaced by MongoDatabase.
> The authentication is also different which means we need to rewrite nearly
> everything.
> And finally, the Mongo elements are not even visible today, so removing
> them has no impact for me.
>
> So let's just remove the code no ?
The driver has been marked deprecated for at least one version of JMeter
(marked on Dec 27 2015).
It will not work on newer MongoDB versions (at least that is what I
heard, haven't tried it).
So it is probably time to remove it.
On the other hand, the versioning scheme would require a new major
version for breaking changes such as dropping a sampler, would not it?
Felix
> Regards
>
> On Fri, Oct 4, 2019 at 7:30 PM Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com> wrote:
>
>>> It’s not about size, it’s about quality and « «uptodateness »
>> This would partially be solved with
>> https://github.com/ben-manes/gradle-versions-plugin
>> That is a Gradle plugin that discovers available updates on demand.
>> What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0?
>>
>>> But even with it, we should drop MongoDB
>> Does it really hurt?
>> The jar is small. The UI is small. It never fails CI.
>>
>> It is not like I use Mongo every day.
>> I just mean that there might be chicken-and-egg problem: no Mongo sampler
>> -> JMeter users don't even try testing MongoDB (or storing temporary data
>> in MongoDB instead of files).
>>
>>> let’s make a POC of it.
>> After 5.2?
>>
>> Vladimir
>>
>
Re: MongoDB driver
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello Vladimir,
No the gradle plugin won't solve this.
The driver has broken source compatibility.
Also we exposed DB object and now it has been replaced by MongoDatabase.
The authentication is also different which means we need to rewrite nearly
everything.
And finally, the Mongo elements are not even visible today, so removing
them has no impact for me.
So let's just remove the code no ?
Regards
On Fri, Oct 4, 2019 at 7:30 PM Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> wrote:
> >It’s not about size, it’s about quality and « «uptodateness »
>
> This would partially be solved with
> https://github.com/ben-manes/gradle-versions-plugin
> That is a Gradle plugin that discovers available updates on demand.
> What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0?
>
> >But even with it, we should drop MongoDB
>
> Does it really hurt?
> The jar is small. The UI is small. It never fails CI.
>
> It is not like I use Mongo every day.
> I just mean that there might be chicken-and-egg problem: no Mongo sampler
> -> JMeter users don't even try testing MongoDB (or storing temporary data
> in MongoDB instead of files).
>
> >let’s make a POC of it.
>
> After 5.2?
>
> Vladimir
>
--
Cordialement.
Philippe Mouawad.
Re: MongoDB driver
Posted by Vladimir Sitnikov <si...@gmail.com>.
Igor>Hello, team! Last year there was a PR in which I made an attempt to
update
Igor>There were 8 failed unit tests left
It turns out JMeter codebase never had MongoDB-specific tests.
If you want to update/re-implement MongoDB adapter, then it would probably
be easier now (thanks to Gradle).
On top of that, you might use TestContainers for integration tests.
Vladimir
Re: MongoDB driver
Posted by Igor Sasovets <is...@gmail.com>.
Hello, team! Last year there was a PR in which I made an attempt to update
mongo-java-driver. There were 8 failed unit tests left but I didn't manage
to fix them without a help from the core development team.
https://github.com/apache/jmeter/pull/390
We can use it during upgrade.
Sincerely,
Ihor
Пт, 4 жовт. 2019 20:30 користувач Vladimir Sitnikov <
sitnikov.vladimir@gmail.com> пише:
> >It’s not about size, it’s about quality and « «uptodateness »
>
> This would partially be solved with
> https://github.com/ben-manes/gradle-versions-plugin
> That is a Gradle plugin that discovers available updates on demand.
> What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0?
>
> >But even with it, we should drop MongoDB
>
> Does it really hurt?
> The jar is small. The UI is small. It never fails CI.
>
> It is not like I use Mongo every day.
> I just mean that there might be chicken-and-egg problem: no Mongo sampler
> -> JMeter users don't even try testing MongoDB (or storing temporary data
> in MongoDB instead of files).
>
> >let’s make a POC of it.
>
> After 5.2?
>
> Vladimir
>
Re: MongoDB driver
Posted by Vladimir Sitnikov <si...@gmail.com>.
>It’s not about size, it’s about quality and « «uptodateness »
This would partially be solved with
https://github.com/ben-manes/gradle-versions-plugin
That is a Gradle plugin that discovers available updates on demand.
What if we upgrade to mongo-java-driver 2.11.3 to 3.11.0?
>But even with it, we should drop MongoDB
Does it really hurt?
The jar is small. The UI is small. It never fails CI.
It is not like I use Mongo every day.
I just mean that there might be chicken-and-egg problem: no Mongo sampler
-> JMeter users don't even try testing MongoDB (or storing temporary data
in MongoDB instead of files).
>let’s make a POC of it.
After 5.2?
Vladimir
Re: MongoDB driver
Posted by Philippe Mouawad <pm...@apache.org>.
On Friday, October 4, 2019, Vladimir Sitnikov <si...@gmail.com>
wrote:
> >I propose to drop it for this release 5.2
>
> This is interesting.
> Do we need Bolt then?
This has been contributed by members of a company tightly related to Neo4j.
MongoDB was not.
I expected MongoDB to be supported by the company
It brings people to JMeter and Graph a field that is expanding.
We try and when something is not successful we drop it, that’s ok for me.
> Who will maintain it?
We’ll see .
I expect initial contributors, I’ll also try to
>
>
> >Possible benefits for users is cleaner UI menus
>
> What if we add a "import-like" feature to the thread group?
> In other words, what if ThreadGroup (or it's ImportConfigurator) includes a
> set of checkboxes:
> "I want Mongo in this threadgroup"
> "I want JSR223 in this threadgroup"
>
> Then context menus might show only "already imported" elements, to it would
> be very small.
> "not yet imported" could be either completely hidden, or put into
> "unimported yet" sub-menu.
>
> The user could configure different imports for different thread groups.
> Menus are small, and everybody's happy.
let’s make a POC of it.
But even with it, we should drop MongoDB
>
> As a bonus, we could even add/remove UI elements from ThreadGroup (or
> whatever element) when the set of imports change.
> For instance, if the user imports "http testing", then we could show "clear
> caches on each iteration" feature to the ThreadGroup / LoopController
> configuration.
>
> mongo-java-driver-2.11.3.jar is 400KiB.
> It is 10 times smaller than Saxon-HE-9.9.1-5.jar which is ~5.5M
> It is 4 times smaller than commons-math3-3.6.1.jar which is 2.2M
> and so on.
>
> We could try reducing the initial download size by downloading dependencies
> from MavenCentral-like repositories, however, that is a different story.
> The removal of Mongo does not reduce the download.
It’s not about size, it’s about quality and « «uptodateness »
And also about number of elements but your proposal would help
>
> Vladimir
>
Re: MongoDB driver
Posted by Vladimir Sitnikov <si...@gmail.com>.
>I propose to drop it for this release 5.2
This is interesting.
Do we need Bolt then?
Who will maintain it?
>Possible benefits for users is cleaner UI menus
What if we add a "import-like" feature to the thread group?
In other words, what if ThreadGroup (or it's ImportConfigurator) includes a
set of checkboxes:
"I want Mongo in this threadgroup"
"I want JSR223 in this threadgroup"
Then context menus might show only "already imported" elements, to it would
be very small.
"not yet imported" could be either completely hidden, or put into
"unimported yet" sub-menu.
The user could configure different imports for different thread groups.
Menus are small, and everybody's happy.
As a bonus, we could even add/remove UI elements from ThreadGroup (or
whatever element) when the set of imports change.
For instance, if the user imports "http testing", then we could show "clear
caches on each iteration" feature to the ThreadGroup / LoopController
configuration.
mongo-java-driver-2.11.3.jar is 400KiB.
It is 10 times smaller than Saxon-HE-9.9.1-5.jar which is ~5.5M
It is 4 times smaller than commons-math3-3.6.1.jar which is 2.2M
and so on.
We could try reducing the initial download size by downloading dependencies
from MavenCentral-like repositories, however, that is a different story.
The removal of Mongo does not reduce the download.
Vladimir
Re: MongoDB driver
Posted by Philippe Mouawad <pm...@apache.org>.
Hello,
I propose to drop it for this release 5.2
If anybody wants it:
- he can use a previous jar
- or extract it and maintain it
It is now outdated, without tests so it hurts JMeter image and quality
Regards
On Sunday, July 23, 2017, Andrey Pokhilko <ap...@ya.ru> wrote:
> No irony at all, I am serious. Any effort is valuable for the project.
>
> Andrey Pokhilko
>
> On 07/23/2017 06:19 PM, Philippe Mouawad wrote:
> > On Sun, Jul 23, 2017 at 5:09 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
> >
> >> Hi Philippe,
> >>
> >> My question is not about dropping, it is about usage level we know and
> >> _possible deprecating_ based on that. Maintaining code that is barely
> >> used could be unnecessary burden for the project.
> >>
> > I see it as a burden when the underlying protocol changes and we need to
> > update it frequently while not sure it is useful.
> > In the case of the protocols mentioned, it looks to me that those
> protocols
> > are now very stable and only require little work.
> >
> > Besides they are potentially useful within Automation of a Test Plan:
> >
> > - LDAP => Create a CSV from a set of users having some LDAP attribute
> or
> > belonging to a group
> > - FTP => Getting or uploading some files
> > - MAIL / SMTP => Sent a mail based on test results or test state...
> >
> > Having those protocols within JMeter is interesting IMO.
> >
> >
> >> For example I have feeling that LDAP as protocol should be rarely used
> >> in JMeter just because protocol itself is declining (my assumption is
> >> based on things like
> >> https://trends.google.ru/trends/explore?date=all&q=ldap,oauth,openid or
> >> https://www.quora.com/Why-isnt-LDAP-dead-yet)
> >>
> >> From your comments I understood that you see interest on SO for all
> >> modules except LDAP. This matches my intuitive expectation.
> >>
> > I am not even sure of that. We had recently bug reports on Ldap.
> > I already used it within my work.
> > I was just mentioning the sources for "usage and popularity"
> >
> >
> >> Thanks for your analysis on usage of components, it's valuable
> >> information for all of us.
> >>
> > I don't pretend to have such a great analysis you are crediting me of
> > ironically or not :-)
> >
> > Clearly it would have been great to know usage based on reporting as
> > Emilian proposed.
> > It would have also been great if the plugins manager was part of JMeter
> > core and there was an Apache repository for Core plugins which would
> maybe
> > make it possible to distribute a small bundle.
> > But it's not the case.
> >
> >
> >> Andrey Pokhilko
> >>
> >> On 07/23/2017 05:34 PM, Philippe Mouawad wrote:
> >>> Hello Andrei,
> >>> I don't see why we should drop elements that are not deprecated and are
> >>> used based on bug reports, SO questions.
> >>>
> >>> MongoDB is not in that case as we can consider we are not maintaining
> it
> >>> and it is deprecated since many months.
> >>>
> >>>
> >>> Regards
> >>>
> >>> On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
> >>>
> >>>> Based on these reasons, don't we see also worth deprecating:
> >>>>
> >>>> 1. Mail/SMTP components
> >>>>
> >>> AKAIK, they are not deprecated. And are useful, I saw several questions
> >> on
> >>> SO
> >>>
> >>>> 2. LDAP components
> >>>>
> >>> AKAIK, they are not deprecated.
> >>>
> >>>> 3. FTP
> >>>>
> >>> AKAIK, they are not deprecated. And are useful, I saw several questions
> >> on
> >>> SO
> >>>
> >>>> 4. Any of other distribution bundle modules (junit/tcp etc)
> >>>>
> >>> AKAIK, they are not deprecated, neither JUnit nor TCP which is used a
> lot
> >>> from SO questions..
> >>>
> >>>
> >>>
> >>>> Possible benefits for users is cleaner UI menus, smaller distribution
> >>>> archive size, faster JMeter startup. Do we have estimations of
> >>>> importance of those parts of JMeter?
> >>>>
> >>>> Andrey Pokhilko
> >>>>
> >>>> On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
> >>>>> Hello,
> >>>>> The decision to deprecate was motivated by many reasons:
> >>>>>
> >>>>> - Very low feedback both on SO, bugzilla and user mailing list
> >>>>> - No mention at all from MongoDB which seems to have its own tool
> >>>>> - The effort to upgrade (lot of deprecations) + the fact that an
> >> async
> >>>>> driver was released and that might be a better choice
> >>>>> - The fact that we need to make choices based on priorities :-)
> JDBC
> >>>>> sampler addresses many DB, MongoDB addresses 1 Product. I think it
> >>>> was a
> >>>>> mistake to add it (my mistake :-) )
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com>
> >>>> wrote:
> >>>>>> When the decision was made to deprecate no one was volunteering to
> >>>> update
> >>>>>> it. If we have volunteers then the volunteer(s) can update the
> driver.
> >>>>>> Mongo becomes undeprecated.
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <
> >>>> ra0077@gmail.com>
> >>>>>> wrote:
> >>>>>>> Issues, question in stackoverflow...
> >>>>>>>
> >>>>>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>>>>>
> >>>>>>>> Out of curiosity, how do you measure usage? Based on issues
> opened?
> >>>>>>>>
> >>>>>>>> --emi
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
> >>>>>>>> <ra...@gmail.com> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> If I remember it's because we have few time to update it and
> >> because
> >>>>>> it's
> >>>>>>>>> not very used
> >>>>>>>>>
> >>>>>>>>> Antonio
> >>>>>>>>>
> >>>>>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <emilian.bold@gmail.com
> >:
> >>>>>>>>>
> >>>>>>>>>> I don't know why the MongoDB protocol got deprecated, but the
> next
> >>>>>>>>>> step would be removal of the classes not updating libraries.
> >>>>>>>>>>
> >>>>>>>>>> --emi
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> >>>>>>>>>> <mc...@apache.org> wrote:
> >>>>>>>>>>> Hi,
> >>>>>>>>>>>
> >>>>>>>>>>> The JMeter bundle still include a mongoDB java driver ( version
> >>>>>>>> 2.11.3 )
> >>>>>>>>>>> which is really old and doesn't work with all authentication
> >>>>>>>>>>>
> >>>>>>>>>>> By example :
> >>>>>>>>>>>
> >>>>>>>>>>> javax.script.ScriptException: java.lang.
> >> IllegalArgumentException:
> >>>>>>>>>>> Unsupported authMechanism: SCRAM-SHA-1
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we
> >> keep
> >>>>>>>> this
> >>>>>>>>>>> librairie or update it to the lastest version ?
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks for ur feedback.
> >>
> >
>
>
Re: MongoDB driver
Posted by Andrey Pokhilko <ap...@ya.ru>.
No irony at all, I am serious. Any effort is valuable for the project.
Andrey Pokhilko
On 07/23/2017 06:19 PM, Philippe Mouawad wrote:
> On Sun, Jul 23, 2017 at 5:09 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
>
>> Hi Philippe,
>>
>> My question is not about dropping, it is about usage level we know and
>> _possible deprecating_ based on that. Maintaining code that is barely
>> used could be unnecessary burden for the project.
>>
> I see it as a burden when the underlying protocol changes and we need to
> update it frequently while not sure it is useful.
> In the case of the protocols mentioned, it looks to me that those protocols
> are now very stable and only require little work.
>
> Besides they are potentially useful within Automation of a Test Plan:
>
> - LDAP => Create a CSV from a set of users having some LDAP attribute or
> belonging to a group
> - FTP => Getting or uploading some files
> - MAIL / SMTP => Sent a mail based on test results or test state...
>
> Having those protocols within JMeter is interesting IMO.
>
>
>> For example I have feeling that LDAP as protocol should be rarely used
>> in JMeter just because protocol itself is declining (my assumption is
>> based on things like
>> https://trends.google.ru/trends/explore?date=all&q=ldap,oauth,openid or
>> https://www.quora.com/Why-isnt-LDAP-dead-yet)
>>
>> From your comments I understood that you see interest on SO for all
>> modules except LDAP. This matches my intuitive expectation.
>>
> I am not even sure of that. We had recently bug reports on Ldap.
> I already used it within my work.
> I was just mentioning the sources for "usage and popularity"
>
>
>> Thanks for your analysis on usage of components, it's valuable
>> information for all of us.
>>
> I don't pretend to have such a great analysis you are crediting me of
> ironically or not :-)
>
> Clearly it would have been great to know usage based on reporting as
> Emilian proposed.
> It would have also been great if the plugins manager was part of JMeter
> core and there was an Apache repository for Core plugins which would maybe
> make it possible to distribute a small bundle.
> But it's not the case.
>
>
>> Andrey Pokhilko
>>
>> On 07/23/2017 05:34 PM, Philippe Mouawad wrote:
>>> Hello Andrei,
>>> I don't see why we should drop elements that are not deprecated and are
>>> used based on bug reports, SO questions.
>>>
>>> MongoDB is not in that case as we can consider we are not maintaining it
>>> and it is deprecated since many months.
>>>
>>>
>>> Regards
>>>
>>> On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
>>>
>>>> Based on these reasons, don't we see also worth deprecating:
>>>>
>>>> 1. Mail/SMTP components
>>>>
>>> AKAIK, they are not deprecated. And are useful, I saw several questions
>> on
>>> SO
>>>
>>>> 2. LDAP components
>>>>
>>> AKAIK, they are not deprecated.
>>>
>>>> 3. FTP
>>>>
>>> AKAIK, they are not deprecated. And are useful, I saw several questions
>> on
>>> SO
>>>
>>>> 4. Any of other distribution bundle modules (junit/tcp etc)
>>>>
>>> AKAIK, they are not deprecated, neither JUnit nor TCP which is used a lot
>>> from SO questions..
>>>
>>>
>>>
>>>> Possible benefits for users is cleaner UI menus, smaller distribution
>>>> archive size, faster JMeter startup. Do we have estimations of
>>>> importance of those parts of JMeter?
>>>>
>>>> Andrey Pokhilko
>>>>
>>>> On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
>>>>> Hello,
>>>>> The decision to deprecate was motivated by many reasons:
>>>>>
>>>>> - Very low feedback both on SO, bugzilla and user mailing list
>>>>> - No mention at all from MongoDB which seems to have its own tool
>>>>> - The effort to upgrade (lot of deprecations) + the fact that an
>> async
>>>>> driver was released and that might be a better choice
>>>>> - The fact that we need to make choices based on priorities :-) JDBC
>>>>> sampler addresses many DB, MongoDB addresses 1 Product. I think it
>>>> was a
>>>>> mistake to add it (my mistake :-) )
>>>>>
>>>>> Regards
>>>>>
>>>>> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com>
>>>> wrote:
>>>>>> When the decision was made to deprecate no one was volunteering to
>>>> update
>>>>>> it. If we have volunteers then the volunteer(s) can update the driver.
>>>>>> Mongo becomes undeprecated.
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <
>>>> ra0077@gmail.com>
>>>>>> wrote:
>>>>>>> Issues, question in stackoverflow...
>>>>>>>
>>>>>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>>>>>
>>>>>>>> Out of curiosity, how do you measure usage? Based on issues opened?
>>>>>>>>
>>>>>>>> --emi
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
>>>>>>>> <ra...@gmail.com> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> If I remember it's because we have few time to update it and
>> because
>>>>>> it's
>>>>>>>>> not very used
>>>>>>>>>
>>>>>>>>> Antonio
>>>>>>>>>
>>>>>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>>>>>>>
>>>>>>>>>> I don't know why the MongoDB protocol got deprecated, but the next
>>>>>>>>>> step would be removal of the classes not updating libraries.
>>>>>>>>>>
>>>>>>>>>> --emi
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>>>>>>>>>> <mc...@apache.org> wrote:
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> The JMeter bundle still include a mongoDB java driver ( version
>>>>>>>> 2.11.3 )
>>>>>>>>>>> which is really old and doesn't work with all authentication
>>>>>>>>>>>
>>>>>>>>>>> By example :
>>>>>>>>>>>
>>>>>>>>>>> javax.script.ScriptException: java.lang.
>> IllegalArgumentException:
>>>>>>>>>>> Unsupported authMechanism: SCRAM-SHA-1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we
>> keep
>>>>>>>> this
>>>>>>>>>>> librairie or update it to the lastest version ?
>>>>>>>>>>>
>>>>>>>>>>> Thanks for ur feedback.
>>
>
Re: MongoDB driver
Posted by Philippe Mouawad <ph...@gmail.com>.
On Sun, Jul 23, 2017 at 5:09 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
> Hi Philippe,
>
> My question is not about dropping, it is about usage level we know and
> _possible deprecating_ based on that. Maintaining code that is barely
> used could be unnecessary burden for the project.
>
I see it as a burden when the underlying protocol changes and we need to
update it frequently while not sure it is useful.
In the case of the protocols mentioned, it looks to me that those protocols
are now very stable and only require little work.
Besides they are potentially useful within Automation of a Test Plan:
- LDAP => Create a CSV from a set of users having some LDAP attribute or
belonging to a group
- FTP => Getting or uploading some files
- MAIL / SMTP => Sent a mail based on test results or test state...
Having those protocols within JMeter is interesting IMO.
> For example I have feeling that LDAP as protocol should be rarely used
> in JMeter just because protocol itself is declining (my assumption is
> based on things like
> https://trends.google.ru/trends/explore?date=all&q=ldap,oauth,openid or
> https://www.quora.com/Why-isnt-LDAP-dead-yet)
>
> From your comments I understood that you see interest on SO for all
> modules except LDAP. This matches my intuitive expectation.
>
I am not even sure of that. We had recently bug reports on Ldap.
I already used it within my work.
I was just mentioning the sources for "usage and popularity"
>
> Thanks for your analysis on usage of components, it's valuable
> information for all of us.
>
I don't pretend to have such a great analysis you are crediting me of
ironically or not :-)
Clearly it would have been great to know usage based on reporting as
Emilian proposed.
It would have also been great if the plugins manager was part of JMeter
core and there was an Apache repository for Core plugins which would maybe
make it possible to distribute a small bundle.
But it's not the case.
>
> Andrey Pokhilko
>
> On 07/23/2017 05:34 PM, Philippe Mouawad wrote:
> > Hello Andrei,
> > I don't see why we should drop elements that are not deprecated and are
> > used based on bug reports, SO questions.
> >
> > MongoDB is not in that case as we can consider we are not maintaining it
> > and it is deprecated since many months.
> >
> >
> > Regards
> >
> > On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
> >
> >> Based on these reasons, don't we see also worth deprecating:
> >>
> >> 1. Mail/SMTP components
> >>
> > AKAIK, they are not deprecated. And are useful, I saw several questions
> on
> > SO
> >
> >> 2. LDAP components
> >>
> > AKAIK, they are not deprecated.
> >
> >> 3. FTP
> >>
> > AKAIK, they are not deprecated. And are useful, I saw several questions
> on
> > SO
> >
> >> 4. Any of other distribution bundle modules (junit/tcp etc)
> >>
> > AKAIK, they are not deprecated, neither JUnit nor TCP which is used a lot
> > from SO questions..
> >
> >
> >
> >> Possible benefits for users is cleaner UI menus, smaller distribution
> >> archive size, faster JMeter startup. Do we have estimations of
> >> importance of those parts of JMeter?
> >>
> >> Andrey Pokhilko
> >>
> >> On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
> >>> Hello,
> >>> The decision to deprecate was motivated by many reasons:
> >>>
> >>> - Very low feedback both on SO, bugzilla and user mailing list
> >>> - No mention at all from MongoDB which seems to have its own tool
> >>> - The effort to upgrade (lot of deprecations) + the fact that an
> async
> >>> driver was released and that might be a better choice
> >>> - The fact that we need to make choices based on priorities :-) JDBC
> >>> sampler addresses many DB, MongoDB addresses 1 Product. I think it
> >> was a
> >>> mistake to add it (my mistake :-) )
> >>>
> >>> Regards
> >>>
> >>> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com>
> >> wrote:
> >>>> When the decision was made to deprecate no one was volunteering to
> >> update
> >>>> it. If we have volunteers then the volunteer(s) can update the driver.
> >>>> Mongo becomes undeprecated.
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <
> >> ra0077@gmail.com>
> >>>> wrote:
> >>>>> Issues, question in stackoverflow...
> >>>>>
> >>>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>>>
> >>>>>> Out of curiosity, how do you measure usage? Based on issues opened?
> >>>>>>
> >>>>>> --emi
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
> >>>>>> <ra...@gmail.com> wrote:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> If I remember it's because we have few time to update it and
> because
> >>>> it's
> >>>>>>> not very used
> >>>>>>>
> >>>>>>> Antonio
> >>>>>>>
> >>>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>>>>>
> >>>>>>>> I don't know why the MongoDB protocol got deprecated, but the next
> >>>>>>>> step would be removal of the classes not updating libraries.
> >>>>>>>>
> >>>>>>>> --emi
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> >>>>>>>> <mc...@apache.org> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>>
> >>>>>>>>> The JMeter bundle still include a mongoDB java driver ( version
> >>>>>> 2.11.3 )
> >>>>>>>>> which is really old and doesn't work with all authentication
> >>>>>>>>>
> >>>>>>>>> By example :
> >>>>>>>>>
> >>>>>>>>> javax.script.ScriptException: java.lang.
> IllegalArgumentException:
> >>>>>>>>> Unsupported authMechanism: SCRAM-SHA-1
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we
> keep
> >>>>>> this
> >>>>>>>>> librairie or update it to the lastest version ?
> >>>>>>>>>
> >>>>>>>>> Thanks for ur feedback.
> >>
> >
>
>
--
Cordialement.
Philippe Mouawad.
Re: MongoDB driver
Posted by Andrey Pokhilko <ap...@ya.ru>.
Hi Philippe,
My question is not about dropping, it is about usage level we know and
_possible deprecating_ based on that. Maintaining code that is barely
used could be unnecessary burden for the project.
For example I have feeling that LDAP as protocol should be rarely used
in JMeter just because protocol itself is declining (my assumption is
based on things like
https://trends.google.ru/trends/explore?date=all&q=ldap,oauth,openid or
https://www.quora.com/Why-isnt-LDAP-dead-yet)
From your comments I understood that you see interest on SO for all
modules except LDAP. This matches my intuitive expectation.
Thanks for your analysis on usage of components, it's valuable
information for all of us.
Andrey Pokhilko
On 07/23/2017 05:34 PM, Philippe Mouawad wrote:
> Hello Andrei,
> I don't see why we should drop elements that are not deprecated and are
> used based on bug reports, SO questions.
>
> MongoDB is not in that case as we can consider we are not maintaining it
> and it is deprecated since many months.
>
>
> Regards
>
> On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
>
>> Based on these reasons, don't we see also worth deprecating:
>>
>> 1. Mail/SMTP components
>>
> AKAIK, they are not deprecated. And are useful, I saw several questions on
> SO
>
>> 2. LDAP components
>>
> AKAIK, they are not deprecated.
>
>> 3. FTP
>>
> AKAIK, they are not deprecated. And are useful, I saw several questions on
> SO
>
>> 4. Any of other distribution bundle modules (junit/tcp etc)
>>
> AKAIK, they are not deprecated, neither JUnit nor TCP which is used a lot
> from SO questions..
>
>
>
>> Possible benefits for users is cleaner UI menus, smaller distribution
>> archive size, faster JMeter startup. Do we have estimations of
>> importance of those parts of JMeter?
>>
>> Andrey Pokhilko
>>
>> On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
>>> Hello,
>>> The decision to deprecate was motivated by many reasons:
>>>
>>> - Very low feedback both on SO, bugzilla and user mailing list
>>> - No mention at all from MongoDB which seems to have its own tool
>>> - The effort to upgrade (lot of deprecations) + the fact that an async
>>> driver was released and that might be a better choice
>>> - The fact that we need to make choices based on priorities :-) JDBC
>>> sampler addresses many DB, MongoDB addresses 1 Product. I think it
>> was a
>>> mistake to add it (my mistake :-) )
>>>
>>> Regards
>>>
>>> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com>
>> wrote:
>>>> When the decision was made to deprecate no one was volunteering to
>> update
>>>> it. If we have volunteers then the volunteer(s) can update the driver.
>>>> Mongo becomes undeprecated.
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <
>> ra0077@gmail.com>
>>>> wrote:
>>>>> Issues, question in stackoverflow...
>>>>>
>>>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>>>
>>>>>> Out of curiosity, how do you measure usage? Based on issues opened?
>>>>>>
>>>>>> --emi
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
>>>>>> <ra...@gmail.com> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> If I remember it's because we have few time to update it and because
>>>> it's
>>>>>>> not very used
>>>>>>>
>>>>>>> Antonio
>>>>>>>
>>>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>>>>>
>>>>>>>> I don't know why the MongoDB protocol got deprecated, but the next
>>>>>>>> step would be removal of the classes not updating libraries.
>>>>>>>>
>>>>>>>> --emi
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>>>>>>>> <mc...@apache.org> wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> The JMeter bundle still include a mongoDB java driver ( version
>>>>>> 2.11.3 )
>>>>>>>>> which is really old and doesn't work with all authentication
>>>>>>>>>
>>>>>>>>> By example :
>>>>>>>>>
>>>>>>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
>>>>>>>>> Unsupported authMechanism: SCRAM-SHA-1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
>>>>>> this
>>>>>>>>> librairie or update it to the lastest version ?
>>>>>>>>>
>>>>>>>>> Thanks for ur feedback.
>>
>
Re: MongoDB driver
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello Andrei,
I don't see why we should drop elements that are not deprecated and are
used based on bug reports, SO questions.
MongoDB is not in that case as we can consider we are not maintaining it
and it is deprecated since many months.
Regards
On Sun, Jul 23, 2017 at 4:27 PM, Andrey Pokhilko <ap...@ya.ru> wrote:
> Based on these reasons, don't we see also worth deprecating:
>
> 1. Mail/SMTP components
>
AKAIK, they are not deprecated. And are useful, I saw several questions on
SO
> 2. LDAP components
>
AKAIK, they are not deprecated.
> 3. FTP
>
AKAIK, they are not deprecated. And are useful, I saw several questions on
SO
> 4. Any of other distribution bundle modules (junit/tcp etc)
>
AKAIK, they are not deprecated, neither JUnit nor TCP which is used a lot
from SO questions..
> Possible benefits for users is cleaner UI menus, smaller distribution
> archive size, faster JMeter startup. Do we have estimations of
> importance of those parts of JMeter?
>
> Andrey Pokhilko
>
> On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
> > Hello,
> > The decision to deprecate was motivated by many reasons:
> >
> > - Very low feedback both on SO, bugzilla and user mailing list
> > - No mention at all from MongoDB which seems to have its own tool
> > - The effort to upgrade (lot of deprecations) + the fact that an async
> > driver was released and that might be a better choice
> > - The fact that we need to make choices based on priorities :-) JDBC
> > sampler addresses many DB, MongoDB addresses 1 Product. I think it
> was a
> > mistake to add it (my mistake :-) )
> >
> > Regards
> >
> > On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com>
> wrote:
> >
> >> When the decision was made to deprecate no one was volunteering to
> update
> >> it. If we have volunteers then the volunteer(s) can update the driver.
> >> Mongo becomes undeprecated.
> >>
> >> Sent from my iPhone
> >>
> >>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <
> ra0077@gmail.com>
> >> wrote:
> >>> Issues, question in stackoverflow...
> >>>
> >>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>
> >>>> Out of curiosity, how do you measure usage? Based on issues opened?
> >>>>
> >>>> --emi
> >>>>
> >>>>
> >>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
> >>>> <ra...@gmail.com> wrote:
> >>>>> Hi,
> >>>>>
> >>>>> If I remember it's because we have few time to update it and because
> >> it's
> >>>>> not very used
> >>>>>
> >>>>> Antonio
> >>>>>
> >>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>>>
> >>>>>> I don't know why the MongoDB protocol got deprecated, but the next
> >>>>>> step would be removal of the classes not updating libraries.
> >>>>>>
> >>>>>> --emi
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> >>>>>> <mc...@apache.org> wrote:
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> The JMeter bundle still include a mongoDB java driver ( version
> >>>> 2.11.3 )
> >>>>>>> which is really old and doesn't work with all authentication
> >>>>>>>
> >>>>>>> By example :
> >>>>>>>
> >>>>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
> >>>>>>> Unsupported authMechanism: SCRAM-SHA-1
> >>>>>>>
> >>>>>>>
> >>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
> >>>> this
> >>>>>>> librairie or update it to the lastest version ?
> >>>>>>>
> >>>>>>> Thanks for ur feedback.
> >>
> >
>
>
--
Cordialement.
Philippe Mouawad.
Re: MongoDB driver
Posted by Andrey Pokhilko <ap...@ya.ru>.
Based on these reasons, don't we see also worth deprecating:
1. Mail/SMTP components
2. LDAP components
3. FTP
4. Any of other distribution bundle modules (junit/tcp etc)
Possible benefits for users is cleaner UI menus, smaller distribution
archive size, faster JMeter startup. Do we have estimations of
importance of those parts of JMeter?
Andrey Pokhilko
On 07/20/2017 10:15 PM, Philippe Mouawad wrote:
> Hello,
> The decision to deprecate was motivated by many reasons:
>
> - Very low feedback both on SO, bugzilla and user mailing list
> - No mention at all from MongoDB which seems to have its own tool
> - The effort to upgrade (lot of deprecations) + the fact that an async
> driver was released and that might be a better choice
> - The fact that we need to make choices based on priorities :-) JDBC
> sampler addresses many DB, MongoDB addresses 1 Product. I think it was a
> mistake to add it (my mistake :-) )
>
> Regards
>
> On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com> wrote:
>
>> When the decision was made to deprecate no one was volunteering to update
>> it. If we have volunteers then the volunteer(s) can update the driver.
>> Mongo becomes undeprecated.
>>
>> Sent from my iPhone
>>
>>> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <ra...@gmail.com>
>> wrote:
>>> Issues, question in stackoverflow...
>>>
>>> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>
>>>> Out of curiosity, how do you measure usage? Based on issues opened?
>>>>
>>>> --emi
>>>>
>>>>
>>>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
>>>> <ra...@gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> If I remember it's because we have few time to update it and because
>> it's
>>>>> not very used
>>>>>
>>>>> Antonio
>>>>>
>>>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>>>
>>>>>> I don't know why the MongoDB protocol got deprecated, but the next
>>>>>> step would be removal of the classes not updating libraries.
>>>>>>
>>>>>> --emi
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>>>>>> <mc...@apache.org> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> The JMeter bundle still include a mongoDB java driver ( version
>>>> 2.11.3 )
>>>>>>> which is really old and doesn't work with all authentication
>>>>>>>
>>>>>>> By example :
>>>>>>>
>>>>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
>>>>>>> Unsupported authMechanism: SCRAM-SHA-1
>>>>>>>
>>>>>>>
>>>>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
>>>> this
>>>>>>> librairie or update it to the lastest version ?
>>>>>>>
>>>>>>> Thanks for ur feedback.
>>
>
Re: MongoDB driver
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
The decision to deprecate was motivated by many reasons:
- Very low feedback both on SO, bugzilla and user mailing list
- No mention at all from MongoDB which seems to have its own tool
- The effort to upgrade (lot of deprecations) + the fact that an async
driver was released and that might be a better choice
- The fact that we need to make choices based on priorities :-) JDBC
sampler addresses many DB, MongoDB addresses 1 Product. I think it was a
mistake to add it (my mistake :-) )
Regards
On Wed, Jul 19, 2017 at 6:19 PM, John Schulz <jo...@aol.com> wrote:
> When the decision was made to deprecate no one was volunteering to update
> it. If we have volunteers then the volunteer(s) can update the driver.
> Mongo becomes undeprecated.
>
> Sent from my iPhone
>
> > On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <ra...@gmail.com>
> wrote:
> >
> > Issues, question in stackoverflow...
> >
> > 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >
> >> Out of curiosity, how do you measure usage? Based on issues opened?
> >>
> >> --emi
> >>
> >>
> >> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
> >> <ra...@gmail.com> wrote:
> >>> Hi,
> >>>
> >>> If I remember it's because we have few time to update it and because
> it's
> >>> not very used
> >>>
> >>> Antonio
> >>>
> >>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >>>
> >>>> I don't know why the MongoDB protocol got deprecated, but the next
> >>>> step would be removal of the classes not updating libraries.
> >>>>
> >>>> --emi
> >>>>
> >>>>
> >>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> >>>> <mc...@apache.org> wrote:
> >>>>> Hi,
> >>>>>
> >>>>> The JMeter bundle still include a mongoDB java driver ( version
> >> 2.11.3 )
> >>>>> which is really old and doesn't work with all authentication
> >>>>>
> >>>>> By example :
> >>>>>
> >>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
> >>>>> Unsupported authMechanism: SCRAM-SHA-1
> >>>>>
> >>>>>
> >>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
> >> this
> >>>>> librairie or update it to the lastest version ?
> >>>>>
> >>>>> Thanks for ur feedback.
> >>>>
> >>
>
>
--
Cordialement.
Philippe Mouawad.
Re: MongoDB driver
Posted by John Schulz <jo...@aol.com>.
When the decision was made to deprecate no one was volunteering to update it. If we have volunteers then the volunteer(s) can update the driver. Mongo becomes undeprecated.
Sent from my iPhone
> On Jul 19, 2017, at 10:02 AM, Antonio Gomes Rodrigues <ra...@gmail.com> wrote:
>
> Issues, question in stackoverflow...
>
> 2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
>
>> Out of curiosity, how do you measure usage? Based on issues opened?
>>
>> --emi
>>
>>
>> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
>> <ra...@gmail.com> wrote:
>>> Hi,
>>>
>>> If I remember it's because we have few time to update it and because it's
>>> not very used
>>>
>>> Antonio
>>>
>>> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>>>
>>>> I don't know why the MongoDB protocol got deprecated, but the next
>>>> step would be removal of the classes not updating libraries.
>>>>
>>>> --emi
>>>>
>>>>
>>>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>>>> <mc...@apache.org> wrote:
>>>>> Hi,
>>>>>
>>>>> The JMeter bundle still include a mongoDB java driver ( version
>> 2.11.3 )
>>>>> which is really old and doesn't work with all authentication
>>>>>
>>>>> By example :
>>>>>
>>>>> javax.script.ScriptException: java.lang.IllegalArgumentException:
>>>>> Unsupported authMechanism: SCRAM-SHA-1
>>>>>
>>>>>
>>>>> As mongoDB is deprecated in JMeter, my question is : Should we keep
>> this
>>>>> librairie or update it to the lastest version ?
>>>>>
>>>>> Thanks for ur feedback.
>>>>
>>
Re: MongoDB driver
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Issues, question in stackoverflow...
2017-07-19 16:00 GMT+02:00 Emilian Bold <em...@gmail.com>:
> Out of curiosity, how do you measure usage? Based on issues opened?
>
> --emi
>
>
> On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
> <ra...@gmail.com> wrote:
> > Hi,
> >
> > If I remember it's because we have few time to update it and because it's
> > not very used
> >
> > Antonio
> >
> > 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
> >
> >> I don't know why the MongoDB protocol got deprecated, but the next
> >> step would be removal of the classes not updating libraries.
> >>
> >> --emi
> >>
> >>
> >> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> >> <mc...@apache.org> wrote:
> >> > Hi,
> >> >
> >> > The JMeter bundle still include a mongoDB java driver ( version
> 2.11.3 )
> >> > which is really old and doesn't work with all authentication
> >> >
> >> > By example :
> >> >
> >> > javax.script.ScriptException: java.lang.IllegalArgumentException:
> >> > Unsupported authMechanism: SCRAM-SHA-1
> >> >
> >> >
> >> > As mongoDB is deprecated in JMeter, my question is : Should we keep
> this
> >> > librairie or update it to the lastest version ?
> >> >
> >> > Thanks for ur feedback.
> >>
>
Re: MongoDB driver
Posted by Emilian Bold <em...@gmail.com>.
Out of curiosity, how do you measure usage? Based on issues opened?
--emi
On Wed, Jul 19, 2017 at 3:19 PM, Antonio Gomes Rodrigues
<ra...@gmail.com> wrote:
> Hi,
>
> If I remember it's because we have few time to update it and because it's
> not very used
>
> Antonio
>
> 2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
>
>> I don't know why the MongoDB protocol got deprecated, but the next
>> step would be removal of the classes not updating libraries.
>>
>> --emi
>>
>>
>> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
>> <mc...@apache.org> wrote:
>> > Hi,
>> >
>> > The JMeter bundle still include a mongoDB java driver ( version 2.11.3 )
>> > which is really old and doesn't work with all authentication
>> >
>> > By example :
>> >
>> > javax.script.ScriptException: java.lang.IllegalArgumentException:
>> > Unsupported authMechanism: SCRAM-SHA-1
>> >
>> >
>> > As mongoDB is deprecated in JMeter, my question is : Should we keep this
>> > librairie or update it to the lastest version ?
>> >
>> > Thanks for ur feedback.
>>
Re: MongoDB driver
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi,
If I remember it's because we have few time to update it and because it's
not very used
Antonio
2017-07-19 14:15 GMT+02:00 Emilian Bold <em...@gmail.com>:
> I don't know why the MongoDB protocol got deprecated, but the next
> step would be removal of the classes not updating libraries.
>
> --emi
>
>
> On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
> <mc...@apache.org> wrote:
> > Hi,
> >
> > The JMeter bundle still include a mongoDB java driver ( version 2.11.3 )
> > which is really old and doesn't work with all authentication
> >
> > By example :
> >
> > javax.script.ScriptException: java.lang.IllegalArgumentException:
> > Unsupported authMechanism: SCRAM-SHA-1
> >
> >
> > As mongoDB is deprecated in JMeter, my question is : Should we keep this
> > librairie or update it to the lastest version ?
> >
> > Thanks for ur feedback.
>
Re: MongoDB driver
Posted by Emilian Bold <em...@gmail.com>.
I don't know why the MongoDB protocol got deprecated, but the next
step would be removal of the classes not updating libraries.
--emi
On Wed, Jul 19, 2017 at 12:55 PM, Maxime Chassagneux
<mc...@apache.org> wrote:
> Hi,
>
> The JMeter bundle still include a mongoDB java driver ( version 2.11.3 )
> which is really old and doesn't work with all authentication
>
> By example :
>
> javax.script.ScriptException: java.lang.IllegalArgumentException:
> Unsupported authMechanism: SCRAM-SHA-1
>
>
> As mongoDB is deprecated in JMeter, my question is : Should we keep this
> librairie or update it to the lastest version ?
>
> Thanks for ur feedback.