I currently have a project with the following collections / arrays:
Data centers - id, city
Accounts - id, name
Traffic - datacenter, account, mbps
I wanted to merge all three of these collections together so that for a given account I could find all data centers where traffic was delivered, or for a given data center I could find all accounts delivering traffic:
This failed because even though traffic was indexed on account, the merged collection did not have this index.
Retaining these indexes may hurt the performance of merging somewhat, but will enable changed merges like this. Because of the possible performance hit, I may consider making it an option:
This way people can opt in (or out if I make it a default) depending on whether they need this functionality.
Whichever solution I choose, this isn't a breaking change (just a new option and a modification to the implementation) so it will only be a bump to 0.1.1 or similar.
I currently have a project with the following collections / arrays:
id
,city
id
,name
datacenter
,account
,mbps
I wanted to merge all three of these collections together so that for a given account I could find all data centers where traffic was delivered, or for a given data center I could find all accounts delivering traffic:
This failed because even though
traffic
was indexed onaccount
, the merged collection did not have this index.Retaining these indexes may hurt the performance of merging somewhat, but will enable changed merges like this. Because of the possible performance hit, I may consider making it an option:
This way people can opt in (or out if I make it a default) depending on whether they need this functionality.
Whichever solution I choose, this isn't a breaking change (just a new option and a modification to the implementation) so it will only be a bump to
0.1.1
or similar.