Clusters don't allow querries to continue to execute on failover. A cluster failover means the instance starts again from a cold state, runs pending recovery on all databases and puts them online on the new node. All clients are disconencted, all pending transactions rolled back, all running querries aborted. Clients have to reconnect and resume from the last commited transaction.
BTW this also applies to Mirroring. The only technology that abstracts transparently the failover event so that applications don't notice the incident is messaging based, eg. Service Broker, because all work is first commited locally and delivered asynchronously to the cluster/mirror, but this does not apply to the vast majority of applications.