WEEK 8: ENTRY 1

 At my internship today, I was working on troubleshooting the 403 authorization error I had from my logs when I was testing my SSO Auth Token connection to the Elasticsearch API. Prior to today, I wrote a Golang code using the Golang Olivere search package to connect to the Elasticsearch API. Basically, I passed my http client and an elasticsearch method to check if an index exists on the cluster of the Elasticsearch API. Having confirmed whether the system user is authorized to make a call to the Elasticsearch API, I was left with very little hints on what I could be doing wrong. Then the question about, what’s next came? 


Well, as usual, there are always smarter people around me in the team, so I asked around to see if someone had worked with Elasticsearch before. To my surprise, one of the VP on our team had prior knowledge, so he decided to help me out with my code. We did pair programming and he was the driver for the most part. I must say that he is very versed with Golang and quick in his debugging. Instead of running the code to the K8s deployment Gitlab, he made it very simple by running the code locally on intelliJ. I learned that it is way easier to debug because with that method, we were able to add a debugger and checkout for errors. With the debugger, we could locate what part of our code was giving us an output and what part was failing. We used numerous print statements that helped us see the errors. It turned out that the API did not like the confirmation of whether a particular index exists or not. Therefore, we instead wrote an elasticsearch query, which gave us an output. 


Although I spent more time debugging this issue, it was very worth the time spent. During this process, I learned so much about how to use the intelliJ debugger tool. So too, I read more documentation on how to use the Olivere elasticsearch package. Thus, I intend to work more on my debugging skills because from the help I received, I learned that I did not exhaust all the possible approaches when I was debugging my code.


Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more