...
Note that you can select either a single or multiple (CTRL+click) communities. You can share widgets with any available community. If you upload to only your personal community, only you (and system administrators) will have access to the file.
The "query" field has a few noteworthy points:
- It can be provided in 2 formats:
- A single JSON object containing a MongoDB query (see next bullet), eg "{ 'docGeo': { '$exists': false } }"
- An array of 2 JSON objects, the first of which is the above query object, the second of which controls the sorting and size of the output (see this tutorial for the format, under advanced topics).
- The aforementioned query must be a MongoDB query (use the /wiki/spaces/INF/pages/3899780), Infinit.e queries are not currently supported (this functionality is coming).
Note: If you set append results to false, there is no need to set an age out.
Note: If you don't want your job to depend on another jobs completion, do not select any job depenencies (you can CTRL-click to remove selected options if necessary).
Note: the "user arguments" field can be any string, it is interpreted by the code in the Hadoop JAR. For custom plugin developers: see this tutorial for a description of how to incorporate user arguments in the code (under advanced topics).
Scheduling a new Saved Query
...
- Leave JAR file blank
- Leave Mapper, Combiner, and Reducer class blank
- Submit a valid query for the query field, a good place to start is saving queries from the http://infinite.ikanow.com Gui under GUI under the Advanced -> Save option. These can be pasted into the query field. (Note unlike the normal map/reduce case, the query in this instance must be an Infinit.e query, not a MongoDB query).
Editing existing plugins/saved queries
...