griddb | generation open source database that makes time series IoT

GridDB (https://github.com/griddb/griddb) is Database for IoT with both NoSQL interface and SQL Interface. This is Python Client Library for GridDB.

Installation Package dependencies

GridDB C Client Download and install RPM or DEB package in GridDB C Client (https://github.com/griddb/c_client/releases).

Install RPM package by this command:

$ sudo yum localinstall package_name.rpm Install DEB package by this command:

$ sudo dpkg -i package_name.deb Pandas and Numpy Install Pandas and Numpy by these commands:

$ python -m pip install numpy

$ python -m pip install pandas

Install the package by the following:

$ pip install griddb_python

That error is commonly seen when GridDB is compiled on a machine with low memory.

You're looking for the TQL ASC or DESC operator which will invert the order data is returned.

If you actually want an inverted index a timestamp I would add a field to your schema and when inserting data, insert (LLONG_MAX - timestamp)

Why are you iterating over SqlDataReader once again after the while statement?

This works:

I checked and executed sample1.c following GridDB Github.

It's OK with my environment.

I suggest:

• You need to check status of your database.
• You need to check container with your container name which is exist or not in your database
• If exist, please drop container. You need to update sample1.c with drop container
• If not, please debug and give more information about failed step.

• Your error is ../depcomp: line 772: exec: g++: not found.
• It causes by your environment which don't have g++ compiler.
• I checked on GridDB repository in Github. Compiler required is CentOS 7.6 (gcc 4.8.5), Ubuntu 18.04 (gcc 4.8.5) and openSUSE Leap 15.1 (gcc 4.8.5).
• You need to install g++ compiler version 4.8.5.

Does your original password contain any special characters? GridDB currently doesn’t accept passwords with chars like %, etc.

As for changing your password and still not working — did you stop the node (gs_stop node) before changing the pass? The changes won’t stick if you do it while the node is running.

GridDB stores TIMESTAMP values in millisecond resolution, inserting records with greater resolution such as micro or nanosecond resolution will result in the timestamp value being truncated. There are three ways to get around the timestamp collisions:

1. Use a Collection with a long as your first index. In that long, store a Unix Epoch in micro or nanoseconds as required. You will obviously lose some time series functions and have to manually convert comparison operators to a Unix epoch in your desired resolution.

2. Use a collection and disable the row key (No @RowKey tag in Java or set the last Boolean in ContainerInfo to False in other languages). This will allow multiple records to have the same "row key value". You can enable a secondary index on this column to ensure queries are still fast. TIMESTAMP and TO_TIMESTAMP_MS functions still work but I'm fairly certain none of the other special timestamp functions will work. When I've had to deal with Timestamp collisions in GridDB, this is the solution I chose.

3. Detect the collisions before you insert and if there is going to be a collision, write the colliding record into a separate container. Use multi-get/query to query all of the containers.