Member since
11-17-2021
1128
Posts
256
Kudos Received
29
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2866 | 11-05-2025 10:13 AM | |
| 482 | 10-16-2025 02:45 PM | |
| 1038 | 10-06-2025 01:01 PM | |
| 821 | 09-24-2025 01:51 PM | |
| 629 | 08-04-2025 04:17 PM |
11-02-2023
08:37 AM
Hmm, that makes sense I suppose. That was my next guess 😉 Glad you figured it out, and thanks for posting the answer here, I appreciate it!
... View more
11-01-2023
05:51 PM
@JuniorDevOps Welcome to the Cloudera Community! To help you get the best possible solution, I have tagged our Ambari experts @Atahar @Scharan who may be able to assist you further. Please keep us updated on your post, and we hope you find a satisfactory solution to your query.
... View more
11-01-2023
08:24 AM
the same error message via Ranger UI. I added the same new table to list
... View more
10-30-2023
10:40 PM
@AK- Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
10-27-2023
03:12 AM
Thanks for the answer. following is the complete stack trace log. 2023-10-10 14:01:01,542 INFO [main] o.e.jetty.server.handler.ContextHandler Started o.e.j.w.WebAppContext@15e0fe05{nifi-api,/nifi-api,file:///opt/exgw/nifi-1.17.0/work/jetty/nifi-web-api-1.17.0.war/webapp/,AVAILABLE}{./work/nar/extensions/nifi-server-nar-1.17.0.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-api-1.17.0.war} 2023-10-10 14:01:01,703 ERROR [Timer-Driven Process Thread-1] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=22ec0a77-b91f-3a2a-e19b-dab6e46e0717] Request Processing failed: StandardFlowFileRecord[uuid=893fd559-fd28-475b-b2d1-e94fbf566d86,claim=,offset=0,name=893fd559-fd28-475b-b2d1-e94fbf566d86,size=0] org.apache.nifi.processor.exception.FlowFileAccessException: Failed to import data from buffer(ResponseBodySource(okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource@1de64fd6)).inputStream() for StandardFlowFileRecord[uuid=f4327acc-d1ea-4450-a5ad-89723bfafec6,claim=,offset=0,name=893fd559-fd28-475b-b2d1-e94fbf566d86,size=0] due to org.apache.nifi.processor.exception.FlowFileAccessException: Unable to create ContentClaim due to java.io.EOFException at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:3580) at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:1008) at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1356) at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:246) at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:102) at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Caused by: org.apache.nifi.processor.exception.FlowFileAccessException: Unable to create ContentClaim due to java.io.EOFException at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:3573) ... 13 common frames omitted Caused by: java.io.EOFException: null at okio.RealBufferedSource.require(RealBufferedSource.kt:199) at okio.RealBufferedSource.readHexadecimalUnsignedLong(RealBufferedSource.kt:381) at okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource.readChunkSize(Http1ExchangeCodec.kt:429) at okhttp3.internal.http1.Http1ExchangeCodec$ChunkedSource.read(Http1ExchangeCodec.kt:408) at okhttp3.internal.connection.Exchange$ResponseBodySource.read(Exchange.kt:276) at okio.RealBufferedSource$inputStream$1.read(RealBufferedSource.kt:158) at java.io.InputStream.read(InputStream.java:101) at org.apache.nifi.controller.repository.io.TaskTerminationInputStream.read(TaskTerminationInputStream.java:62) at org.apache.nifi.stream.io.StreamUtils.copy(StreamUtils.java:35) at org.apache.nifi.controller.repository.FileSystemRepository.importFrom(FileSystemRepository.java:837) at org.apache.nifi.controller.repository.StandardProcessSession.importFrom(StandardProcessSession.java:3570) ... 13 common frames omitted
... View more
10-26-2023
08:00 AM
@jai1gupta I am not clear on your ask here and it does not seem related to the question asked and solution accepted in this thread. Please start a new community question with details around what you are trying to accomplish/solve. Feel free to @MattWho in that new question so that I get notified and I will try to assist you there. Thank you, Matt
... View more
10-25-2023
03:37 AM
Thanks for assistance @DianaTorres
... View more
10-20-2023
03:27 PM
@Tyrone As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks.
... View more
10-20-2023
11:53 AM
Hi Krishna We have done this by pushing commands out to the shell after setting up a trusted SSH connection between CDSW and the Unix server. This is the python function we use: user_name = "username"
unix_server = "my.unix.host"
unix_path = "/some/path"
file_to_transfer = "my_csv_file.csv"
def scp_file_to_sas(local_path, file_name, user_name, unix_server, unix_path):
p = subprocess.Popen(
[
"scp",
"-v",
local_path + file_name,
user_name + "@" + unix_server + ":/" + unix_path + "/" + file_name,
]
)
sts = os.waitpid(p.pid, 0)
... View more
10-20-2023
05:26 AM
4 Kudos
We love to recognize community members who display their contributions to the Cloudera Community! With our Community Reputation Program, you will be able to collect and show off all badges or rank up to new levels.
We have introduced enhancements to our community ranking structure that make it easier to climb up the ranks. We have simplified the process of earning points and enabled you to reach higher levels faster.
What is the Cloudera Community Reputation Program?
The Cloudera Community Reputation Program is a system designed to recognize and reward community members for their contributions and engagement within the Cloudera Community platform.
What are the key components of the Reputation Program?
The Reputation Program comprises community ranks, badges, and leaderboards. The community platform acknowledges your contributions and engagement by asking questions, replying to others, giving and receiving kudos, and providing valued solutions.
How does the Rank Structure work in the Reputation Program?
Ranks reflect your status within the community, and your contributions add up to your rank advancement. You can go from a New Member to a seasoned Guru or Mentor by participating in our forums and helping other members.
How can I determine my current rank in the community?
An icon next to your username indicates your current rank. This icon changes as your contributions and engagement within the community increase. Check out the chart for a complete list of our ranks and corresponding icons.
How can I advance in rank within the Reputation Program?
To advance in rank, actively contribute to the Cloudera Community The more substantive your contributions, the higher your rank. Simple interactions and useful input will still contribute to your rankings, but advanced, well-rounded contributions really boost your rank. Check out an example of many ways in which you can move up!
Do community contributions also earn badges?
Yes, contributions to the community earn you badges.
Badges are a great way to be recognized for contributions to community discussions and questions. Additionally, badges may have different colors assigned by level to show your progression in certain community tasks, from beginner to advanced. Each badge group has a level from 1 to 5 (with the exception of solutions, which go up to 7). You’ll start out with beginner badges and progress to advanced.
The colors will go from gray to mint to orange, as seen below in the progression.
For example:
How do I find my badges?
To check your badges, go to your Community profile page (you can do that by clicking “Community Profile” in the top menu when you are signed in) and scroll down to “Community Badges”.
How is rank advancement different from earning badges?
Rank advancement is primarily based on your overall contributions and engagement within the Cloudera community. In contrast, badges are earned for specific actions or achievements, and they may have different levels based on the number of times you perform these actions.
What are the leaderboards in the Cloudera Community Reputation Program, and what do they recognize?
Leaderboards promote a little friendly competition and highlight community members who are providing the most valued solutions and quality content. Instead of a single leaderboard, we now have the following:
Top Solution Authors
Top Kudoed Authors
Top Community Article Contributors
The individual leaderboards are sorted by the last 30 days of contributions. You can change the time range to the last day, last week, or even "All Time".
Got more questions?
Get in touch with the Cloudera Community Team at community-team@cloudera.com. They are there to help and support community members who contribute, ask questions, and share their expertise to grow the collective knowledge within the community.
Thank you for helping us continue to grow our collective knowledge by asking questions, adding content, and sharing your expertise.
... View more