Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:47
    sonarcloud[bot] commented #1589
  • 07:47
    sonarcloud[bot] commented #1589
  • 07:45
    codecov[bot] commented #1589
  • 07:45
    codecov[bot] commented #1589
  • 07:45
    Aschen synchronize #1589
  • 07:45

    Aschen on update-sdk-js

    Add debug when ES throw an error (compare)

  • Mar 27 11:44
    sonarcloud[bot] commented #1589
  • Mar 27 11:42
    Aschen labeled #1589
  • Mar 27 11:42
    Aschen assigned #1589
  • Mar 27 11:42
    Aschen labeled #1589
  • Mar 27 11:42
    Aschen opened #1589
  • Mar 27 11:38

    Aschen on update-sdk-js

    Bump sdk version 2.1.3 (compare)

  • Mar 26 05:06
    codecov[bot] commented #1587
  • Mar 26 05:05
    codecov[bot] commented #1587
  • Mar 26 05:05
    codecov[bot] commented #1587
  • Mar 26 04:43
    sonarcloud[bot] commented #1587
  • Mar 26 04:43
    sonarcloud[bot] commented #1587
  • Mar 26 04:41
    codecov[bot] commented #1587
  • Mar 26 04:41
    codecov[bot] commented #1587
  • Mar 26 04:41
    Aschen synchronize #1587
Alexandre Bouthinon
@alexandrebouthinon
This message was deleted
enlight3d
@enlight3d
ah alright
so, what is the issue ?
Alexandre Bouthinon
@alexandrebouthinon
    environment:
      - kuzzle_services__db__client__host=http://elasticsearch_7:9200
      - kuzzle_services__internalCache__node__host=redis
      - kuzzle_services__memoryStorage__node__host=redis
      - NODE_ENV=production
These settings are for Kuzzle v1
enlight3d
@enlight3d
ah
Alexandre Bouthinon
@alexandrebouthinon
try this:
      - kuzzle_services__storageEngine__client__node=http://elasticsearch:9200
      - kuzzle_services__internalCache__node__host=redis
      - kuzzle_services__memoryStorage__node__host=redis
      - NODE_ENV=production
enlight3d
@enlight3d
thanks ! trying right now
okay
some progress here
enlight3d
@enlight3d

[x] [ERROR] PluginImplementationError: [/var/app/plugins/enabled/kuzzle-plugin-probe-listener/manifest.json] Unable to load the file 'manifest.json': Cannot find module '/var/app/plugins/enabled/kuzzle-plugin-probe-listener/manifest.json',
[2020-02-19 11:05:27+00:00] Starting Kuzzle...,
[ℹ] Starting Kuzzle server,
[✔] Cache engine initialized,
[✔] Storage engine initialized,
PluginImplementationError: [/var/app/plugins/enabled/kuzzle-plugin-probe-listener/manifest.json] Unable to load the file 'manifest.json': Cannot find module '/var/app/plugins/enabled/kuzzle-plugin-probe-listener/manifest.json'
should I remove both entries in volumes section of kuzzle service ?
enlight3d
@enlight3d
yup removing that made it work ! perfect :) thanks
so, shouldn't there be any volume created for kuzzle or redis to retain the users' infos?
Alexandre Bouthinon
@alexandrebouthinon
Users info and Data are stored in Elasticsearch, if you want to retain them you should create a volume for Elasticsearch service
enlight3d
@enlight3d
ah fine, it's already the case then
Faizan Sheikh
@sheikh431_twitter
Hi, I have an array in my document, I want to append more data in array, rather to replace, Is there a way to do that? @scottinet @j33f @ctcook @bradjonesca
Adrien Maret
@Aschen
Hi @sheikh431_twitter ,
There is no way to do this with ES, you have to get the previous array, append your data and then send it back
Faizan Sheikh
@sheikh431_twitter
Thankyou, Adrien
Faizan Sheikh
@sheikh431_twitter
can I unsubscribe a room in kuzzle with roomId?
Sébastien Cottinet
@scottinet
enlight3d
@enlight3d
hello, is there a way for kuzzle to access already existing indexes inside elasticsearch that were created by another service ?
Sébastien Cottinet
@scottinet
Kuzzle v1: yes, no condition.
Kuzzle v2: indexes created outside the Kuzzle API can only be accessed if they are named (or aliased) using the Kuzzle naming system: https://docs.kuzzle.io/core/2/guides/essentials/store-access-data/#kuzzle-indexes-in-elasticseach
enlight3d
@enlight3d
thank you !
enlight3d
@enlight3d
alright, managed to do what I want using reindex api of elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#docs-reindex-api-desc)
Faizan Sheikh
@sheikh431_twitter
Hi, as we do everything in Kuzzle in onSuccess method, what if we want to return anything from the function? like I search some document from collection, and its response comes to onSuccess method, then how I can return the result? @scottinet @Aschen @alexandrebouthinon
Sébastien Cottinet
@scottinet

