Which version of moxi should I use with Couchbase 2.0?

94 views
Skip to first unread message

Teemu Harju

unread,
Apr 29, 2013, 6:05:52 AM4/29/13
to couc...@googlegroups.com
Hi,

I just noticed that the version of moxi what comes with the Couchbase 2.0 .deb package is 2.0 and the latest standalone install package of moxi has version 1.8. Should I use the 2.0 version that comes with the Couchbase .deb package? I installed the standalone package because I didn't want to install Couchbase server on the "client" machines.

Br,

Teemu

Tugdual Grall

unread,
Apr 30, 2013, 5:45:02 AM4/30/13
to couc...@googlegroups.com

First of all:
- Can you switch to a Couchbase client? 
This is the most effective way to access Couchbase


Based on what I see in the documentation you should use the 1.8:

Regards
Tug
@tgrall

Aliaksey Kandratsenka

unread,
Apr 30, 2013, 3:27:27 PM4/30/13
to couc...@googlegroups.com
Code-wise 1.8.1 moxi is identical to 2.0.0, 2.0.1 and to current state of upcoming 2.0.2. There's just single new commit that fixes automake incompatibility since 1.8.1 tag.

That's because development of moxi is frozen since long time ago and apparently no critical bugs were reported since 1.8.1 release.


--
You received this message because you are subscribed to the Google Groups "Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Teemu Harju

unread,
Apr 30, 2013, 11:09:22 PM4/30/13
to couc...@googlegroups.com
Thanks for the info. Unfortunately I cannot use any client SDK since we use Python and the Python SDK is not currently working very well. I'm eagerly waiting for the libcouchbase based SDK that is under development.

- Teemu

Matt Ingenthron

unread,
Apr 30, 2013, 11:42:07 PM4/30/13
to couc...@googlegroups.com
On 4/30/13 8:09 PM, "Teemu Harju" <teemu...@gmail.com> wrote:

Thanks for the info. Unfortunately I cannot use any client SDK since we use Python and the Python SDK is not currently working very well. I'm eagerly waiting for the libcouchbase based SDK that is under development.

We're in the process of posting version 0.9, and it's up at pypi right now.  We'd appreciate your feedback!

Matt

p.s.: thanks for joining us all the way from Finland!  ;)



tiistai, 30. huhtikuuta 2013 22.27.27 UTC+3 Aliaksey Kandratsenka kirjoitti:
Code-wise 1.8.1 moxi is identical to 2.0.0, 2.0.1 and to current state of upcoming 2.0.2. There's just single new commit that fixes automake incompatibility since 1.8.1 tag.

That's because development of moxi is frozen since long time ago and apparently no critical bugs were reported since 1.8.1 release.


On Mon, Apr 29, 2013 at 3:05 AM, Teemu Harju <teemu...@gmail.com> wrote:
Hi,

I just noticed that the version of moxi what comes with the Couchbase 2.0 .deb package is 2.0 and the latest standalone install package of moxi has version 1.8. Should I use the 2.0 version that comes with the Couchbase .deb package? I installed the standalone package because I didn't want to install Couchbase server on the "client" machines.

Br,

Teemu

--
You received this message because you are subscribed to the Google Groups "Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


-- 
Matt Ingenthron
Couchbase, Inc.

Teemu Harju

unread,
May 1, 2013, 11:21:42 PM5/1/13
to couc...@googlegroups.com
Thanks Matt,

I couldn't get the 0.9 from pypi yet. Still gives me 0.8, but once it's there I'll definitely give it a try.

- Teemu

Matt Ingenthron

unread,
May 1, 2013, 11:36:28 PM5/1/13
to couc...@googlegroups.com
Hi Teemu,

I've just now (in the last few minutes) fixed an issue there.

Please let me know if you still have issues.

Thanks!

Matt

-- 
Matt Ingenthron - Director, Developer Solutions
Couchbase, Inc.

Teemu Harju

unread,
May 2, 2013, 6:57:46 AM5/2/13
to couc...@googlegroups.com
Thanks for the quick fix Matt. However, building the c-extension fails on my machine (osx). Here's the error output in case it gives you idea what might be wrong...

pip install couchbase
Downloading/unpacking couchbase
  Running setup.py egg_info for package couchbase

