Yes, that was the problem! The new accumulo instance did not have the correct authorizations. Setting the authorizations and scanning the table works correctly.
Thank you! 2017-10-11 16:01 GMT+02:00 Keith Turner <[email protected]>: > Are you scanning with the correct authorizations? May be filtering > everything out on the server side if not. > > On Wed, Oct 11, 2017 at 3:05 AM, vLex Systems <[email protected]> > wrote: > > Hi, > > > > I'm doing backups of an accumulo database following the procedure in > > the readme (clonetable, offline and exporttable). I distcp to s3 and > > also upload the exportMetaddata.zip to s3. > > I do the restore by downloading the files from s3, distcping them to > > hadoopfs and then doing the importtable. > > > > > > When I restore the tables in a new accumulo server, all tables but one > > are correctly restored. When I do a scan -t of that table, the shell > > hangs approximately for a minute and it returns nothing. > > > > According to the accumulo web interface the table has data. How can I > > debug what's happening with that table? >
