WEEK 8: ENTRY 3

 At my internship today, I continued working on the HTTPS GET request to the elasticsearch api. Having constructed my elasticsearch query in the Elasticsearch console, I just needed to use that query and pass it to my elasticsearch api call in my intelliJ code. The goal is to use the list of hostnames I queried from Big Query and get their metadata from the elasticsearch api. I used the olivere elasticsearch package because it is compatible with my http client. So too, I would just have to use the package’s functions to make the Get request to the api. 


After writing the Get request function and passing the list of hostnames and pushing my code to Gitlab, it did not work on the first try. The data format is returned was in byte format and I would like to have it in Json readable format. Thus, I iterate through that array of byte data and convert them into json. However, the elasticsearch olivere package size can only take 10,000. This is a big issue  for my case because the hostnames could be more than 140,000 and having a default size of 10,000 is definitely not a good case for me. So my next step is to figure out how I would work around that. I might have to make multiple api calls each time instead of a bulk request. 


Generally, the day was very insightful because I got to use my knowledge about the olivere package and use it to make the api call. It was a very fast resolution because while I was waiting on the other team to give me authorization to make the api call, I spent some time reading the documentation on that package, and that seems to pay off. Besides, I learned through the process that I should have double checked if the size of the package function would accept more than the default size. In the future, I would read more on a package’s function and see it’s deem fit to be use in my use case.


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