OpenSearch Dashboards Search in “Discover” tab does not works - kibana

Search in “Discover” tab does not works.
I’m searching for some word and got an error.
I tried to switch between DQL and Lucerne, the result is the same.
Currently the only thing that solves the issue is to delete the index and create it again but it's not ideal solution.
I wonder if anyone know better solution for that
Thank you.
Here is the error i got:
Error:Bad Request
OpenSearch log

Related

Pagination of data in Flutter with Firebase

I'm writing an app with a database of users. I want to show these to people on the app, and as such, in order to limit the download of data, I'm using the standard Firebase pagination concept:
.startAtDocument(lastDocumentSeen)
The problem is, I have no idea what actually happens when the 'read head' gets to the end of the database? Does Firebase/Flutter loop back and start to look at the top of the database again? If not, how does it signal to me that I've reached the end?
I've done quite extensive googling about this, and searched StackOverflow too, but can't seem to find any clear answers - does anyone know?
Assuming you have a query like this:
collectionRef.orderBy("something").startAfter(cursor).limit(10)
If there are not enough documents to return 10 results, Firestore will simply return however many documents are left. It does not perform any tricks beyond that.
You can use fetch_more package for pagination, it’s easy to use. You can see an example in the Example tab.
https://pub.dev/packages/fetch_more

Freebase with own data?

I have been looking for an autosuggest search script and I have finally found one that I like, the only problem is that I cannot find a way to get it to run off our database results.
Is there any way to customize this script so that it runs from our own database, and not off the freebase pre-defined data types?
http://www.freebase.com/docs/suggest
Have you tried overriding service_url and service_path ? There are also the corresponding params for the flyout service. It's documented in the docs that you pointed to.
As masouras says, you can override service_url and service_path, but that's not particularly helpful unless you have another service which provides the same APIs as Freebase.
Dae Park recently posted a recipe to the Freebase mailing list which might help - however, I'm not aware of anyone who's actually managed to get Suggest working with anything other than Freebase.

Basic querying in freebase

I am tinkering with Freebase, and trying things with the query editor and everything looks great. I'm still reading the fine manual, but can't seem to get the point if this may be used as a web search replacement for showing refined data to the user. The main question is:
If {q1, q2, q3 ....} be the query the user submits - how do I programatically map each query term to the freebase query key:value pair?
I am not sure if it can entirely replace the current search engines as of now.I have just written a blog post for handling a basic query(more will follow) in C# for freebase.
http://2guysfrommumbai.wordpress.com/
If you like the java stuff you can go to,
https://github.com/narphorium/freebase-java-api
this is a more complete api,and i have used it with good success.
You can append multiple queries using q1,q2,q3 as parameters,more details are available on the freebase developer site.
Hope this helps.

Able to get Facebook comments with FQL and Graph App but both present a problem

I am working on a little mobile app for facebook and have been studying the Facebook Api's for weeks now.
My problem I need help with is comments, I have my app retrieving them via post_id/comments?access_token=**&limit=10 but the problem with this way is that the comments are being sent oldest first, so if i wanted to get the newest comments and there were 200 comments i'd have to call the api because of pagination 19 times to get the most recent. Is there any way of telling the graph api to send the newest comments first? I really want to avoid having to get all the comments at once just to sort them myself - sometimes there are over 2000 comments.
I did a little experimenting with fql last night and found I was able to specify ORDER BY time in the query and also LIMIT and less than time to do my own kind of pagination. The problem with this way is that the person name (who had made the comment) isn't returned, only an id for that person. Please correct me if im wrong but that would then mean having to make a call to the api to find out the name of the commenter for each comment made on a post - again sometimes over 2000. I think this is not a solution for mobile.
I just want my app to show comments newest first. Please can any one of any advice?
Regards
http://developers.facebook.com/docs/reference/rest/fql.multiquery/

Bugzilla: How to get an rss feed for bug comments?

I can see where to get an rss feed for the BUG LIST, however I would like to get rss updates for modifications to current bugs if possible.
This is quite high up when searching via Google for it, so I'm adding a bit of advertisement here:
As Bugzilla still doesn't support this I wrote a small web service supporting exactly this. You can find its source code here and a running instance here.
What you're asking for is the subject of this enhancement bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=256718
but no one seems to be working on it.
My first guess is that the way to do it is to add a template somewhere like template/en/default/bug/show.atom.tmpl with whatever you need. Put it in custom or an extension as needed.
If you're interested in working on it or helping someone with it, visit channel #mozwebtools on irc.mozilla.org.
Not a perfect solution, but with the resolution of bug #255606, Bugzilla now allows listing all bugs, by running a search with no criteria, and you can then get the results of the search in Atom format using the link in the bottom of the list.
From the release notes for 4.2:
Configuration: A new parameter search_allow_no_criteria has been added (default: on) which allows admins to forbid queries with no criteria. This is particularly useful for large installations with several tens of thousands bugs where returning all bugs doesn't make sense and would have a performance impact on the database.

Resources