If you think it is, send in a bug report. Bugs are always a possibility, but if you cannot describe the situation with the clarity and precision required for a responsible bug report, don't make the mistake of failing to consider the possibility that the problem might not be a bug but an error in concept or operation.
A strong indication that you might be jumping to conclusions is that in this thread you haven't mentioned what was done that generated those log messages. For example, if it's a query that was used, you haven't provided the query text that results in the log messages cited, or the schemas for what the query uses. You only cited the log messages. That seems to indicate that you might believe the query text has no errors, and instead troubleshooting should begin by assuming the log messages indicate an error in the system. If so, that's getting it backwards, as experience shows queries very frequently tend to have errors in them (typos, errors in concept, etc.) while bugs are very infrequent.
Just guessing here given the absence of info, but it seems to me the right path is to start by debugging the query, eliminating the possibility of errors in the query or in configuration, not by assuming what was done is perfect and thus the error must be in the system. There's always time once you eliminate the most likely source of errors to move on to less likely sources of errors.
It's no accident that the bug report page includes this advice:
users should not let the consideration of a possible bug lead them astray if they have encountered a problem. Few things are as effective at stopping the solutions process as deciding too early on that the problem must be a bug. Do not allow assumptions about a possible bug to prevent you from taking effective measures to solve problems.
Bugs are very rare. It is almost always a mistake to think that a problem arises from a bug and not from an error in concept or operation. If you have a problem, hit the books and apply your maximum RTFM skills.
But, like I say, bugs are always possible, so if you believe this is a bug it is important to send in a bug report. Doing a good job of sending in a bug report requires sending in the essential information you've not posted in this thread, such as the query you are using, the schemas of what is involved, versions of software you are using, and other essentials. That's not wasted effort, because frequently during the process of gathering those details people discover a mistake being made, and immediately solve the problem.