The onSuccess event provides a Request object, containing informations about the ongoing request. When you plug a pipe on it, then Kuzzle expects it to resolve a Request object. That new object (or the same one, modified or not) is used by Kuzzle to respond to the corresponding query. If you don't resolve with a Request object, Kuzzle will throw an error.

To resolve a request object, you have to invoke the callback provided by the event, or return a promise ultimately resolving to a request object.

Documentation: https://docs.kuzzle.io/core/2/plugins/guides/pipes/#usage

Faizan Sheikh
@sheikh431_twitter
Hi, I am creating mapping by this way { "zone_coordinates":{"type":"polygon"} } but it generate an error 'the data type "polygon" doesn't exist' @scottinet @Aschen @alexandrebouthinon
Adrien Maret
@Aschen
Hello @/all !
We just finish our Winter Release 2020 blog post: https://blog.kuzzle.io/kuzzle-winter-release-2020
Check it out if you want to know about our latest releases :-)
  • Kuzzle 2.1.0
  • Our shiny new command-line interface
  • Our Admin Console gets a new look
  • Java SDK 3 beta & Javascript 7.1 for Kuzzle v2
Faizan Sheikh
@sheikh431_twitter
Hi, @scottinet @Aschen I am facing this exception while updating the document(JAVA sdk)
org.json.JSONException: JSONObject["_source"] not found
Gabriel Pulido
@gpulido
@Aschen Just checking kourou and I'm surprised that is written in ts. Giving that Kuzzle doesn't provide its own types definition for the sdk at this moment, would this means that maybe are you going to provide one? It would be amazing so I don't have to keep mine updated :)
Faizan Sheikh
@sheikh431_twitter
Hi, @Aschen @gpulido @scottinet
Is there any issue with updateDocument in java sdk?
Sébastien Cottinet
@scottinet

Hi @gpulido
Regarding typescript and our JS SDK, we're against a ts type definitions file and we already refused contributor PR about this subject.
Our reasoning is simple: to this day (and to our knowledge), there aren't any tools able to detect that ts type definitions are out-of-date, so we cannot guarantee that it will continue to work despite the changes. This is against our quality policies, so we cannot add it.

But we also discussed a few months ago about the future of our JS SDK, and we all agreed that typescript is now sufficiently mature and used, and that our next major version of our JS SDK should be directly written in TS.

Gabriel Pulido
@gpulido
@scottinet I already knew about the PR for adding types, that in fact is the one I'm using as a base for my types for Angular. As I read through th explanation of why don't add the types, I also tried to found a way to at least test for the types against the JS SDK implementation and I didn't found an automatic way.
Being said this, from my humble POW, the JS SDK api is not changing so frenquenly that could not have another "task" associated that is just update the types to match the new implementations. At least for the released versions (the ones with tag). But I know is easy to say from my pow that doesn't have "resources" and "bills" to pay.
And going back to the present / future, if your are going to write the next JS SDK in TS, that would mean that the problem will solve itself, as you will have the types declared for the TS, so I just have to wait until the new major release to have them and until them just use my types that just cover the functionallity that I need from the api to be exposed on the "to-be-called ngrx-kuzzle" module.
shawub
@shawub
Hi, is https://console.kuzzle.io/ down atm? Im gettimg a 504
fmilonas
@fmilonas
Hi, I am new to all this stuff. I'm trying to set up kuzzle. Until yesterday everything ran smoothly but today when I write on the terminal <<curl "http://localhost:7512/?pretty">> it gives me a 403 error and doesn't connect to the localhost. Also, is it necessary to always install kuzzle running this command <<bash -c "$(curl https://get.kuzzle.io/)">> to get it started?
My final step yesterday was to the point <<node subscribe.js>> on the first steps
Adrien Maret
@Aschen
Hi @fmilonas ,
The 403 error mean thats you don't have the right to execute an API action, typically it occur when you are not logged in and the anonymous user have restricted rights https://docs.kuzzle.io/core/2/api/essentials/error-handling/
You don't have to run the script each time you want to run Kuzzle, you can simply use the Docker-compose file to run the container.

If you are planning to develop an application that need custom server side logic, I advise you to clone this repo and start Kuzzle from the docker-compose.yml file present at the directory root: https://github.com/kuzzleio/kuzzle-core-plugin-boilerplate

If you only want to use Kuzzle API from a frontend application, you can stick with the docker-compose.yml file downloaded by the installation script, or you can also use our CLI, Kourou, to run a Kuzzle Stack: https://github.com/kuzzleio/kourou/#kourou-instancespawn

fmilonas
@fmilonas
ok thanks but how i fix the error?
is there a way to remove everything and install everything from scratch?
Ibrahima Gaye
@ibstelix
hi all
i have this document:
image.png
i searched the document like this:
 results = await kuzzle.document.search(
                'test19',
                'tracking',
                {
                    query: {
                        match: {
                          "name": 'INDIVIDU_1'
                        }
                      }

                },
            );
but result is always 0
is that normal?
Ibrahima Gaye
@ibstelix
any help please