GEOADD passes long/lat parameters in the wrong order to Redis

[IdanFridman]

Redis GEOADD API expecting latitude,longitude (with that order)

Lettuce API has the opposite order:
RedisFuture geoadd(K key, double longitude, double latitude, V member);

Thanks,
Idan.

[mp911de]

Affected versions: 3.3, 3.4 and 4.0

[mp911de]

It's actually the other way round. Redis expects longitude latitude (see http://redis.io/commands/geoadd). The API has the correct signature, but the values are passed in the wrong order towards Redis. The parameter order was switched during the Geo API development (see redis/redis#2705). In contrast to the current impl, Matt's implementation used latitude longitude.

[mp911de]

Fixed 4.0-SNAPSHOT available on https://oss.sonatype.org/content/repositories/snapshots/

[IdanFridman]

Thank you.

2015-09-10 8:46 GMT+03:00 Mark Paluch [email protected]:

Closed #134 https://github.com/mp911de/lettuce/issues/134.

—
Reply to this email directly or view it on GitHub
https://github.com/mp911de/lettuce/issues/134#event-405581613.