Import Your CSV and JSON Data to NodeChef

188 views
Skip to first unread message

NodeChef

unread,
Aug 23, 2016, 10:13:59 PM8/23/16
to NodeChef
Here at NodeChef, we're always looking for ways to make it easier to import your data. Today we're happy to announce that we're rolling out a new feature called NodeChef ETL Designer. NodeChef ETL Designer lets you import your CSV and JSON data with just a click of a button. The NodeChef ETL feature supports number, Boolean, string, date, and GeoPoint formats for any column.

You can read more about importing data with the NodeChef ETL Designer in the documentation.

ad...@tillify.com

unread,
Aug 31, 2016, 6:23:24 AM8/31/16
to NodeChef

I have a development set-up on nodechef, app + mongo db, i transfered this from Parse. I now need to create a production deployment. How can i create a new account and copy the mongo db set-up: don't need data just schema to the new app?

dev.no...@gmail.com

unread,
Aug 31, 2016, 10:56:50 AM8/31/16
to NodeChef, ad...@tillify.com
Currently you can clone the other database using the database import tool. This will copy the data and schema over. You currently cannot copy just the schema

ad...@tillify.com

unread,
Sep 1, 2016, 4:33:45 AM9/1/16
to NodeChef, ad...@tillify.com, dev.no...@gmail.com
If we want to add some feature so that the user of our app can say upload a csv of their contacts, how is the best way to insert the data into the mongo/parse db, how did you do this with the mentioned csv importer? Are you using parse batch insert objects or are you doing this directly with mongo api. Need help with this.

dev.no...@gmail.com

unread,
Sep 1, 2016, 10:07:52 AM9/1/16
to NodeChef, ad...@tillify.com, dev.no...@gmail.com
This is custom developed. If you want an API to import for your clients, we can provide that as well. That is already in place, we just have to give you a way to authenticate to this API.

The workflow will be something of this sort.

1. Get your client to upload file. You can store this file also as a temporary file on your container. Each container has a temporary directory with name /tmp.

2. Call the api with and specify the url of this file pointing to the container which you uploaded to. Note if you have multiple containers you will have to specify the container Id as well which you can retrieve from the environment variable process.env.NC_CONTAINER_ID

When the api becomes available there will be a step by step guide how to do this.

naray...@avazapp.com

unread,
Aug 8, 2017, 2:18:04 PM8/8/17
to NodeChef
I have been trying to do a database upload of a JSON file into the User table via the website - but it does not seem to upload.
It has about 1000 rows, and it does not insert into the User table. Neither do I get to see any logs etc.
When I upload about 5 rows of the same file, it works fine. The file size is less than 600KB. Could you tell me if can see logs of this error? Or is there limit upto how many rows are inserted.  Below is the selection that I do. 
Can you please guide as to how to diagnose the problem?

Auto Generated Inline Image 1

dev.no...@gmail.com

unread,
Aug 8, 2017, 2:26:01 PM8/8/17
to NodeChef, naray...@avazapp.com
Select the collection is a Parse server class option as well and preview the data and then attempt the import. If you do not select this option, the data loaded into the table will be incorrect.

naray...@avazapp.com

unread,
Aug 9, 2017, 2:44:20 AM8/9/17
to NodeChef, naray...@avazapp.com, dev.no...@gmail.com
If I select that option - is a Parse server class - it changes the CreatedAt and UpdatedAt fields.
How do I avoid that? Is there a way that I can do this upload from the command line or a REST API, instead of the web interface.

in...@nodechef.com

unread,
Aug 9, 2017, 9:59:15 AM8/9/17
to NodeChef, naray...@avazapp.com, dev.no...@gmail.com
You can build your own tools to use the REST API. Currently the only tools provided by us is the web interface. The CreatedAt and UpdatedAt fields are just simply transformations done by the parse server at run time, the data actually has to be stored in mongo as _created_at and _updated_at. This is why the tool changes those fields.
Reply all
Reply to author
Forward
0 new messages