Closed kurry421 closed 5 years ago
Can you run the server VERBOSE=1?
Hey @dplewis thanks for your reply. In my server set up I included logLevel: "VERBOSE"
but the logs are not showing anything more verbose.. is my set up incorrect?
var api = new ParseServer({
appName: AppName,
databaseURI: databaseUri,
cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
appId: process.env.APP_ID,
masterKey: process.env.MASTER_KEY,
fileKey: process.env.FILE_KEY,
serverURL: process.env.SERVER_URL,
publicServerURL: process.env.SERVER_URL,
clientKey: process.env.CLIENT_KEY,
javascriptKey: process.env.JAVASCRIPT_KEY,
liveQuery: {
classNames: ["Room", "Messages"], // List of classes to support for query subscriptions
redisURL: process.env.redisURL
},
databaseOptions: { poolSize: 500 },
maxUploadSize: "5mb",
logLevel: "VERBOSE",
verbose: true
});
ParseServer.createLiveQueryServer(httpServer, {
appId: process.env.APP_ID,
masterKey: process.env.MASTER_KEY,
serverURL: process.env.SERVER_URL,
javascriptKey: process.env.JAVASCRIPT_KEY,
redisURL: process.env.redisURL,
websocketTimeout: 10 * 1000,
cacheTimeout: 60 * 600 * 1000,
logLevel: "VERBOSE",
verbose: true
});
I don’t see where you are saving objects in your log. Are they "Room" objects?
im scratching my head as to why the logs aren't printing it out.
But, the Room class has a relation to Messages class.
When a client saves a message, it saves it in the Messages class and attaches the new object as a relation to the Room class.
Live Query doesn’t handle relations. You could do an array of ObjectIds as a work around
Thanks for the suggestion - question -since client is subscribed to Messages class on Livequery, shouldn't the client get an update when a new object is created/saved? edit - I guess it depends on the query client side, I updated so that client subscribed on Messages class. No dice when I update/add new message.
I just tested your suggestion on the Room class - I added a new column in the Room class, and manually added an array of strings while client connection was enabled. The client was not receiving the updates or create events
update digging deeper into this, it looks like functionality is working as expected locally. this leads me to believe that may be an AWS EB and/or Redis connection issue that is preventing when running correctly from the cloud.
Check your Nginx Configuration.
Here is a great guide that was made specifically for AWS
Live Query doesn’t handle relations. You could do an array of ObjectIds as a work around
Hello,
Thank you for this information.
Is there an article in the documentation where such limitations regarding LiveQueries are listed? I was not able to find this information in the following documentations (maybe I missed something):
It would be great to have them listed with a few workarounds for these known limitations.
Have a good day,
Hi everyone.. I'm facing the same issue.. My open event is triggered.. but my create and update events are not working.. i'm writing my client in angular.. Kindly inform how did you resolve your issue..??
Issue Description
I have setup Livequery however when I update the database, the client is not receiving the update notification.
Steps to reproduce
On the client I subscribe to the Livequery server. I send a message (write a new object to db). However Livequery does not send any update on the client.
Expected Results
Client Side Code:
Actual Outcome
There is no Livequery notification on update/create.
Environment Setup
-Client JS
Server Main App Setup Code:
Server Live Query App Setup Code
On AWS, I set up the NGINX for both env and set up Security group for the Elasticache:
Logs/Trace