Thanks Curtis...I tried plocal 1st...then remote. Both fail to login to an existing database. Had to bail on ETL and brute force create a batch of sql scripts.
On Monday, December 22, 2014 6:04:38 AM UTC-7, Curtis Mosters wrote: > > Afaik ETL does not work properly with Remote. Try plocal. > > Am Sonntag, 21. Dezember 2014 02:59:20 UTC+1 schrieb Erik Peterson: >> >> Still no luck on my end...any progress on yours with this? Your question >> is curious...are there known issues with ETL on an existing database? >> Because it works with a new db, but fails to login on an existing one. >> >> >> On Thursday, December 18, 2014 5:14:01 AM UTC-7, Lvc@ wrote: >>> >>> Hi Erik, >>> Could you attach also the error message? >>> >>> Do the database exists? >>> >>> Lvc@ >>> >>> >>> On 18 December 2014 at 12:46, Erik Peterson <[email protected]> wrote: >>>> >>>> I've tried admin and root user/password combinations but ETL continues >>>> to fail to login. >>>> >>>> ... >>>> "loader" : { >>>> "orientdb": { >>>> "dbURL": "remote:localhost/xxxx", >>>> "dbUser": "admin", >>>> "dbPassword": "xxxx", >>>> "dbAutoCreate": true, >>>> "tx": false, >>>> "batchCommit": 1000, >>>> "dbType": "graph" >>>> } >>>> } >>>> } >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "OrientDB" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
