-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with what is written in cassandra #116
Comments
@2014siavash we'll check this out. @drasko did some refactoring on the service, so he'll check out this bug as well. |
@2014siavash you are correct, and all SenML sent to Mainflux is now normalized i.e. resolved before it is being written into Cassandra. Please take a look at SenML spec, chapter 4.4 "Resolved Records": https://tools.ietf.org/html/draft-ietf-core-senml-10#page-8 We should completely remove base values from Cassandra tables, they are not needed anymore. |
Signed-off-by: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
Signed-off-by: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
* Add selectable and hover to attribute editor Signed-off-by: Darko Draskovic <darko.draskovic@gmail.com> * Use subtopic as attrib name when name empty Signed-off-by: Darko Draskovic <darko.draskovic@gmail.com>
* feat(invitations): Implement invitations outline This commit adds the necessary data structures and methods for managing invitations to join a domain. It includes structs for invitations, pages of invitations, and pages of invitations with additional metadata. Additionally, error variables for missing and invalid relations are defined. The commit also introduces methods for sending, viewing, listing, accepting, and deleting invitations. In addition, it includes functions for creating, retrieving, updating, and deleting invitations in a repository. Furthermore, a function is added to check the validity of a relation, returning an error if it does not match specific values. Signed-off-by: Rodney Osodo <28790446+rodneyosodo@users.noreply.github.com> * docs(invitations): add godocs * test: Add tests for MarshalJSON and CheckRelation Add tests to ensure the MarshalJSON function of the InvitationPage struct correctly marshals the JSON representation. Also, add tests for the CheckRelation function to verify its behavior in different scenarios. The tests use a loop and the assert.Equal function to compare expected and actual errors. Signed-off-by: Rodney Osodo <28790446+rodneyosodo@users.noreply.github.com> * feat(invitations): add withToken parameter to RetrieveAll method This commit adds a new parameter "withToken" to the RetrieveAll method in the invitations package. This parameter allows the caller to specify whether they want to include the token in the returned invitation list. Signed-off-by: Rodney Osodo <28790446+rodneyosodo@users.noreply.github.com> * docs(invitations): Add Base README --------- Signed-off-by: Rodney Osodo <28790446+rodneyosodo@users.noreply.github.com>
Hi,
I dont know it is an issue or not, but when I want to see what is written in the database, I saw that some variables are written in different columns or just not written in the database such as "bn", "bt" and so on (the null ones). I saw "bn" in the column "n", as you can see in the below. More precisely, in the column "n", we can see for example "some-base-name:voltage", but "some-base-name" is for column "bn" and column "n" should be just "voltage". There are also maybe some other substitutions ("bt" is written in "t" and so on).
Am I wrong?
I used your instruction at http://mainflux.readthedocs.io/en/latest/
thanks for your support.
The text was updated successfully, but these errors were encountered: