51. . . . . . . . . abstract class has three main methods for loading data and for most use cases it would suffice to extend it. A. Load B. LoadFunc C. FuncLoad D. None of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option B No explanation is given for this question Let's Discuss on Board
52. Point out the correct statement. A. LoadMeta has methods to convert byte arrays to specific types B. The Pig load/store API is aligned with Hadoop InputFormat class only C. LoadPush has methods to push operations from Pig runtime into loader implementations D. All of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option C No explanation is given for this question Let's Discuss on Board
53. Which of the following has methods to deal with metadata? A. LoadPushDown B. LoadMetadata C. LoadCaster D. All of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option B No explanation is given for this question Let's Discuss on Board
54. . . . . . . . . method will be called by Pig both in the front end and back end to pass a unique signature to the Loader. A. relativeToAbsolutePath() B. setUdfContextSignature() C. getCacheFiles() D. getShipFiles() Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option B No explanation is given for this question Let's Discuss on Board
55. Point out the wrong statement. A. The load/store UDFs control how data goes into Pig and comes out of Pig. B. LoadCaster has methods to convert byte arrays to specific types. C. The meaning of getNext() has changed and is called by Pig runtime to get the last tuple in the data D. None of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option C No explanation is given for this question Let's Discuss on Board
56. . . . . . . . . return a list of hdfs files to ship to distributed cache. A. relativeToAbsolutePath() B. setUdfContextSignature() C. getCacheFiles() D. getShipFiles() Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option D No explanation is given for this question Let's Discuss on Board
57. The loader should use . . . . . . . . method to communicate the load information to the underlying InputFormat. A. relativeToAbsolutePath() B. setUdfContextSignature() C. getCacheFiles() D. setLocation() Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option D No explanation is given for this question Let's Discuss on Board
58. . . . . . . . . method enables the RecordReader associated with the InputFormat provided by the LoadFunc is passed to the LoadFunc. A. getNext() B. relativeToAbsolutePath() C. prepareToRead() D. all of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option C No explanation is given for this question Let's Discuss on Board
59. . . . . . . . . method tells LoadFunc which fields are required in the Pig script. A. pushProjection() B. relativeToAbsolutePath() C. prepareToRead() D. none of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option A No explanation is given for this question Let's Discuss on Board
60. A loader implementation should implement . . . . . . . . if casts (implicit or explicit) from DataByteArray fields to other types need to be supported. A. LoadPushDown B. LoadMetadata C. LoadCaster D. All of the mentioned Answer & Solution Discuss in Board Save for Later Answer & Solution Answer: Option C No explanation is given for this question Let's Discuss on Board