#general


@mineshp: @mineshp has joined the channel
@karinwolok1: Hello new Pinot members! :wine_glass: Welcome to the community! :wave: Who are you? What brought you to the community? How did you first hear about Pinot? @zhangmingfeng1982 @garystaf @coolhongly @maheshda @julius.syvanen @y.a @nkarandikar @lakshmanan.velusamy @mineshp @kevinv @harsur_12 @rams357 @ravi.maddi @rajasekhar.m @dixit @sathi.tadi @alexandre @avinashup45 @jmeyer @c.ravikiran123 @djwang @kmvb.tau
@wuwenw: @wuwenw has joined the channel
@sosyalmedya.oguzhan: Hello, i have a few questions about hdfs deep storage. We are working on AliCloud, and we want to use Alibaba Object Storage Service(OSS) as hdfs deep storage. We are trying to configure hdfs deep storage to use OSS as deep storage. We are working on Kubernetes. Is there anyone working with pinot on alibaba cloud? Or can anyone help us for that? Also i wonder that does pinot controllers and servers tries to connect deep storage while pods are creating? Because we set deep storage configs and put jars after pod is created
  @mayanks: I am not aware of Pinot being used on Alibaba cloud, but let's see if someone responds here. I am unclear on your question on OSS, but assuming you want Pinot to use OSS as the deepstore, then you just need to implement PinotFS interface to create OSS plugin. Pinot controller will probably have some access initialization for PinotFS (OSS in your case). Will need to check if it an cause any issues for you.
  @fx19880617: does AliCloud provide a managed k8s cluster which you can use, similar to AWS EKS ?

#random


@mineshp: @mineshp has joined the channel
@wuwenw: @wuwenw has joined the channel

#feat-text-search


@zhangmingfeng1982: @zhangmingfeng1982 has joined the channel

#feat-presto-connector


@mineshp: @mineshp has joined the channel
@garystaf: @garystaf has joined the channel
@zhangmingfeng1982: @zhangmingfeng1982 has joined the channel

#troubleshooting


@mineshp: @mineshp has joined the channel
@wuwenw: @wuwenw has joined the channel

#pinot-dev


@amrish.k.lal: I am seeing and also failing with the same error message in JDK 1.8 Quickstart (JDK 11, 13 Quickstart passes). So this must be a generic build issue rather than something specific to changes in these PRs? Error messages given below. Any idea what has changed here? ```[{"message":"BrokerResourceMissingError","errorCode":410}] ... Executing command: StopProcess -controller -server -broker -zooKeeper 18885 + true 18886 + kill -0 3750 18887 .github/workflows/scripts/.pinot_quickstart.sh: line 71: kill: (3750) - No such process 18888 + break 18889 + rm -rf /tmp/PinotAdmin/zkData 18890 + '[' 0 -eq 0 ']' 18891 Batch Quickstart failed: Cannot get correct result for count star query. 18892 + echo 'Batch Quickstart failed: Cannot get correct result for count star query.' 18893 + exit 1 18894 Error: Process completed with exit code 1.```
  @mayanks: Seems the quickstart test has become brittle recently. Some JDK version keeps failing randomly and passes on rerun
  @jackie.jxt: Github Actions test vm only provides 2 cores:
  @jackie.jxt: I suspect enabling the lead controller resources by default adds some extra workload on the controller, which causes the issue
  @jackie.jxt: Let's see if extending the setup time fixes the issue:
  @mayanks: It was approved, so I took the liberty to merge the PR.
  @mayanks: @jackie.jxt ^^
  @jackie.jxt: Was planning to run tests more times lol. Let's see if the problem gone in master
  @npawar: doesnt look like it’s helping
  @jackie.jxt: Yeah, same issue..
  @mayanks: Argh
  @fx19880617: seems this time it’s unit test failure
  @fx19880617: pinot-spark :stuck_out_tongue:
  @jackie.jxt: There is another quick-start test failure:
@grace.walkuski: Hello! :wave: I am trying to write integration tests for my application that hits Pinot through the Java JDBC. When we do the same for elasticsearch, we use to spin up a docker image to run the tests on. There is not a test container for Pinot. Does anyone have experience with this or has found an easy way to either make your own test container or spin up the docker image yourself? Thanks!
@g.kishore: we recently put together a test container for pinot as well @kanth909 ^^
@kanth909: @kanth909 has joined the channel
@kanth909: sharing it here as well, if anyone else needs it
@kanth909: ```import org.testcontainers.containers.GenericContainer; import org.testcontainers.containers.wait.strategy.Wait; import org.testcontainers.containers.wait.strategy.WaitAllStrategy; import org.testcontainers.utility.DockerImageName; public class PinotContainer extends GenericContainer<PinotContainer> { public static final int BROKER_HTTP_PORT = 9000; public static final String DEFAULT_ENDPOINT = "/"; private static final DockerImageName DEFAULT_IMAGE_NAME = DockerImageName.parse("apachepinot/pinot"); private static final String DEFAULT_TAG = "0.6.0"; public PinotContainer() { this(DEFAULT_IMAGE_NAME.withTag(DEFAULT_TAG)); } public PinotContainer(String pinotVersion) { this(DEFAULT_IMAGE_NAME.withTag(pinotVersion)); } public PinotContainer(final DockerImageName dockerImageName) { super(dockerImageName); dockerImageName.assertCompatibleWith(DockerImageName.parse("apachepinot/pinot")); withExposedPorts(BROKER_HTTP_PORT); withCommand("QuickStart", "-type", "batch"); waitingFor(Wait.forHttp(DEFAULT_ENDPOINT).forStatusCode(200).forPort(BROKER_HTTP_PORT)); } @Override protected void configure() { super.configure(); withCreateContainerCmdModifier(createContainerCmd -> createContainerCmd.withName("pinot-quickstart")); withCommand("QuickStart", "-type", "batch"); waitingFor( new WaitAllStrategy() .withStrategy(waitStrategy) .withStrategy(Wait.forListeningPort())); } public String getPinotBrokerUrl() { return String.format("", getHost(), getBrokerPort()); } public Integer getBrokerPort() { return getMappedPort(BROKER_HTTP_PORT); } }```
@kanth909: we will publish it when we get a chance but for now you can just use this class
@zhangmingfeng1982: @zhangmingfeng1982 has joined the channel

#getting-started


@garystaf: @garystaf has joined the channel

#pinot-flow


@chinmay.cerebro: @chinmay.cerebro has joined the channel
@vallamsetty: @sathi.tadi: He Sathi .. Hope you are well. I added @chinmay.cerebro to this channel. Chinmay is a leader in our engineering team and has extensive experience building and running apps on top of Pinot at Uber and LinkedIn. I requested him to jump on our next call to provide an deep dive on Pinot and answer any questions ..
@vallamsetty: Let us co-ordinate the best time for this session here. Chinmay is also in bay area, but we can do an IST friendly time as some of your team is based there. Please suggest some days/time that would work for you.
@sathi.tadi: Thanks @vallamsetty. Hi @chinmay.cerebro Nice to e-meet you.. Can we do this session today evening anytime after 10 PM PST or tomorrow morning @8:30 AM?
@vallamsetty: I have a conflict tomorrow morning, day after works for me. Let's wait for @chinmay.cerebro to get back.
@chinmay.cerebro: day after (4/8) @ 8:30 am PST works for me as well
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Reply via email to