Yes, that's precisely the method that should get initCredentials(job) as well. All the other overloaded methods with table are covered.
On Mon, Apr 7, 2014 at 2:48 PM, Ted Yu <[email protected]> wrote: > You are talking about this method, right ? > > public static void initTableMapperJob(List<Scan> scans, > Class<? extends TableMapper> mapper, > Class<? extends WritableComparable> outputKeyClass, > Class<? extends Writable> outputValueClass, Job job, > boolean addDependencyJars) throws IOException { > > Looks like it should call initCredentials(job) as well. > > > On Mon, Apr 7, 2014 at 2:37 PM, Jim Huang <[email protected]> wrote: > > > I am looking at the 0.94 branch and I have noticed that the overloaded > > methods for "initTableMapperJob" behaves differently in that one of them > > calls the "initCredentials(job);" while the others don't. For people who > > are using Kerberos security on their cluster, the initCredentials(job) > sets > > up the HBase security tokens for all the mapper tasks only for that > > overloaded method. Is there a specific reason why this could be > > intentional? Otherwise, I would like to create a new JIRA to see if I > can > > work on this as a newbie issue. > > > > Thanks for any pointer. > > Jim > > >
