volkswagen | Volkswagen behaves differently under CI and in prod

You need .skip() and .limit().

Take the document by starting index: 2 and with only 1 document, which is the third document.

Update: Thanks and credit to @Wernfried for pointing out, you need .sort() to guarantee to get the nth of the document. For your scenario, you have to sort by car_id.

Sort Consistency

MongoDB does not store documents in a collection in a particular order. When sorting on a field that contains duplicate values, documents containing those values may be returned in any order.

Because this.vehicles is filled asyncronously, that's how .subscribe() works. When your ng-select is rendered, this.vehicles does not contains your api response.

A simple way to handle this :

html :

First, assuming there are really not blank lined in between each line of data in data.csv, all you need is sort, you don't need awk at all. For example, since there is only ':' before the total score you want to sort descending by, you can use:

The main probelm seems to be in

You should iterate over dictionaries and accumulate the items inside temporary dictionary with names as a keys and values as dictionary of cars from make to dict of cars, and finally we convert this dictionary to our desired dictionary:

You can use string interning to ensure that each duplicate string points to the same memory.

Otherwise, if you create 1,000,000 Strings and set them to the value "Ford", you have created 1,000,000 copies of the bytes composing "Ford" in memory.

Thanks to pringi for asking the question. After pringi's question I checked my saving method:-

facets added to a query doesn't work that way. It will simply return the record count for each facet value, not the actual records (https://www.algolia.com/doc/api-reference/api-parameters/facets/)

You can create filters around facets and use those to display results by facet value, but there isn't a way to build a single response JSON that is already grouped by facets like you show above. https://www.algolia.com/doc/api-reference/api-parameters/filters/

With the hints from the comments, I was able to resolve the issue. The problem is that Clojure records do not implement the JavaBeans spec, while the JRBeanCollectionDataSource expects such beans.

With the clj-bean library, I was able to make it work.