Bumping up this thread as pagination does not solve client cases where all
tasks must be pulled for evaluation. Example: SLA commands in aurora_admin.
I would like to explore the #2 idea proposed by David and subsequently
outlined by Bill/Suman.
Specifically, I am proposing to add an optional for
Hi,
Mark suggested that I ask here for help too. I am trying to use
TFileTransport between Java and Python to wrap Suro's Java logging client.
While I can use TJSON and TBinary in Python with no troubles (for both
writing to a file and reading from it), it has been problematic to read the
file co
Hi,
The documentation only refers to the aurora client and a read-only Web UI. I
was wondering if there was a REST/HTTP API available for clients to create
jobs, etc?
Thanks,
Lili
Short answer: no
There's officially a Thrift API which is used by the Web UI. Someone at
PayPal implemented a REST API in a forked repository, check it out:
https://github.com/smarth-madan/incubator-aurora
Regarding this functionality, I am also an interested party. One might
consider contributi
Small correction. TBase does not support lookup by field names, so the
format would have to be a list of field IDs:
// Defines a set of thrift paths to be populated when returning
ScheduledTasks.
// Single path format is a list of valid field IDs representing thrift
query path.
// Valid examples:
At the moment, we do not have any kind of API for end-users.
It's something that we'd probably like to have in the future, but for now,
getting the command-line tools working correctly is more important to us.
Any API that we implemented now would be changing so rapidly that it
wouldn't be useful
Thank you for your responses. I will look into the work being done by paypal.
An API would make it easier for 3rd parties to integrate versus calling a
client which would require parsing of the output from the client.
Lili
- Original Message -
From: "Mark Chu-Carroll"
To: dev@aurora.
