WEEK 6: ENTRY 2

 Today at my internship, I was tasked at converting the json data format that my big query returns. My query from Big Query API returns a Json response body. Unlike the regular json array data I have seen previously, this json was different because first it has some schema metadata that I don’t need in my response body. The json data also is nested with each key in each map having the same key name, let say “v.” For me, this was the biggest challenge I have had with manipulating json data. 


So how did it go for me? Well, I must say that it is really tedious. I first of all had to read more on manipulating nested json data and then use the Go programming language to do the conversion. After reading a couple of articles, I got an idea that I could use a Go package, unmarshall, to modify the json data. From the stack overflow solution I found, the unmarshall package was used for very simple json data: key: value pair map data type.  Thus, to mimic that approach was very unlikely to resolve my problem.  I tried it on my codebase but it did not work at all. I also tried going through the other articles my manager sent me but it did not work out as well.  Until now, I’m having trouble unmarshalling the json data I got from Big Query. 


As I am writing this blog, I felt like I was so naive that I did not try using the Go playground online IDE and create a replica of my data and use the unmarshall function to test out my logic. So too, I could have saved a lot of time if I had consulted by buddy and see what their approach or suggestion could be with this issue. Therefore, I’m scheduling a meeting with my buddy first thing tomorrow; however, I will try using the Go playground online and try out my replica data that way it would speed up the debugging process with my logic. 

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