Find items whose "name" field equals "ant-1.9.4.jar"
Regular notation
items.find({"name":{"$eq":"ant-1.9.4.jar"}})
Short notation
items.find({"name":"ant-1.9.4.jar"})
example
// find items whose "name" field matches the expression "*test.*"
items.find({"name": {"$match" : "*test.*"}})
// find items that have been downloaded over 5 times.
// we need to include the "stat" specifier in "stat.downloads" since downloads is a field of the stat domain and not of the item domain.
items.find({"stat.downloads":{"$gt":"5"}})
// find items that have never been downloaded. note that when specifying zero downloads we use "null" instead of 0.
// we need to include the "stat" specifier in "stat.downloads" since downloads is a field of the stat domain and not of the item domain.
items.find({"stat.downloads":{"$eq":null}})
// find builds that use a dependency that is a snapshot
builds.find({"module.dependency.item.name":{"$match":"*SNAPSHOT*"}})
AQL supports specifying time intervals for queries using relative time. In other words, the time interval for the query will always be relative to the time that the query is run, so you don't have to change or formulate the time period, in some other way, each time the query is run. For example, you may want to run a query over the last day, or for the time period up to two weeks ago.
relative time is specified using the following two operators:
OPERATORS
PARAPHRASE
$before
The query is run over complete period up to specified time.
$last
The query is run over period from the specified time until the query is run
Time periods are specified with a number and one of the following suffixes:
// sort by created timestamp
items.find(
{"repo" : "repo-name"},
{"path" : {"$match":"path/to/folder*"}},
{"name" : {"$match":"name-*.json"}}
).include( "repo","path","name","created","updated","actual_md5","actual_sha1" )
.sort({"$desc":["created"]})
.limit(1)
find and pagination (sort and limit)
// run the same example, but this time, display up to 50 items but skipping the first 100
items.find({"name" : {"$match":"*.jar"})
.sort({"$asc" : ["repo","name"]})
.offset(100)
.limit(50)
// Find all items, and display the "name" and "repo" fields as well as the number of "downloads" from the corresponding "stat" entity
items.find().include("name", "repo", "stat.downloads")
// Find all items, and display the default item fields fields as well as the stat fields
items.find().include("stat")
// Find all items, and display the default item fields as well as the stat and the property fields
items.find().include("stat", "property")
// Find all items, and display the "name" and "repo" fields as well as the stat fields
items.find().include("name", "repo", "stat")
// Find all builds that generated items with an Apache license, and display the build fields as well as the item "name" fields. Click below to view the output of this query
builds.find(
{
"module.artifact.item.@license":{"$match":"Apache*"}
}
).include("module.artifact.item.name")
call aql via CURL
running via curl -d
-d, --data (HTTP MQTT) Sends the specified data in a POST request to the HTTP server, in the same way that a browser does when a user has filled in an HTML form and presses the submit button. This makes curl pass the data to the server using the content-type application/x-www-form-urlencoded. Compare to -F, --form.
--data-raw is almost the same but does not have a special interpretation of the @ character. To post data
purely binary, you should instead use the --data-binary option. To URL-encode the value of a form field
you may use --data-urlencode.
If any of these options is used more than once on the same command line, the data pieces specified are
merged with a separating &-symbol. Thus, using '-d name=daniel -d skill=lousy' would generate a post
chunk that looks like 'name=daniel&skill=lousy'.
If you start the data with the letter @, the rest should be a file name to read the data from, or - if
you want curl to read the data from stdin. Posting data from a file named 'foobar' would thus be done
with -d, --data @foobar. When -d, --data is told to read from a file like that, carriage returns and
newlines are stripped out. If you do not want the @ character to have a special interpretation use
--data-raw instead.
The data for this option is passed on to the server exactly as provided on the command line. curl does
not convert, change or improve it. It is up to the user to provide the data in the correct form.
--data can be used several times in a command line
Examples:
curl -d "name=curl" https://example.com
curl -d "name=curl" -d "tool=cmdline" https://example.com
curl -d @filename https://example.com
See also --data-binary, --data-urlencode and --data-raw. This option is mutually exclusive to -F, --form
and -I, --head and -T, --upload-file.
running via curl -T
-T, --upload-file This transfers the specified local file to the remote URL. If there is no file part in the specified URL, curl will append the local file name. NOTE that you must use a trailing / on the last directory to really prove to Curl that there is no file name or curl will think that your last directory name is the remote file name to use. That will most likely cause the upload operation to fail. If this is used on an HTTP(S) server, the PUT command will be used.
Use the file name "-" (a single dash) to use stdin instead of a given file. Alternately, the
file name "." (a single period) may be specified instead of "-" to use stdin in non-blocking
mode to allow reading server output while stdin is being uploaded.
You can specify one -T, --upload-file for each URL on the command line. Each -T, --upload-
file + URL pair specifies what to upload and to where. curl also supports "globbing" of the
-T, --upload-file argument, meaning that you can upload multiple files to a single URL by
using the same URL globbing style supported in the URL, like this:
curl --upload-file "{file1,file2}" http://www.example.com
or even
curl -T "img[1-1000].png" ftp://ftp.example.com/upload/
