How is the data warehouse write operation calculated (total number of records) for a simple and complex query?

Question

I am working on a data warehouse application engine project (creating our database),

According to the information provided in this link, the total number of write read operations is indicated for different cases (insert, update and delete), but I am confused how the write operation is calculated to change the index and composite index.

we have a Case scenario below in which we must calculate the number of writes

1 -> Datastore query requires filtering based on a single property without a complex query [no index defined in datastore-indexes.xml file]

according to example "SELECT * FROM MESSAGE AS MESSAGE ORDER BY timestamp desc"

2 -> Datastore query requires filtering based on a single property without a complex query [index defined on one property in datastore-indexes.xml file ] as an example"SELECT * FROM MESSAGE AS MESSAGE ORDER BY timestamp desc"

3 → The Datastore query requires filtering based on a complex query [index defined for complex query defind in datastore-indexes.xml file ]  as an example "SELECT * FROM MESSAGE AS MESSAGE WHERE req_id =" xyz123 "ORDER BY timestamp desc"

Note :: for example, target: I accepted this statement "SELECT * FROM MESSAGE AS MESSAGE ORDER BY timestamp desc". This jpql request makes an HTTP get (1 read operation) request to retrieve data from the data store.

Question

For the script above the script, how will the write operation New Entity Put be counted? [New Entity Put "2 writes + 2 records per indexed property value + 1 record per composite index value"]

early!!!!

Answer 1

:

• 1
• 1 EntitiesByKind
• 2
• 1

, :

• 1 + 1 + 2 * ( )
• , # 1; datastore-indexes.xml, .
• 1 + 1 + 2 * ( ) + 1

.

Answer 2

• 2 + 2 * n ( : 1, ) + 0
• 2 + 2 * n ( : 1, ) + 1 ( 0 )
• 2 + 2 * n ( : 2, req_id, timestamp) + 1