Elastic.SemanticKernel.Connectors.Elasticsearch/ElasticsearchVectorStoreRecordCollection.cs (11 lines):
	- line 57: /// <summary>TODO: TBC</summary>
	- line 100: VectorStoreRecordPropertyVerification.VerifyGenericDataModelKeyType(typeof(TRecord), false /* TODO: options?.CustomMapper is not null */, SupportedKeyTypes);
	- line 200: // TODO: Handle options
	- line 222: // TODO: Use mget endpoint
	- line 223: // TODO: Handle options
	- line 243: // TODO: Handle options
	- line 257: // TODO: Use _bulk endpoint
	- line 258: // TODO: Handle options
	- line 272: // TODO: Handle options
	- line 292: // TODO: Use _bulk endpoint
	- line 293: // TODO: Handle options


Elastic.SemanticKernel.Connectors.Elasticsearch/MockableElasticsearchClient.cs (5 lines):
	- line 23: #pragma warning disable CA1852 // TODO: Remove after using MockableElasticsearchClient in unit tests
	- line 213: ///     TODO: TBC
	- line 249: /// TODO: TBC
	- line 280: /// TODO: TBC
	- line 321: #pragma warning restore CA1852 // TODO: Remove after using MockableElasticsearchClient in unit tests


Elastic.SemanticKernel.Connectors.Elasticsearch/ElasticsearchVectorStoreCollectionSearchMapping.cs (4 lines):
	- line 101: /// TODO: TBC
	- line 108: // TODO: Implement FieldValue.FromValue() in Elasticsearch client
	- line 109: // TODO: FieldValue.Any()
	- line 110: // TODO: FieldValue.Array()


Elastic.SemanticKernel.Connectors.Elasticsearch/ElasticsearchVectorStoreOptions.cs (1 line):
	- line 12: // TODO: Do we want to support a prefix here that is used to filter collections/indices (and automatically prepend when creating a collection, etc.) or is that something that should be up to the user?