Update index-redis-om-spring-hash.mdx

add detail for the issue [451](redis-developer#451)

Author: TianMing2018

Diff for: docs/develop/java/spring/redis-om/index-redis-om-spring-hash.mdx

@@ -76,6 +76,13 @@ To use Redis OM Spring, open the `pom.xml` file and add the Redis OM Spring Mave
 </dependency>
 ```
 
+> TODO: assume that's a demo from [redis-om-spring](https://github.com/redis/redis-om-spring)
+> - this jar cloud have different `unique name` which from groupId、artifactId、version, and this doc was based on once of stage point
+>    - first, this `unique name` you offered can't be download cause we don't have it's repository node in `pom.xml`
+>       when I changed it's groupId to `com.redis.om` now, and add repo node whose url is  `https://s01.oss.sonatype.org/content/repositories/snapshots/` ,
+>       it do download a jar, however there is few difference  must be confirmed,i'will mark it with `TODO:xxx` below
+> - find this jar or rewrite in the latest version is on your turn.
+
 ### Gradle
 
 If using gradle add the dependency as follows:
@@ -86,6 +93,8 @@ dependencies {
 }
 ```
 
+> TODO: groupId and version number sholud same with import with maven
+
 ## Enabling Redis Repositories
 
 The generated application contains a single Java file, the `@SpringBootApplication` annotated main application.
@@ -144,6 +153,8 @@ services:
 To launch the docker compose application, on the command line (or via Docker Desktop), clone this repository
 and run (from the root folder):
 
+> TODO: maybe it's better to paste image whole id to ensure the result exactly as your's
+
 ```bash
 docker compose up
 ```
@@ -329,6 +340,8 @@ with `com.redis.om.documents.domain.Company:` (which is the default key prefix f
 1638336613.156351 [0 172.19.0.1:63396] "FT.CREATE" "UserIdx" "ON" "HASH" "PREFIX" "1" "com.redis.om.hashes.domain.User:" "SCHEMA" "firstName" "AS" "firstName" "TAG" "middleName" "AS" "middleName" "TAG" "lastName" "AS" "lastName" "TAG" "email" "AS" "email" "TAG"
 ```
 
+> TODO: didn't seen it in my container console , and why this indexId without prefix(package and classname?)
+
 ROMS uses the POJO fields annotated with `@Indexed` or `@Searchable` to build the index schema. In the case of the `User` POJO
 we have the fields `firstName`, `middleName`, `lastName` and `email` are all annotated as "indexable",
 meaning that we can do exact searches over these fields.
@@ -345,7 +358,7 @@ For each of the `User` POJO we should see a sequence of REDIS commands like:
 1638340447.200874 [0 172.19.0.1:63398] "HMSET" "com.redis.om.hashes.domain.User:01FNTB6JWTQHMK7NTEYA8725MP" "_class" "com.redis.om.hashes.domain.User" "email" "[email protected]" "firstName" "Zack" "id" "01FNTB6JWTQHMK7NTEYA8725MP" "lastName" "de la Rocha"
 1638340447.203121 [0 172.19.0.1:63398] "SADD" "com.redis.om.hashes.domain.User" "01FNTB6JWTQHMK7NTEYA8725MP"
 ```
-
+> TODO: executed commands don't exactly like this, executed count and order
 First SDR checks whether the object already exists in the Redis SET of primary keys using the `SISMEMBER` command. Then,
 a `DEL` is issued to remove the Hash, following by a `HMSET` to write the new or udpated Hash. Finally, the `id` property
 of the object is addded to the primary keys set using the `SADD` command.