[#KATTA-76] Attempting to add an index on a non-existent HDFS breaks listIndexes

Katta

Attempting to add an index on a non-existent HDFS breaks listIndexes

Created: 17/Jul/09 12:00 AM Updated: 19/Nov/09 08:27 PM

Component/s:

index

Affects Version/s:

0.5.1

Fix Version/s:

0.6

Description

« Hide

In this example I've attempted to add an index, but I've made a typo in the port number:

$ bin/katta addIndex index3 hdfs://localhost:80200/index org.apache.lucene.analysis.StandardAnalyzer 1
.not deployed index index3
$ bin/katta listIndexes
Exception in thread "main" java.io.IOException: Call to localhost/127.0.0.1:19000 failed on local exception: Connection refused

You should be able to list your indices even if one of them is not available. That way you would be able to know which index to remove.

In addition, the "not deployed index index3" message you get upon trying to add the index in the first place is unhelpful.

All

Comments

Change History

git Commits

Sort Order:

[ Permlink | « Hide ]

Stefan Groschupf added a comment - 13/Oct/09 10:58 PM

not sure if I understand this:

"In addition, the "not deployed index index3" message you get upon trying to add the index in the first place is unhelpful."

Can you please explain what you mean? Thanks.

[ Permlink | « Hide ]

Phil Hagelberg added a comment - 13/Oct/09 11:40 PM

It's been a while, but I think I meant instead of "not deployed" it could give a reason why it couldn't be deployed.

Showing the "Call to localhost/127.0.0.1:19000 failed on local exception: Connection refused" error on the call to addIndex rather than listIndexes would be a good improvement.

[ Permlink | « Hide ]

Johannes Zillmann added a comment - 19/Nov/09 08:27 PM

In case the index is not reachable no exception will be thrown anymore. The size calculation which caused the exception is skipped and shows -1 in this case.