Jump to content

Search History shows more documents retrieved than the doc grid


Gus Wiening

Recommended Posts

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

When searching inside of Eclipse, the search history displayed on the left will allow you to easily re-run a previous search by clicking on the entry. It also displays the number of search hits in parenthesis.

 

However, sometimes, the number in parens will show larger than the number of docs in the grid. For instance, you might see "1 - (6028)" in the history window, but the document grid may show only 4,097 entries.

 

In this instance, the culprit is most likely an out-of-date dtSearch index. When you perform a text search in Eclipse, the dtSearch service will return a list of DocIDs from dtSearch representing the list of all docs which contained hits. However, it's entirely possible that this list may contain DocIDs which no longer exist within the case. When the document grid is populated, it will only return documents which have a valid DocID. Thus, the case will be displaying only those documents which actually exist.

 

This situation can be resolved by performing a full case reindex.

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

Hi Gus,

I get what your trying to explain here, but the search history exists only for the current session. So, unless it been a long day, where the search was executed at start of the day and then some documents were add or deleted and the index not updated. In my experience, this occurs when eligibility criteria for the documents changed which caused exclusion of certain documents from the search results, when the search was re-run from search history.

Vai

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Vaibhav,

 

This can actually happen when the search is executed immediately after deleting the documents and prior to rebuilding the index. For instance, if a search for "Consumer" would have brought back 5000 docs, but then 1000 of those are deleted without the index being rebuilt, the search for "Consumer" executed at that time would retrieve the 4000 docs which exist but would report having retrieved 5000 docs in the history window. Ultimately this is just a small UI hiccup with no actual user impact other than the fact that the number in the search history does not reflect the number of docs retrieved in the search.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...