Ah yes...I think the example needs the collections beforehand (i.e. it only 
imports the data and doesn't create the collections).

Please create a profiles (document) and a relations (edge) collection.

Sorry...Been a while I have been using this. Maybe it is a better idea to 
create the collection in the import script ;)

Am Donnerstag, 16. Februar 2017 16:36:37 UTC+1 schrieb Feng Wang:
>
> hi , thanks for your help and I did as you write :creating a job with the 
> following JSON:
> and got filed job run state....
>
>
>
> {
> "id": "pokec-import",
> "run": {
>   "cmd": "/import.sh tcp://10.2.0.141:1026 <http://10.0.2.11:1026/>",
>   "cpus": 1,
>   "mem": 128,
>   "disk": 0,
>   "docker": {
>     "image": "arangodb/pokec-import"
>   }
> }
> }
>
>
> here is my endpoint pic:
>
>
> <https://lh3.googleusercontent.com/-FjUkea8Kizk/WKXGzQFsN2I/AAAAAAAACmU/F9XILjCAwLINMnAZxLt7Efe5amMCpF9cgCLcB/s1600/Selection_009.png>
>
>
>
>
>  Is there any thing wrong with my job json??
>
>
> 在 2017年2月16日星期四 UTC+8下午11:00:06,[email protected]写道:
>>
>> Hi,
>>
>> these are the internal IP addresses of the coordinators. To do an import 
>> I would recommend deploying a job to DC/OS.
>>
>> Here is an example we are using internally:
>>
>> https://github.com/arangodb-helper/pokec-import
>> https://hub.docker.com/r/arangodb/pokec-import/
>>
>> You can deploy it via the Jobs tab in DC/OS by creating a job with the 
>> following JSON:
>>
>> {
>>   "id": "pokec-import",
>>   "run": {
>>     "cmd": "/import.sh tcp://10.0.2.11:1026",
>>     "cpus": 1,
>>     "mem": 128,
>>     "disk": 0,
>>     "docker": {
>>       "image": "arangodb/pokec-import"
>>     }
>>   }
>> }
>>
>> Please adjust the endpoint in the cmd to your needs :)
>>
>> This is more or less the quick and dirty way because we are hardcoding 
>> the coordinator. We have created a small tutorial on how we would build a 
>> fully resilient application on DC/OS using ArangoDB as its backend:
>>
>> https://docs.arangodb.com/3.1/cookbook/Cloud/DcosFullExample.html
>>
>> In this setup you would use
>>
>> tcp://arangodb-proxy.marathon.mesos:8529
>>
>> as the endpoint and not have to care about a specific arangodb endpoint.e
>>
>> Hope that helps!
>>
>> Kind regards,
>>
>>   Andreas Streichardt
>>
>> Am Donnerstag, 16. Februar 2017 15:55:37 UTC+1 schrieb Feng Wang:
>>>
>>> Hello community,
>>>    I have install ArangoDB3 in DC/OS , and the STATE is 'Healthy' . I 
>>> open the service and the panel like this:
>>>                  
>>>
>>>
>>> <https://lh3.googleusercontent.com/-tGfjLVFnGrw/WKW9LuWV_CI/AAAAAAAACmE/bMzQDbI82noLy2gwPVUb4mQbWm70SBmbACLcB/s1600/Selection_008.png>
>>>
>>>
>>> I also run 'docker ps'  on both two Endpoints,and see some images are 
>>> running such as :
>>> arangodb/arangodb-mesos:3.1....master.mesos:5000/arangodb/arangodb-mesos-framework:3.1-build1
>>>
>>> I want to know :
>>> 1. how can I use arangoimp to import data
>>> 2. which docker image process should I attach.
>>>
>>> thx
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"ArangoDB" 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.

Reply via email to