Skip to content

Will data import be supported? #550

Closed

Description

@zh-wowtv

I'm wondering if data import be supported?

If not, how am I supposed to migrate my current data to my parse-server? Thanks.

Activity

  1. markmssd commented on Oct 5, 2016

    @markmssd

    By following their migration guide: https://parse.com/migration.
    Every step of the process is clearly explained.

  2. zh-wowtv commented on Oct 5, 2016

    @zh-wowtv
    Author

    I don't think it covers what I want. It doesn't explain how to export data and how to import the data into new database.

  3. markmssd commented on Oct 5, 2016

    @markmssd

    It doesn't explain that explicitly, because it does it for you automatically. In your app settings on parse.com, when you specify your new Mongo URI, it will transfer all your data to that database.

    https://parse.com/migration#database

    Is there a reason why you need to manually export your data then import it in your DB, instead of using their tool?

  4. zh-wowtv commented on Oct 5, 2016

    @zh-wowtv
    Author

    Thanks for your reply. There are two reasons I tried to manually export/import.

    1.I tried this. But didn't work.

    Since I'm using Openshift so I use port-forward to get the port of mongodb.

    2016-10-06 1 04 58

    I created a db called test in this mongodb through MongoHub.

    2016-10-06 1 06 43

    Got the following error message:

    2016-10-06 1 07 07

    2.The new dashboard doesn't have a "Migration" option so that I can't use this in the future if I want to migrate to another Mongodb.

    Any idea? Thanks.

  5. zh-wowtv commented on Oct 7, 2016

    @zh-wowtv
    Author

    @mamaso Any idea why the migration doesn't work for me? Thanks.

  6. mamaso commented on Oct 10, 2016

    @mamaso

    Just a quick look, but I'm assuming it has to do with your port forwarding.

    You're migrating from the dashboard on parse.com, correct? You won't be able to connect to mongodb://127.0.0.1:60691/test because that's localhost. You'll need to use your external ip address so that parse.com can locate the db.

  7. zh-wowtv commented on Oct 11, 2016

    @zh-wowtv
    Author

    @mamaso I think you misunderstood. The connection is through port forwarding so that it's not connected locally. That's how Openshift works. And I have no problem to connect to mongodb://127.0.0.1:60691/test through a mongo GUI app like MongoHub. (Openshift doesn't allow to connect through external ip address).

  8. zh-wowtv commented on Oct 18, 2016

    @zh-wowtv
    Author

    Any idea for this problem?

  9. SaifAlDilaimi commented on Oct 24, 2016

    @SaifAlDilaimi

    @zh-wowtv you need to use the Openshift address that is forwarding to 127.0.0.1:60691

    It's 10000% not possible to use mongodb://127.0.0.1:60691/test from a external host. As @mamaso said you are trying to connect to localhost and not your openshift endpoint.

    8852d16a-8b61-11e6-8cc8-2ee913d67d55

  10. zh-wowtv commented on Oct 24, 2016

    @zh-wowtv
    Author

    @deada92 I'm also confused but I'm 100% sure I can use 127.0.0.1:60691 to connect to my mongdb in Openshift through MongoHub. Openshift doesn't allow to use other ip address to connect and only allow to connect through localhost.

  11. arakwar commented on Oct 26, 2016

    @arakwar

    @zh-wowtv this isn't how networking works. 127.0.0.1 means "localhost". So when you give this address to the Parse Dashboard at Parse.com, you are telling him to connect to his localhost. If you want to ask to Parse.com to connect to your database, it has to use an address he can find, and 127.0.0.1 is not that one. You have to use your public IP.

  12. zh-wowtv commented on Oct 27, 2016

    @zh-wowtv
    Author

    @MEMSIS @deada92 Sorry, I have the same idea at first. But do you know Openshift well?

    Of course I can't connect through localhost to Openshift directly. But I can connect to localhost after I run the Openshift's port forwarding command. I guess my connection to this port in localhost will be forwarded by Openshift's command to remote mongodb in Openshift. That's why I can connect to Mongodb through Mongohub App in this way. But I don't know why I can't do the same thing through 'Migrate App' in parse.

    By they, I can get the url of mongodb in openshift but I can't connect to it directly because I guess Openshift doesn't allow this for security reason.

    Does anybody have any experience on how to migrate data to Openshift? Thanks.

  13. arakwar commented on Oct 27, 2016

    @arakwar

    No, it's because the URL you type in the parse migrate tool is run by the
    parse server, which is not linked to your openshift port forwarding.

    On Thursday, 27 October 2016, zh-wowtv notifications@github.com wrote:

    @MEMSIS https://github.com/memsis @deada92 https://github.com/deada92
    Sorry, I have the same idea at first. But do you know Openshift well?

    Of course I can't connect through localhost to Openshift directly. But I
    can connect to localhost after I run the Openshift's port forwarding
    command. I guess my connection to this port in localhost will be forwarded
    by Openshift's command to remote mongodb in Openshift. That's why I can
    connect to Mongodb through Mongohub App in this way. But I don't know why I
    can't do the same thing through 'Migrate App' in parse.

    By they, I can get the url of mongodb in openshift but I can't connect to
    it directly because I guess Openshift doesn't allow this for security
    reason.

    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub
    #550 (comment),
    or mute the thread
    https://github.com/notifications/unsubscribe-auth/ACktf6i-Et6ksM5NasZOGPc9SRFlljQ0ks5q4HjYgaJpZM4KOgN1
    .

    Envoyé avec mon Iphone

  14. zh-wowtv commented on Oct 28, 2016

    @zh-wowtv
    Author

    Then I have two questions.

    • Why I can connect to Openshift MongoDB through http://127.0.0.1:60691/test by MongoHub app?
    • And does this mean there is no way to connect to Openshift MongoDB in Parse Migration Tool because Openshift only allow to connect to localhost?
  15. arakwar commented on Oct 28, 2016

    @arakwar

    As I can see from it's website, it is executed locally, on your own
    computer. The Parse platform is not executed locally on your own computer.
    So when the Parse platform try to find their "localhost", it points them to
    their own servers.

    You have to get the public IP of your Openshift installation. This is the
    IP to use. For any computer or server, 127.0.0.1 means "myself". It is the
    same for the Parse platform, giving them 127.0.0.1 means he'll try to
    connect to itself, and not to your Openshift installation or your computer.


    Sébastien Lemieux

    2016-10-27 21:14 GMT-04:00 zh-wowtv notifications@github.com:

    Then I have two questions.

    • Why I can connect to Openshift MongoDB through
      http://127.0.0.1:60691/test by MongoHub app?
    • And does this mean there is no way to connect to Openshift MongoDB
      in Parse Migration Tool because Openshift only allow to connect to
      localhost?

    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub
    #550 (comment),
    or mute the thread
    https://github.com/notifications/unsubscribe-auth/ACktfyDRoBU9nzRypBzsFJtLG3CD3JVYks5q4UyDgaJpZM4KOgN1
    .

  16. zh-wowtv commented on Oct 28, 2016

    @zh-wowtv
    Author

    @MEMSIS Yes, your explanation make sense. Maybe I can try to run parse server in my local.

    I've tried the public IP of Openshift already. It's not working because Openshift doesn't allow that.

    Thank you anyway.

  17. stale commented on Jan 11, 2019

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  18. added and removed
    state:wont-fixWon’t be fixed with a clearly stated reason
    on Oct 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions