Why is the Elasticsearch REST API for search and view data via port 9500* returning only 10 records? Is there a maximum number that controls this?
http://localhost:9500/*/_search?q=module:"login"
*https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/analyt
ics/elasticsearch/
Since analytics is based on the elasticsearch, to the query you need to add the additional parameter &size=100000 to the url.
Example:
http://localhost:9500/_search?size=100000
Related
I want to connect REST API from QlikView and create chart/table view based on the JSON response from the REST call.
Instead of connecting MySQL datasource and database Is it possible to connect REST API and get the JSON and then generate chart/table view?
yes you need to download and install Qlikview Rest connector from downloads in Qlikview support page https://us-d.demo.qlik.com/download/.
Here is direct link to latest version 2.11 https://da3hntz84uekx.cloudfront.net/RESTConnector/2.11/0/_MSI/QlikRestConnector_setup.exe
I just created an API on APIC, but when I search APIs it doesn't show up in the search. Any idea why or where I can find the API I just created?
Try searching for the product. Then you can search through the product's API's and it should be there.
In Worklight v6.1, analytics search view has "contextual search". It runs a new search that will return events that occurred in the same time frame. This is useful for trouble shooting of fatal or error logs.
In MFP Foundation v7.0, I see just "Download all logs for this device". It's tough to find related events.
Does MFP Foundation the have same function? If not, is there any way to run similar search?
It seems I should change my question more specifically.
In the analytics 7.0 console, it seems we can limit the logs only by date. Is there any way to limit the logs by minute?
In the analytics 7.0 console you can go to the search tab. There you can search on client logs or server logs. For client you have the option to filter on keywords, application, environment, level, packages, and date range. For server you can filter on keywords, server, level, and date range.
Seems like contextual search is mostly just find your error and put in the date range to limit the logs.
You can submit request for enhancements at https://developer.ibm.com/mobilefirstplatform/help
We're building an app that analyzes twitter feed using streaming api. But it will only start analyzing after app starts. We need to download historical twitter data using API to initialize our system.
As per documentation twitter API only has until query parameter.
Is there a way to download /keep downloading the twits for given keyworkds with from to dates ?
We're using python.
As per documentation twitter API, query method that you mentioned provides "since_id" parameter. If you want to keep downloading tweetsas they come then use "until" parameter for first time n then "since _id" whenever you want to update
I'm currently working on a Worklight Project that deals with location based services. I want to be able to get the ZipCode of an user's current location for the iOS platform specifically. I researched online and there are many ways to approach this. I currently have it implemented using a custom cordova plugin using native location manager features and retrieve the zip code through reverse geocoding. This approach seem like I'm doing it the long way. I noticed that google provides an api call for the reverse geocoding by just supplying the lat and long. However, there is a limit to how many calls you can make.
Users of the free API:
2,500 requests per 24 hour period.
10 requests per second.
Maps for Business customers:
100,000 requests per 24 hour period.
10 requests per second.
This app needs to have no restrictions on how many times it can get the location based on zip code.
Does Worklight have a simpler or better way of getting the zip Code for user's location(I've checked the worklight api reference calls but didn't see anything about retrieving user's zip code)?
Worklight provide a way to implement this by using adapters, but not the API itself. Although you could the adapter to work as something like a local cache of the ZIP you already know.
To save money due to the APIs that would be usually based on a number of calls, we would need to have some cache, database(more likely: CouchDB or mongoDB) to handle this cache of what you already know.
A mobile(app-side) solution + a server side solution. On putting this 2 together, worklight would help you.