Installing collected packages: couchbase
  Running setup.py install for couchbase
    building 'couchbase/libcouchbase' extension
    cc -fno-strict-aliasing -fno-common -dynamic -I/usr/local/include -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c couchbase/libcouchbase.c -o build/temp.macosx-10.8-x86_64-2.7/couchbase/libcouchbase.o
    couchbase/libcouchbase.c:785:22: error: unknown type name '__time_t'; did you mean 'time_t'?
    static CYTHON_INLINE __time_t __Pyx_PyInt_from_py___time_t(PyObject *);
                         ^~~~~~~~
                         time_t
    /usr/include/sys/select.h:87:26: note: 'time_t' declared here
    typedef __darwin_time_t         time_t;
                                    ^
    couchbase/libcouchbase.c:14645:22: error: unknown type name '__time_t'; did you mean 'time_t'?
    static CYTHON_INLINE __time_t __Pyx_PyInt_from_py___time_t(PyObject* x) {
                         ^~~~~~~~
                         time_t
    /usr/include/sys/select.h:87:26: note: 'time_t' declared here
    typedef __darwin_time_t         time_t;
                                    ^
    couchbase/libcouchbase.c:14646:11: error: unknown type name '__time_t'; did you mean 'time_t'?
        const __time_t neg_one = (__time_t)-1, const_zero = (__time_t)0;
              ^~~~~~~~
              time_t
    /usr/include/sys/select.h:87:26: note: 'time_t' declared here
    typedef __darwin_time_t         time_t;
                                    ^
    couchbase/libcouchbase.c:14646:31: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        const __time_t neg_one = (__time_t)-1, const_zero = (__time_t)0;
                                  ^
    couchbase/libcouchbase.c:14646:58: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        const __time_t neg_one = (__time_t)-1, const_zero = (__time_t)0;
                                                             ^
    couchbase/libcouchbase.c:14648:16: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        if (sizeof(__time_t) == sizeof(char)) {
                   ^
    couchbase/libcouchbase.c:14650:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsUnsignedChar(x);
                        ^
    couchbase/libcouchbase.c:14652:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsSignedChar(x);
                        ^
    couchbase/libcouchbase.c:14653:23: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        } else if (sizeof(__time_t) == sizeof(short)) {
                          ^
    couchbase/libcouchbase.c:14655:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsUnsignedShort(x);
                        ^
    couchbase/libcouchbase.c:14657:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsSignedShort(x);
                        ^
    couchbase/libcouchbase.c:14658:23: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        } else if (sizeof(__time_t) == sizeof(int)) {
                          ^
    couchbase/libcouchbase.c:14660:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsUnsignedInt(x);
                        ^
    couchbase/libcouchbase.c:14662:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsSignedInt(x);
                        ^
    couchbase/libcouchbase.c:14663:23: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        } else if (sizeof(__time_t) == sizeof(long)) {
                          ^
    couchbase/libcouchbase.c:14665:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsUnsignedLong(x);
                        ^
    couchbase/libcouchbase.c:14667:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsSignedLong(x);
                        ^
    couchbase/libcouchbase.c:14668:23: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
        } else if (sizeof(__time_t) == sizeof(PY_LONG_LONG)) {
                          ^
    couchbase/libcouchbase.c:14670:21: error: use of undeclared identifier '__time_t'; did you mean 'time_t'?
                return (__time_t)__Pyx_PyInt_AsUnsignedLongLong(x);
                        ^
    fatal error: too many errors emitted, stopping now [-ferror-limit=]
    20 errors generated.
    error: command 'cc' failed with exit status 1

Teemu

Алексей Терехов

unread,
May 6, 2013, 6:34:34 AM5/6/13
to couc...@googlegroups.com
this save your python project:
apt-get install git;
pip install git+git://github.com/kvogt/couchbase-python-client.git;


четверг, 2 мая 2013 г., 13:57:46 UTC+3 пользователь Teemu Harju написал:
Thanks for the quick fix Matt. However, building the c-extension fails on my machine (osx). Here's the error output in case it gives you idea what might be wrong...

pip install couchbase
Downloading/unpacking couchbase
  Running setup.py egg_info for package couchbase

Reply all
Reply to author
Forward
0 new messages