Skip Menu |

This queue is for tickets about the Dancer-Session-ElasticSearch CPAN distribution.

Report information
The Basics
Id: 93350
Status: resolved
Worked: 20 min
Priority: 0/
Queue: Dancer-Session-ElasticSearch

People
Owner: Nobody in particular
Requestors: dolmen [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Elasticsearch replaces ElasticSearch
Elasticsearch is the new name of the ElasticSearch module. -- Olivier Mengué - http://perlresume.org/DOLMEN
On Tue Feb 25 10:34:33 2014, DOLMEN wrote: Show quoted text
> Elasticsearch is the new name of the ElasticSearch module.
Fixed in 1.006 Ta
On 2014-02-25 10:00:55, BABF wrote: Show quoted text
> On Tue Feb 25 10:34:33 2014, DOLMEN wrote:
> > Elasticsearch is the new name of the ElasticSearch module.
> > Fixed in 1.006 > > Ta >
Elasticsearch is NOT a simple drop-in replacement for ElasticSearch. They have different APIs. Please be sure to test before making this change, and make it clear to the users that they now need to formulate their calls differently!!!! Or alternatively, allow an option to let them specify which backend they are using.
Subject: Re: [rt.cpan.org #93350] Elasticsearch replaces ElasticSearch
Date: Wed, 26 Feb 2014 06:54:53 +0000
To: bug-Dancer-Session-ElasticSearch [...] rt.cpan.org
From: Robbie Bow <robbiebow [...] gmail.com>
Feel free to make a clone, patch as necessary and make a pull request On 25 Feb 2014 23:12, "Karen Etheridge via RT" < bug-Dancer-Session-ElasticSearch@rt.cpan.org> wrote: Show quoted text
> Queue: Dancer-Session-ElasticSearch > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=93350 > > > On 2014-02-25 10:00:55, BABF wrote:
> > On Tue Feb 25 10:34:33 2014, DOLMEN wrote:
> > > Elasticsearch is the new name of the ElasticSearch module.
> > > > Fixed in 1.006 > > > > Ta > >
> > > > Elasticsearch is NOT a simple drop-in replacement for ElasticSearch. They > have different APIs. Please be sure to test before making this change, and > make it clear to the users that they now need to formulate their calls > differently!!!! > > Or alternatively, allow an option to let them specify which backend they > are using. >