Object count is always 0 #1470

Activity

1. davimacedo commented on Feb 12, 2020

   

   davimacedo

   on Feb 12, 2020

   Member

   More actions

   I couldn't reproduce the issue. Could you share all dependencies that you have in your package.json, yoru parse server config and your parse dashboard config?
2. Wouter125 commented on Feb 12, 2020

   

   Wouter125

   on Feb 12, 2020

   Author

   More actions

   Sure!

   Full package.json;

   {
     "name": "prod-api",
     "version": "1.0.0",
     "description": "",
     "main": "index.js",
     "scripts": {
       "test": "echo \"Error: no test specified\" && exit 1",
       "start": "node index.js"
     },
     "author": "Wouter",
     "license": "ISC",
     "dependencies": {
       "@parse/s3-files-adapter": "^1.4.0",
       "parse-server": "^3.10.0",
       "parse-dashboard": "^2.0.5"
     }
   }
   

   Parse server config and Parse dashboard config. Running from my DO droplet;

   const express = require('express');
   const { default: ParseServer, ParseGraphQLServer } = require('parse-server');
   const ParseDashboard = require('parse-dashboard');
   const S3Adapter = require('@parse/s3-files-adapter');
   const AWS = require("aws-sdk");
   
   // Create express app
   const app = express();
   
   // Configure DO spaces adapter
   const spacesEndpoint = new AWS.Endpoint('fra1.digitaloceanspaces.com');
   
   const S3Options = {
       bucket: '',
       baseUrl: 'https://fra1.digitaloceanspaces.com',
       region: 'fra1',
       directAccess: true,
       globalCacheControl: "public, max-age=31536000",
       bucketPrefix: '',
       s3overrides: {
           accessKeyId: '',
           secretAccessKey: '',
           endpoint: spacesEndpoint
       }
   };
   
   const filesAdapter = new S3Adapter(S3Options);
   
   // Create Parse REST server instance
   const parseServer = new ParseServer({
       databaseURI: 'postgres://{user}:{pass}@localhost:5432/database',
       appId: '',
       masterKey: '',
       readOnlyMasterKey: '',
       serverURL: 'http://localhost:1337/parse',
       allowClientClassCreation: false,
       filesAdapter: filesAdapter
   });
   
   // Create Parse GraphQL server instance
   const parseGraphQLServer = new ParseGraphQLServer(
       parseServer,
       {
           graphQLPath: '/graphql',
           playgroundPath: '/playground'
       }
   );
   
   // Create Parse dashboard instance
   var parseDashboard = new ParseDashboard({
       "apps": [
           {
               "serverURL": "",
               "appId": "",
               "masterKey": "",
               "readOnlyMasterKey": "",
               "graphQLServerURL": "",
               "appName": ""
           }
       ],
       "users": [
           {
               "user": "Wouter",
               "pass": ""
           },
           {
               "user": "",
               "pass": ""
           },
           { 
               "user": "",
               "pass": "",
               "readOnly": true
           }
       ],
       "useEncryptedPasswords": true
   });
   
   // Mount the REST API
   app.use('/parse', parseServer.app);
       
   // Mount the Dashboard
   app.use('/dashboard', parseDashboard);
       
   // Mount the GraphQL API
   parseGraphQLServer.applyGraphQL(app);
           
   // Start the server
   const port = 1337;
   const httpServer = require('http').createServer(app);
   
   httpServer.listen(port, () => {
   });
   

   I've stripped out some values and passwords of course. But I think this will do the trick.
3. davimacedo commented on Feb 12, 2020

   

   davimacedo

   on Feb 12, 2020

   Member

   More actions

   Do you see any error message either in your Parse Server or Web browser console?
4. Wouter125 commented on Feb 12, 2020

   

   Wouter125

   on Feb 12, 2020

   Last edited by Wouter125

   Author

   More actions

   I was checking that before, but unfortunately not. Only the warning that I didn't set my push notification locale. That's why I opened this issue. 😬

   Is there any way I can increase the logging on the server? A verbose flag or anything? Also is it possible there is cache active on the graphQL layer or inside parse server?

   I already removed postgres once and did a clean install. Also deleted the node modules and reinstalled them. Neither of them brought back the count.
5. dplewis commented on Feb 13, 2020

   

   dplewis

   on Feb 13, 2020

   Last edited by dplewis

   Member

   More actions

   Count operations are expensive operations. In the dashboard we use estimated count.

   https://github.com/parse-community/parse-server/pull/5330/files

   We should add this information in the read me as I've seen users ask about this before.

   If you are using PG you can force the estimate count to update by using ANALYZE on a specific class.
6. Wouter125 commented on Feb 14, 2020

   

   Wouter125

   on Feb 14, 2020

   Last edited by Wouter125

   Author

   More actions

   Alright, I just added some more rows to see what happens.

   

   Still displaying zero. It counts on creation, and on deletion, on filtering. But it remains 0 when just rendering the list.
7. dplewis commented on Feb 14, 2020

   

   dplewis

   on Feb 14, 2020

   Last edited by dplewis

   Member

   More actions

   There are certain triggers that will update estimated count. If you are using Postgres check out the thread I posted before or google Autovacuum or ANALYZE command for PG.
8. Wouter125 commented on Feb 15, 2020

   

   Wouter125

   on Feb 15, 2020

   Last edited by Wouter125

   Author

   More actions

   Gotcha. So I just ran vacuumdb -d [dbname] -v -f -F on my database, and now all counts are working correctly. Thank you for your help and explaining how this works! 🙏

   👍React with 👍1Reacted by huiqiang_sd
9. Wouter125

   closed this as completedon Feb 15, 2020