You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current date indexing system involving the creation and maintenance of a org.nunaliit.date_clusters document and couchdb date-index view is falling over when the number of documents containing nunaliit date objects gets high (~20,000+).
This issue is to track an evaluation and redesign effort.
The text was updated successfully, but these errors were encountered:
After investigating the code it appears that the servlet and this table are used for searching dates from the search (magnifying glass) and no where else that I can find.
Thanks @billingb. Any thoughts on how to refactor to avoid requiring this enormously deep JSON document while keeping the functionality? I imagine that the function may also be used by some atlases within custom timeline widget code.
One possibility might be to revisit search now that we are on CouchDB 2.x. I believe there is more there now than there was when the original search index views and code were written.
I checked the custom timeline code I could find and didn't see any network calls for the date servlet. It is possible I'm missing them but I couldn't find them. I think the timeline widget does the filtering browser side.
I'm looking into the JSON document (which is really a serialized tree). It seems to produce a view and I'm looking to see how else we can do that.
The current date indexing system involving the creation and maintenance of a
org.nunaliit.date_clusters
document and couchdbdate-index
view is falling over when the number of documents containing nunaliit date objects gets high (~20,000+).This issue is to track an evaluation and redesign effort.
The text was updated successfully, but these errors were encountered: