Problem with "$lookup"? about meteor-reactive-aggregate HOT 5 CLOSED

@thearabbit

collection.js

Posts = new Mongo.Collection('posts')

Meteor.isServer && Meteor.publish('posts', function() {
  // ReactiveAggregate(this, Posts, [{
  //   $lookup: {
  //     from: 'users',
  //     localField: 'userId',
  //     foreignField: '_id',
  //     as: 'user'
  //   }
  // }])

  return [Posts.find(), Users.find()]
})

client.js

Template.registerHelper('posts', function () {
  return Posts.find().map(post => {
    return _.extend(post, {
      user: Users.find(post.userId)
    })
  })
})

from meteor-reactive-aggregate.

Thanks for your reply.
Could example?

from meteor-reactive-aggregate.

@JcBernack - Is there any way to get reactivity of collection used by $lookup? I'm in a situation that I cannot use your above proposed solution that "publish other collections and join them on client side". Because of the huge amount of data in the other collection I cannot publish them. At the same time I need to aggregate with that collection data. Your suggestions would be very much appreciated

from meteor-reactive-aggregate.

This package observes changes in the given collection (Disbursement) and updates the aggregation. Changes to the collection used by $lookup will go unnoticed. Maybe you should push the other collections via separate publications and "join" on the client side.

from meteor-reactive-aggregate.

@crapthings

Thanks for posting this example. The reduction and flexibility of my code changes in relation to publications (publish composite, reactive join aggregations), coupled using react-komposer, simply exquisite. Fair amount of unbounded arrays requiring aggregations, so denormalizing was not a very good option (or really much of an option at all). This solved a ton of problems and helped me think of a couple of new ways to do things. Thanks again!

from meteor-reactive-aggregate.