This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Enhanecement request to have file connector accept a list of hosts, and not just a single host name
Client uses orc and Avro HDFS formats, which in turn use File Connector stage instead of Big Data File stage.
The file connector leverages WebHDFS and has a â€œhostâ€ property that must be explicitly set to point to an active name node, in order for it to function.
Since any one of two (or more) name nodes may be active on this client's EDL at any given time, the workaround implemented was to poll the available name nodes and seeing which one is active, just prior to launching jobs.
The client has various flavors of this scheme, with all having the following commonality:
a. They are somewhat fragile since the name node can always fail over during, or right after the poll
b. There is a balancing act between polling more often and cluttering your job stream with repeated polling calls and polling less often and inviting job failures when the name node fails over and the next job uses the no-longer-active name node
Impact : ======
Datastage cannot dynamically find the active namenode, and Datastage sequences will fail due to name node failover in the middle of the sequence.
What the client needs is for the file connector to accept a list of hosts, and not just a single host name, in order to handle failover scenarios appropriately. The expectation is that this scenario is common in a real-world Hadoop implementation, and do so â€œout of the boxâ€.
Do not place IBM confidential, company confidential, or personal information into any field.