user128779: From bitcoin magazine, I saw that

When Taproot/Schnorr goes live soon, they will use the new witness version one to distinguish them from older Segregated Witness transactions.

But when I check the type of inputs/outputs after Nov 14, I only see witness_v0_scripthash, witness_v0_keyhash, scripthash, multisig, nonstandard, witness_unknown and pubkeyhash.
Should the new taproot txns be labelled as witness_v1? or is there any other way to identify them on big-query?
Thanks

user47827: You clarified in the comments that you are using BigQuery datasets and so you are right Taproot transactions should eventually be labelled as witness_v1_.... Taproot only activated a couple of days ago at the time of writing so presumably the authors haven't added Taproot support yet. You can either wait for them to do so (or request they do!) or find an alternative SQL data source that has added Taproot support. If it is the latter feel free to ask a separate question on this site, I'm not familiar with any alternative SQL blockchain data sources.

128779: <p>From <a href="https://bitcoinmagazine.com/technical/bitcoin-taproot-explainer" rel="nofollow noreferrer">bitcoin magazine</a>, I saw that</p>
<blockquote>
<p>When Taproot/Schnorr goes live soon, they will use the new witness version one to distinguish them from older Segregated Witness transactions.</p>
</blockquote>
<p>But when I check the type of inputs/outputs after Nov 14, I only see witness_v0_scripthash, witness_v0_keyhash, scripthash, multisig, nonstandard, witness_unknown and pubkeyhash.</p>
<p>Should the new taproot txns be labelled as witness_v1? or is there any other way to identify them on big-query?</p>
<p>Thanks</p>
 47827: <p>You clarified in the comments that you are using <a href="https://cloud.google.com/blog/products/data-analytics/introducing-six-new-cryptocurrencies-in-bigquery-public-datasets-and-how-to-analyze-them" rel="nofollow noreferrer">BigQuery datasets</a> and so you are right Taproot transactions should eventually be labelled as <code>witness_v1_...</code>. Taproot only activated a couple of days ago at the time of writing so presumably the authors haven't added Taproot support yet. You can either wait for them to do so (or request they do!) or find an alternative SQL data source that has added Taproot support. If it is the latter feel free to ask a separate question on this site, I'm not familiar with any alternative SQL blockchain data sources.</p>
