WEEK 9: ENTRY 3

At my internship today, I continued on completing the merging and outputting the final result on my server. Yesterday I was able to successfully compare the hostnames from the Elasticsearch API and Big Query API in the form of struct; however, I could not combine the two struct and transform the struct data type into a readable format, for instance Json. As a result, I spent my whole today resolving that issue. In simple terms, I have these two structs that I needed to merge after making the comparison and display the one merge data on my browser. To make sure the comparison I was making from yesterday was correct, I loop through the merge data and create a map. Maps are great choices because of its keys and values; however, it was not the best choice because my server is to display the final output into a json format and apparently using a struct makes that way more dynamic and easier. With a struct, I could easily convert the struct into a json format by unmarshalling it. 


Although I have been working with structs for a while now, it was a different approach I needed because after the comparison I needed to append the hostnames and their metadata to a data structure, which could be an array, map, or struct. In my case, the struct was the best option. I could easily append the data to the map but I was little did I know that I can do the same with the struct. All this while I have been having the answer beneath my eyes, but as the saying goes, “Ignorance is bliss.”  I felt so dumbed when my buddy helped me to append the data to the struct because it was the simplest part of all this implementation. In another way, I felt that it was because I just did not know, so it was not as bad as it should have been when I knew. 


Generally, I gained the understanding of how versatile Go structs are as well as how easy resolving an issue is when you understand what data structures best suits your use case. Another insight I gained was that I could always explore various options while troubleshooting an issue to narrow down the wide range of failure percentage. As a result, I intend to keep working harder on my data structures and Go skills so that next time I encounter a similar issue, it would be made easier.

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