Class table inheritance and eager loading bug

With class table inheritance, when eager loading is enabled on a relationship for a derived entity LightSpeed tries to eager load that relationship on other derived entities where the relationship doesn't make sense.

e.g. Event and Place entities both inherit from a common entity. When eager loading is enabled for Event.EventTickets LightSpeed still generates SQL to eager load from the EventTickets table even when loading Place entities.

When will you be looking at this bug?

It is not currently planned in.  What is the impact?

What I discribed in the first post. When I set a CTI's entity collection to be eager loaded the eager load SQL query redundently happens for every CTI entity even though it could never return a result. I'd like to use eager loading in some places and it is useless because it hurts rather than improves performance.

Yes, I understand that, but how significant is the performance impact?  If you perform with query with eager loading switched on vs. switched off, how much is the difference?  1%?  10%?  100%?

One workaround is to use a named aggregate, and include the aggregate when querying for a class that could include the association, and leave it off when querying for a class that could not include the association.  Ugly, of course, but could serve as an interim solution.

I don't know, I'm still building the website and I don't have a real life amount of data to test against.

At the moment I don't care while developing that there are the additional queries, I just need to know that it will be fixed in the future before the website goes live in the future. When will that be?

At a guess the table that will be eager loaded will have tens of thousands of rows at least (not all against the same entity of coarse) in the lifetime of the website.